i disagree with sdn421 - i run a commercial web platform with many (up to 100) web sites running from a single IP address with rarely any problem associated with doing that (almost never in fact - i can;t remember a ingle occasion that using a single ip address caused any problems)
my advice to try to diagnose the problem is to start by checking event log - is there anything useful in there?
next, try shutting down related services - wingate proxy? what port/s does it run on? i'd not be surprised if it were wingate grabbing your web port/s.
if you can do without wingate for a day, try running the server with wingate shut down, see if your IIS sites still crash. if you really must have wingate, run it on a spare computer for a while (if poss).
cheers.
Main Topics
Browse All Topics





by: sdn421Posted on 2002-08-28 at 08:03:19ID: 7246659
Using host headers to have multiple sites on a single machine is generally a bad idea. It can cause lots of different problems. Can you get more IP's? If so, it would probably be better to add those IP's to the server and then assign each IP to a website in IIS. You will also need to get your DNS updated so the names resolve to the new IP's. This might not fix your problem, but it probably be a good move for the future.
Good Luck!