I've migrated to Win2003 this week from WinNT. Besides it being nearly totally foriegn, I've got an issue with rebooting. When I have any clients plugged into my switch, the Server basically dies on a reboot. I cannot access the Internet, I can access the LAN, the Clients cannot access the server or Internet either. Same thing if I just plug the server from the switch. But, if I unplug all of the clients (I can leave the printers connected) and reboot, then everything is fat and happy. I can reconnect all of the clients, and go on my way. But this is extremely annoying with 23 clients connected. Anyone have experience with this issue. Do I have something configured incorrectly? Your help is always appreciated.

Just like I said before, setup DNS forwarding, have all your client workstations point to your new Server and have your 2003 server setup as a DNS forwarder to your ISP..

You will have to develop a test or tests to determine why it is rebooting. Use performance monitor, event viewer, task manager and dump messages to find out why it is crashing. Kind of odd that a connection to a dumb switch causes a reboot.

The don't think DNS forwarding is the issue. If I wait to plug in the items in to the switch after the reboot is completed, everything works fine. The switch is not making it reboot. I am doing in manually (after a program install, etc...), and running into the issue there. I've checked all available logs and have had no help through any of those. It shows that everything loaded properly on boot, and just fine on the exit. But leaving just 1 client machine plugged in, it'll hose both network connections (Internet and LAN). Also, if I unplug the server from the switch during a reboot, I get a similar response. So the server must be plugged into the switch, with no client machines plugged in to complete a good reboot. Could the switch software be gumming up the works? It's a 3-Com SuperStack II Your help is always appreciated.