|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Fouled up IIS 6
Hi, I was recently trying to configure IIS so that I could use server side includes, a task at which I was unsuccessful, but in the process I somehow managed to make //localhost or 124.0.0.1 inaccessible. I get the "Unable to connect" error.
Is there anyway to restore IIS to the default values, as I seem incapable of retracing the steps that led me to this dastardly situation. Thanks in advance, ![]() |
|
#2
|
|||
|
|||
|
btw localhost should be 127.0.0.1, not 124.x.x.x
Check the services and verify the www service is running, if not figure out why and get IIS restarted. Better is to visit the IIS manager and see the status. Look for any events in the event logs that may give a clue. Make sure you didn't enable some firewall or other blocking software that's blocking http. And if you installed some other web server while working make sure only one is running. If you don't have many webs, it may be easiest to completely uninstall IIS, reboot, then reinstall IIS, but I try to find and fix the exact problem rather than a shotgun approach whenever possible.
__________________
====== Doug G ====== "Hide, hide witch! The good folk come to burn thee. Their keen enjoyment hid behind their gothic mask of duty." -Mark Clifton |
|
#3
|
|||
|
|||
|
Thanks for the tips. I will try them tomorrow morning when I get to work. I will let you know the results. Thanks.
Oh, and the '124' thing was just a typo, but thanks for the catch. ![]() |
![]() |
| Viewing: Dev Shed Forums > System Administration > IIS > Fouled up IIS 6 |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|