Has anyone else had any strange network problems after the (apparently)
sucessful installation of SUS?
A client of mine has a Windows 2000 Server, with a mixture of Macs (these
are not used very much) and PC's, which use DHCP from the Netgear Router,
DNS from the W2K Server. A pretty straightforward setup you would think!.
After SUS was installed and got working about 5 weeks ago the users started
complaining of "not being able to see the server" and they rebooted the
server and it seemed to get them connected again. This started happening
about 4 or 5 tinmes a day apparently!
I looked at the server and could see no reason that the server would need a
reboot, and started looking towards the router.
I thought that I had diagnosed this down to a faulty router, since if the
router was restarted the users then could see the network (after a reboot of
their client PC's). A router replacement was installed and we all hoped this
was the end of it, but later on the same day I got a call saying the same
problem had ocuured, and could still be sorted by restarting the router, so
maybe the router was not at fault at all. (Or was it a faulty new one?)
There is nothing in the event logs, they are pretty clean about everything.
It was then suggested that maybe SUS was causing this, and could I stop
that? Since there are no other web applications I stopped the Default Web
Site in IIS, and lo and behold the problem went away.
I now need to get to the bottom of the problem so I can once again get SUS
working for them without causing network problems.
Any suggestions gratefully received
TIA
Simon
