Wednesday, September 22, 2010

Advantages of Dynamic IP and Static IP

One of the techie words that you would often come across when you sign up for your home broadband package or business package is IP address or Internet Protocol address. When you get a broadband connection, you are normally offered an IP address so that other PCs in the world wide web network can connect and communicate with your PC (if you are a home user) or your web server (assuming, you are hosting a website on your web space).

Non-technically speaking, IP address is a unique number often assigned to your PC in a network. If you are connected to internet, just check the internet options to go to LAN settings. You would find the IP address of your PC. This address helps other PCs to identify your PC as well as helping your PC to get information from other PCs which have similar unique numbers.

IP addresses are of two types: Dynamic IP and Static IP. What are their features? Why do you get dynamic IP free, why does getting a static IP cost you a bit? What are the advantages and disadvantages of each type?

Remember, when your PC is not connected to internet, it can have any type of IP which is offered by the administrator. Usually, in a LAN network, the IP address of individual PC will be unique and that is the only required in such a network unless the PC is connected to internet.

Dynamic IP

Dynamic IP is usually offered free by all ISPs and this IP will change every time you log on to internet. This means your PC will be assigned different number codes at different times.

Advantages of Dynamic IP

In a network that is administered by Dynamic Host Configuration Protocol (DHCP), the allocation of IP address and network configuration are done much faster.

All the computers (clients) get IP address, DNS, gateway from the DHCP server, automatically. This also makes your task of adding new computers to the network much easier. Regardless of the size of the network, dynamic IP is quite useful as it is easy to allocate, distribute and manage.

In a large LAN network, dynamic IP administration helps you to save your time as you need not configure hundreds of computers manually.

Dynamic IP also helps you to log in as an anonymous user.

The main disadvantage of dynamic IP is that it is not suited to web hosting. You would require static IP then. However, home users will not find any difficulty in using this type of IP.

Static IP

A few broadband providers offer this option which has some distinct advantages. It is a useful feature when you consider web hosting as the server often needs this type of IP address as the DNS will be able to interpret the domain names as IP addresses which never change in the network. Static IP is quite helpful to identify a specific PC in a large network of PCs. Hence, static IP is often used in a large infrastructure environment.

Advantages of Static IP

As static IP never changes in the internet environment, a specific PC can be accessed and controlled and maintained from any place.

For web hosting purposes,static IP is very ideal. If you are a business user and want to promote your business via internet, go for a business broadband package which sometimes may provide you with a free static IP address. Businesses can see better growth and be in touch with their customers when they have their own websites. If you are looking for a cheaper option, find a business package that comes with free static IP and free web space.

Make sure that you pick the right business broadband package after going through the extras provided by the ISPs like free emails, free domain name, webspace etc.

Just think that you can create your own email addresses with your domain name. If your email accounts have some unique identity, they make a huge difference and become an important part of better management of your businesses, it is better to have your own email accounts with your own domain name. It will also help your company to cut a niche among your competitors.

If you are a gamer and use a dedicated broadband connection for that purpose, take a static IP and find the difference. It would definitely help you to have an significant edge over others. This is because the FTP servers make the data transfer much faster.

Related : Buy Cheap Bluetooth Headset | LOWER Prices

Tuesday, September 21, 2010

Set Up FTP Server Using FileZilla on Windows 7

FTP stands for File Transfer Protocol, if you want to know more about it, you can check it out at Wikipedia. FTP is actually getting less popular nowadays as users have lots of other protocols to exchange files, P2P especially BT. FTP, however, is still playing a very important role.

Let's say, if you have a file that's about 300MB and you would like to send it over to your friend oversea immediately. What would you do? Usually emails have attachment limit (usually it's not as high as 300MB) and it will be extremely slow and unstable if you try to transfer over instant messenger software like MSN. The best solution will be setting up your own FTP server at home and authorize your friend to download from your computer. Mind as well, you can set up an account so that you can view all of your files and grab them wherever you go.

If have already set up your remote desktop at home, you will probably leave the computer on 24*7 just so that you can access it any time you want. Or if you have a spare computer like I do, why don't you try to make use of it? I am going to show you how you can make your computer into a FTP server.

After trying a couple of the FTP server software, the freeware FileZilla Server became my choice.

OK, let's get started.

The first thing you will need to do is to install the package you just downloaded (from the above link); the installation is quite straight forward and I am not going to get into too detail.

Upon successful installation, FileZilla server will launch and you should be able to see the following interface:

Before we go ahead and set it up the ports, we would like to add a user to make sure it works. We will go to choose from "Edit-->Users" (Or there is a shortcut icon right underneath the "Edit" on the menu bar.)

I created a user named "anonymous", and I make sure the "Password" field is uncheck because I would like to make this as my public FTP account that visitors could download from my FTP server. If you would like to set up other accounts, make sure your "Password" filed is checked to enforce a secure login. For different users, you can assign different path, or you can just create a group and assign the path to all members in that group.

On the left hand side, you will see the "Shared folders", you can specify the folder path you would like "anonymous" to look at as well as the permission you would like to grant. Once it's done, click OK.

Note: The shared folder directories is the root folder that the selected user (in this case, it's "anonymous") could see, but any folders contained by root folders are also visible to this user.

The common thing Windows users would probably miss while setting up FileZilla is the Firewall. Over the installation, even though you grant permission for FileZilla server to access your computer resources, there is something not quite correctly set up.

Browse to your firewall setting, you should be able to find FileZilla Server Interface might be in the allow list; however, this is the problem. We should allow the FileZilla Server core instead of the interface. The interface is just the UI for end users like you and me to access the core program. So we click add to choose "FileZilla Server" from the installation folder:

Now it should be OK.

If you have two or more computers at home, you can give it a test now. First find out your internal IP address. If you don't know how to do it, check my previous post, set up your remote desktop. For example, I found that my server's internal IP is 192.168.1.111, then on the other computer, I simply type in ftp://192.168.1.111.

Note: If you have a different port other than port 21, let's say you have port 22, you should type in ftp://192.168.1.111:22 if you don't know what port it is, it's actually under setting-->General setting: If it works for you, we will move on; otherwise, please read the instructions again or ask me.

FTP server is meant to be exit in a network, if you just try to set it up at home, then you are done; but according to the situations I introduced in my first paragraphs, I do want to make it global.

Like a Remote Desktop, we will also need to set up port forwarding. In my case, since my FileZilla Server is on Port 21 on my computer, I will need to somehow forward the FTP request onto this port. Ideally, it would be great if we can set up port 21 as external port because every time we type in the address, we don't need to type in the port number (Browser's default FTP port is port 21). However, most of the ISP (Internet Service Provider), for example I use Telus, block port 21. We will need to find an alternate port as our external port:

I set up Port 5050 as my external port and all FTP request through this port will be redirect to Port 21 on my server. I am using D-Link DIR-825, if you have different router, please refer to the instruction on your manual.

If you set up your Dynamic DNS, then you are already done, if not, please go back and read my post; it's extremely easy.

Let's say you have your Dynamic DNS name as myServerAtHome.no-ip.org, then when you are outside, you can simply type in ftp://myServerAtHome.no-ip.org:5050, but if you are at home, you can just type in ftp://192.168.1.111.

You can use your browsers to visit your FTP server, however, I do recommend you to use FTP software. FileZilla Server is a great FTP server and they do have client software too. You can check FileZilla's website; if you haven't got one, why don't you try FileZilla Client?

Friends Link : Remote Console Wireless Fence Blu Ray Disks

Monday, September 20, 2010

Basic Configuration Tutorial For the Cisco ASA 5510 Firewall

Continuing our series of articles about Cisco ASA 5500 firewalls, I'm offering you here a basic configuration tutorial for the Cisco ASA 5510 security appliance. This device is the second model in the ASA series (ASA 5505, 5510, 5520 etc) and is fairly popular since is intended for small to medium enterprises. Like the smallest ASA 5505 model, the 5510 comes with two license options: The Base license and the Security Plus license. The second one (security plus) provides some performance and hardware enhancements over the base license, such as 130,000 Maximum firewall connections (instead of 50,000), 100 Maximum VLANs (instead of 50), Failover Redundancy, etc. Also, the security plus license enables two of the five firewall network ports to work as 10/100/1000 instead of only 10/100.

Next we will see a simple Internet Access scenario which will help us understand the basic steps needed to setup an ASA 5510. Assume that we are assigned a static public IP address 100.100.100.1 from our ISP. Also, the internal LAN network belongs to subnet 192.168.10.0/24. Interface Ethernet0/0 will be connected on the outside (towards the ISP), and Ethernet0/1 will be connected to the Inside LAN switch.

The firewall will be configured to supply IP addresses dynamically (using DHCP) to the internal hosts. All outbound communication (from inside to outside) will be translated using Port Address Translation (PAT) on the outside public interface. Let's see a snippet of the required configuration steps for this basic scenario:

Step1: Configure a privileged level password (enable password)

By default there is no password for accessing the ASA firewall, so the first step before doing anything else is to configure a privileged level password, which will be needed to allow subsequent access to the appliance. Configure this under Configuration Mode:

ASA5510(config)# enable password mysecretpassword

Step2: Configure the public outside interface

ASA5510(config)# interface Ethernet0/0

ASA5510(config-if)# nameif outside

ASA5510(config-if)# security-level 0

ASA5510(config-if)# ip address 100.100.100.1 255.255.255.252

ASA5510(config-if)# no shut

Step3: Configure the trusted internal interface

ASA5510(config)# interface Ethernet0/1

ASA5510(config-if)# nameif inside

ASA5510(config-if)# security-level 100

ASA5510(config-if)# ip address 192.168.10.1 255.255.255.0

ASA5510(config-if)# no shut

Step 4: Configure PAT on the outside interface

ASA5510(config)# global (outside) 1 interface

ASA5510(config)# nat (inside) 1 0.0.0.0 0.0.0.0

Step 5: Configure Default Route towards the ISP (assume default gateway is 100.100.100.2)

ASA5510(config)# route outside 0.0.0.0 0.0.0.0 100.100.100.2 1

Step 6: Configure the firewall to assign internal IP and DNS address to hosts using DHCP

ASA5510(config)# dhcpd dns 200.200.200.10

ASA5510(config)# dhcpd address 192.168.10.10-192.168.10.200 inside

ASA5510(config)# dhcpd enable inside

The above basic configuration is just the beginning for making the appliance operational. There are many more configuration features that you need to implement to increase the security of your network, such as Static and Dynamic NAT, Access Control Lists to control traffic flow, DMZ zones, VPN etc.

Visit my website in my resource box below for more information about Cisco products and solutions. You can also learn how to configure any Cisco ASA 5500 Firewall Here (applicable for ALL ASA models running software versions 7.x and 8.x).

See Also : LASIK Vision Institute Pride Scooters

Sunday, September 19, 2010

Web Hosting Website Migration Process - Moving From One Web Hosting Company to Another

This article provides a detailed step by step process for migrating a website from one web hosting provider to the next without disrupting the delivery of either the website or email services associated with the domain.

A summary of the steps involved in the process are:


Make sure you have all necessary information
Request set up of the hosting account with the new provider
Replicate DNS with the new provider
Re-delegate the domain name
Copy the site content
Test the site on the temporary domain
Configure email services
Change DNS records.
Migration completed

Before you begin make sure you have everything you will need to complete the migration. This includes, among other things:


Domain password or registry keys
Access to the web hosting account on the existing web hosting provider
Ability to perform database dumps on the existing web hosting provider
All SSL certificate files (if there is one)
Checked that the hosting platform is compatible (i.e. versions of applications, Linux vs windows).
List of all existing email addresses
Setup the web hosting account with the new web host

Make sure that the website hosting account is setup with the new web hosting provider. Setting up the account will not interfere with the operation of the existing live site. When the web hosting account is configured with the new host, you should receive all the access details for adding content to the account.

DNS Configuration

We highly recommend redelegating the domain name to the name servers of the new hosting company in advance of moving any other services, this is commonly referred to as the DNS.

DNS is usually handled by the same company that handles either website or email hosting or both. It is however technical independent and is a service that can be handled by different companies.

DNS is where the change is made made when a website is switched from one hosting provider to another.

We suggest changing the DNS to be hosted by the new provider but set the DNS records to continue to point all services at the existing hosting service provider. Once the DNS records are hosted by the new provider, change the TTL (Time To Live) attribute to reduce it from the standard 24 hours to 10 minutes. This allows us to make changes between providers in as little as 10 minutes once the services are ready to be migrated. This is a big improvement on the standard 24 hours since the level of disruption is greatly minimised and the risk of users being spread between old and new sites is so much lower.

We first need to make sure we have an accurate copy of the records from the existing host. The best way to do this is to request a copy of the records from the current host or DNS provider. If this is not possible, with a reasonable knowledge of the services in use on the domain name, it is usually possible to collect most of the necessary information that you need using tools such as dig or nslookup.

Site Copying

Once DNS migration has been initiated we have approximately 24-48 hours before the domain can be redelegated to the new hosting providers name servers. This will give us ample time to move the content across to the new servers. There are essentially two ways this can be completed depending on what information we have. If you have FTP/SSH details then you will be able to log in and copy the files across. Important things to note:


Databases? Make sure a dump is taken and saved in the home directory
Provided you have SSH access, the easiest way to copy the content across is to tar up the entire home directory and then SCP it across.

A simple way of copying an entire website if you have FTP access is using LFTP. Login to the server the account is on as root and:


$ su -
$ cd public_html
$ lftp

lftp:~> user
Password:

lftp:/> ls (just to make sure you're in the correct folder, otherwise cd to the folder containing the website)
lftp:/> mirror

This will mirror the entire contents of the website into your current folder. You still need to manually copy any databases across.

Without SSH/FTP access you can copy the site using Wget if you keep in mind a few caveats: Wget will only work when there is static content on the webpage, no dynamic pages (eg php, asp, shtml), no databases. If the site contains Javascript or Flash you might find you miss parts of the content.

Site Testing

Once the website has been copied test it on the temporary URL (as provided in the introductory email) for the hosting account setup and compare against original website to ensure everything is working correctly. If anything is not working, make sure it is fixed at this stage.

It is important that you confirm with the new hosting provider that you have completed your testing of the website.

Email Configuration

Assuming that all email services are to be migrated, a full list of email addresses that are required must be provided to your hosting company. If mail services are remaining with the existing host, or they are already handled externally it is important that you let your hosting company know.

Once they have been provided your web host should supply you with new username and passwords.

Note that if email services are to be migrated in most cases you will be changing the username and password details for email services. This change is the one that will have the greatest effect on the end user of the hosting services and it's important that it is communicated properly. If peoples email breaks these days, it's often more disruptive to their work than cutting of their telephone.

We've found that the best way to ensure no email is lost in the migration process is to leave the existing configuration in place, so that the mail client continues to check the old mail server, then add a new profile that checks the new mail server concurrently. This should usually be left in place for up to 7 days after the change over. It will ensure that any mail that still does make its way to the old location will be collected.

Finalise Migration

Once everything has been checked and rechecked we can switch the site across our servers for web and email hosting (by switching the DNS).

You should contact your hosting provider to confirm a time to make the change.

If the website uses a database it may be necessary to complete a final synchronisation of database immediately prior to changing the DNS.

Complete!

That's it, you're all done. You site migration should be complete and all traffic flowing to the new host with a minimum of disruption.

My Links : Baldor Motors Transcend 8 GB SDHC Class 6 Store

Saturday, September 18, 2010

Best Website Hosting Providers

There are a lot of benefits and advantages a business could get from tying up with a web hosting provider.  Aside from helping they promote their products; they can also aid them in increasing their revenue by cutting down extra costs.  Below are additional benefits a company could get by doing business with a best web site hosting partner:

They may choose which Operating System will best work for their company.  They also have the liberty to select which Operating System Support to use.  They may either go for a Linux or for an open source system such as Red Hat Enterprise, Cent OS, Microsoft Windows Server, Fedroa Core, and Debian.  Using an Operating system that you are familiar with helps you save time and energy.  It keeps you from the hassle of having to learn a brand new system.

Also, having the ability to choose your Operating system helps you manage your company's budget wisely.  If you worry about additional expenses, then you may opt for an open source system, since they do not cost anything extra.  If needed, then you can just purchase additional services like security patches upgrade, exposure and OS resolutions, and OS upgrade.  Choosing the best web site hosting provider among the numerous selections given may seem difficult.  But yet, it may prove to be rewarding as your business grows.

Data Center Services may help enhance your web hosting experience.  It helps you get relevant services to do tasks for your business smoothly and flawlessly.  Data Center offers exceptional services like firewall services, anti - virus programs, technical support, load balancing, D Dos (distributed denial - of - service attack) reduction and protection, backups and repair, DNS hosting accommodation, database management, disaster recovery, protection from an unauthorized user, performance tuning, software configuration and installation, load balancing, monitoring servers, user management, operating system, and simple network protocol.

Security of information stored online is very important.  And as such, companies should take extra measures in making sure that their database is safe from spammers, hackers, and worms.  Web hosting providers supply anti - virus programs, firewall protection, and scanning systems to prevent any unauthorized user from accessing confidential information on your website.  This is one advantage website owners could get from managed servers.  They provide extra security to your business and online information.  Hosting partners that guarantee added security should be on top of your list of best web site hosting providers.

My Links : Zoom H2 Handy Portable Sterio Recorder Best Price Acer Aspire One AOD150-1920 Store Toshiba Satellite Laptops Store. LOWER Prices

Friday, September 17, 2010

What is Process MDNSResponder.exe?

mDNSResponder.exe is a process associated with "Bonjour for Windows" software. It is mainly used by ITunes for music sharing. This is a non-essential process meaning that it is not needed by the SYSTEM to perform its normal function thus disabling or enabling it is down to user preference. mDNSResponder.EXE as mentioned above is Bonjour system service that implements Multicast DNS Service Discovery for the discovery of services on the local network, and unicast DNS Service Discovery for discovery of services anywhere over the whole Internet. mDNSResponder.EXE was built originally to go with the Mac OS X Platform since Apple produce both Mac OS and ITunes music software. Applications like iTunes, iPhoto, iChat and Safari use mDNSResponder.EXE to implement zero-configuration (zero configuration is explained in the paragraph below) network music sharing, photo sharing, chatting and file sharing, and discovery of remote user interfaces for hardware devices like printers and web cameras. mDNSResponder.EXE is open source, and hardware device manufacturers are encouraged to embed the mDNSResponder source code directly into their products to benefit from zero-configuration networking.

What is Bonjour?

Bonjour service which is a zero-configuration networking system enables automatic discovery of computers, devices, and services on IP networks. Bonjour uses industry standard IP protocols to allow devices to automatically discover each other without the need to enter IP addresses or configure DNS servers. Bonjour is basically like 3 services joined together into one. Specifically, Bonjour service enables configures automatically IP address assignment without a DHCP server, translates domain name to IP addresses without the need for a DNS server (Domain Name Server), and does service discovery without a directory server. Bonjour is an open protocol which Apple has submitted to the IETF. Open protocol means that any software developer can read its documentation or download the source code for it and implement his own version of this service or include it in his application for networks discovery.

mDNSResponder.exe in Windows operating system is usually located in a subfolder of "C:Program Files" or sometimes in a subfolder of the "My Files" folder. The application uses ports to connect to LAN or Internet. You can uninstall this program from the add/remove software feature in the control panel.

Related : Buy Cheap Anti Virus 2010 | LOWER Prices External Harddisk Store. LOWER Prices

Thursday, September 16, 2010

Securing IIS 6.0 Web Server on Windows 2003

Hacking a Web Server
With the advent of Windows 2003 and IIS 6.0 there was a sharp turn in the way hosting services were being provided on Windows platform few years back. Today, web servers running on Internet Information Services 6.0 (IIS 6.0) are highly popular worldwide - thanks to the .NET and AJAX revolution for designing web applications. Unfortunately, this also makes IIS web servers a popular target amongst hacking groups and almost every day we read about the new exploits being traced out and patched. That does not mean that Windows is not as secured as Linux. In fact, it's good that we see so many patches being released for Windows platform as it clearly shows that the vulnerabilities have been identified and blocked.

Many server administrators have a hard time coping up with patch management on multiple servers thus making it easy for hackers to find a vulnerable web server on the Internet. One good way I have found to ensure servers are patched is to use Nagios to run an external script on a remote host, in turn alerting on the big screen which servers need patches and a reboot after the patch has been applied. In other words, it is not a difficult task for an intruder to gain access to a vulnerable server if the web server is not secured and then compromise it further to an extent that there is no option left for the administrator but to do a fresh OS install and restore from backups.
Many tools are available on the Internet which allows an experienced or a beginner hacker to identify an exploit and gain access to a web server. The most common of them are:

IPP (Internet Printing Protocol) - which makes use of the IPP buffer overflow. The hacking application sends out an actual string that overflows the stack and opens up a window to execute custom shell code. It connects the CMD.EXE file to a specified port on the attacker's side and the hacker is provided with a command shell and system access.

UNICODE and CGI-Decode - where the hacker uses the browser on his or her computer to run malicious scripts on the targeted server. The script is executed using the IUSR_ account also called the "anonymous account" in IIS. Using this type of scripts a directory transversal attack can be performed to gain further access to the system.

Over these years, I've seen that most of the time, attacks on a IIS web server result due to poor server administration, lack of patch management, bad configuration of security, etc. It is not the OS or the application to blame but the basic configuration of the server is the main culprit. I've outlined below a checklist with an explanation to each item. These if followed correctly would help prevent lot of web attacks on an IIS web server.

Secure the Operating System
The first step is to secure the operating system which runs the web server. Ensure that the Windows 2003 Server is running the latest service pack which includes a number of key security enhancements.

Always use NTFS File System
NTFS file system provides granular control over user permissions and lets you give users only access to what they absolutely need on a file or inside a folder.

Remove Unwanted Applications and Services
The more applications and services that you run on a server, the larger the attack surface for a potential intruder. For example, if you do not need File and Printer sharing capabilities on your shared hosting platform, disable that service.

Use Least Privileged Accounts for Service
Always use the local system account for starting services. By default Windows Server 2003 has reduced the need for service accounts in many instances, but they are still necessary for some third-party applications. Use local system accounts in this case rather than using a domain account. Using a local system account means you are containing a breach to a single server.

Rename Administrator and Disable Guest
Ensure that the default account called Guest is disabled even though this is a less privileged account. Moreover, the Administrator account is the favorite targets for hackers and most of the malicious scripts out there use this to exploit and vulnerable server. Rename the administrator account to something else so that the scripts or programs that have a check for these accounts hard-coded fail.

Disable NetBIOS over TCP/IP and SMB
NetBIOS is a broadcast-based, non-routable and insecure protocol, and it scales poorly mostly because it was designed with a flat namespace. Web servers and Domain Name System (DNS) servers do not require NetBIOS and Server Message Block (SMB). This protocol should be disabled to reduce the threat of user enumeration.

To disable NetBIOS over TCP/IP, right click the network connection facing the Internet and select Properties. Open the Advanced TCP/IP settings and go to the WINS tab. The option for disabling NetBIOS TCP/IP should be visible now.

To disable SMB, simply uncheck the File and Print Sharing for Microsoft Networks and Client for Microsoft Networks. A word of caution though - if you are using network shares to store content skip this. Only perform this if you are sure that your Web Server is a stand-alone server.

Schedule Patch Management
Make a plan for patch management and stick to it. Subscribe to Microsoft Security Notification Service (http://www.microsoft.com/technet/security/bulletin/notify.asp) to stay updated on the latest release of patches and updates from Microsoft. Configure your server's Automatic Update to notify you on availability of new patches if you would like to review them before installation.

Run MBSA Scan
This is one of the best way to identify security issues on your servers. Download the Microsoft Base Line Security tool and run it on the server. It will give you details of security issues with user accounts, permissions, missing patches and updates and much more.

That's it to the basic of securing the operating system. There are more fixes which can be performed for further securing the server but they are beyond the scope of this article. Let's now move on to securing the IIS web server.

IIS 6.0 when setup is secured by default. When we say this, it means that when a fresh installation of IIS is done, it prevents scripts from running on the web server unless specified. When IIS is first installed, it serves only HTML pages and all dynamic content is blocked by default. This means that the web server will not serve or parse dynamic pages like ASP, ASP.NET, etc. Since that is not what a web server is meant to do, the default configuration is changed to allow these extensions. Listed below are some basic points that guide you to securing the web server further:

Latest Patches and Updates
Ensure that the latest patches, updates and service packs have been installed for .NET Framework. These patches and updates fix lot of issues which enhances the security of the web server.

Isolate Operating System
Do not run your web server from the default InetPub folder. If you have the option to partition your hard disks then use the C: drive for Operating System files and store all your client web sites on another partition. Relocate web root directories and virtual directories to a non-system partition to help protect against directory traversal attacks.

IISLockDown Tool
There are some benefits to this tool and there are some drawbacks, however, so use it cautiously. If your web server interacts with other servers, test the lockdown tool to make sure it is configured so that connectivity to backend services is not lost.

Permissions for Web Content
Ensure that Script Source Access is never enabled under a web site's property. If this option is enabled, users can access source files. If Read is selected, source can be read; if Write is selected, source can be written to. To ensure that it is disabled, open IIS, right click the Websites folder and select Properties. Clear the check box if it is enabled and propagate it to all child websites.

Enable Only Required Web Server Extensions
IIS 6.0 by default does not allow any dynamic content to be parsed. To allow a dynamic page to be executed, you need to enable the relevant extension from the Web Service Extensions property page. Always ensure that "All Unknown CGI Extensions" and "All Unknown ISAPI Extensions" are disabled all the time. If WebDAV and Internet Data Connector are not required, disable that too.

Disable Parent Paths
This is the worst of all and thanks to Microsoft, it is disabled in IIS 6.0 by default. The Parent Paths option permits programmers to use ".." in calls to functions by allowing paths that are relative to the current directory using the ..notation. Setting this property to True may constitute a security risk because an include path can access critical or confidential files outside the root directory of the application. Since most of the programmers and third-party readymade applications use this notation, I leave it up to you to decide if this needs to be enabled or disabled. The workaround to Parent Paths is to use the Server.MapPath option in your dynamic scripts.

Disable Default Web Site
If not required, stop the Default Web Site which is created when IIS 6.0 is installed or change the property of Default Web Site to run on a specific IP address along with a Host Header. Never keep it running on All Unassigned as most of the ready-made hacking packages identify a vulnerable web server from IP address rather than a domain name. If your Default Web Site is running on All Unassigned, it means that it can serve content over an IP address in the URL rather than the domain name.

Use Application Isolation
I like this feature in IIS 6.0 which allows you to isolate applications in application pools. By creating new application pools and assigning web sites and applications to them, you can make your server more efficient and reliable as it ensures that other applications or sites do not get affected due to a faulty application running under that pool.

Summary
All of the aforementioned IIS tips and tools are natively available in Windows. Don't forget to try just one at a time before you test your Web accessibility. It could be disastrous if all of these were implemented at the same time making you wonder what is causing a problem in case you start having issues.

Final tip: Go to your Web server and Run "netstat -an" (without quotes) at the command line. Observe how many different IP addresses are trying to gain connectivity to your machine, mostly via port 80. If you see that you have IP addresses established at a number of higher ports, then you've already got a bit of investigating to do.

Visit : All In Ones Printers Store