5 replies
by venkat17 Accepted solution
by oh smeg Accepted solution
But assuming that is all OK and exceeds the needs of 2003 I would be looking for DNS conflicts on the network. ;)
Col
by venkat17 Accepted solution
by oh smeg Accepted solution
Also what is running as it starts?
I've seen a Server that was so underpowered and overworked that it took about 45 minutes to an Hour to start and probably another 35 minutes to shut down. But it was only a P4 CPU with 512 MEG of RAM and to make it a Server it had a RAID 1 Array.
In that case it had no where near enough System Resources for what it was being asked to run and they where loading well over 150 services when it started, so it took forever to shut down and restart. That's why they didn't bother turning it off ever.
But as a double check you could disconnect it from the Network and do some Diagnostics with something like the Ultimate Boot CD available free to download here
http://www.ultimatebootcd.com/download.html
You should check the Installed RAM, CPU and HDD's at the very least but I would also check the Network Connections for correct function. Not to mention opening the case and making sure that it's clean inside.
I've seen some really strange behavior with cases filled with gunk and other rubbish that has been sucked in over time. Slow starting is just one of the things that happens. ;)
Col
by seanferd Accepted solution
This ONLY in Forwarders, right? Your ISP's DNS server addresses should not be anywhere else.
Or are you saying you don't run a local DNS server at all in your network?
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending