Problem solve Get help with specific problems with your technologies, process and projects.

Why does my network go down every night?

Our networking fundamentals expert, Chris Partsenidis, explains why a network server might go down at a certain time every night, in this expert response.

During the day time my network works very smoothly, but after 6:30 in the evening it almost always goes down. We are not able to get the mapped drives on local machines and also we cannot save anything on our server. We have Dell PowerEdge 2800 Server with Microsoft 2003 as the operating system. We have recently put PIX Firewall 515 on the switch (D-link DES 3550). We have scanned all the machines with Trend Micro for viruses and found nothing. What do I do?
These types of problems can be somewhat difficult to resolve if there isn't enough information. I'd have to assume the PIX Firewall has been installed to protect your network from the public and acts as a gateway for your local network, so I doubt it would be the source of the problem. However, it would be a good idea to check the configuration with a Cisco engineer to ensure it's been configured properly.

In the meantime, I'd turn my eyes towards your Windows server for a number of reasons.

Firewall.cx logo

Do you have questions about networking, VPN security or VoIP? Then visit Firewall.cx, one of the few websites recommended by Cisco Systems in its world class Cisco Academy program.

You mentioned the server is running Windows 2003, which means that you've got Active Directory installed and this machine is acting as a primary domain controller (PDC). Due to its role, it's most likely acting as a master browser for your Windows network as well. This means that the server contains a view of the whole network, so other workstations consult it to find out what resources and machines are available. If for any reason your network's master browser goes down, these services are temporarily unavailable until a new master browser is elected.

The problems you are experiencing can be a combination of a Master Browser problem, and DNS services running on the Windows 2003 server.

My suggestion in such cases is to consult the server's event viewer and look for error messages that might give you a few clues as to where the problem is. Make sure you check all log files and use the Event ID number to consult Microsoft's support page (support.microsoft.com) as you're likely to find your solution there.

This was last published in April 2006

Dig Deeper on Network management and monitoring