Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Everything was working fine yesterday, but this morning when I walked in only a computer that was in my firewalls DMZ was able to locate the server. None of the other computers can resolve the FQDN of the server and attempting to ping the IP returns timed out. When I attempt to ping any device on the intranet, the server returnes with "General Error"

share|improve this question
You need to provide more information about your network layout. Did you check the physical layer? NIC, ethernet cables, etc? – Quinten Jul 27 '11 at 17:56
"What Changed?" -- Do not say "Nothing". – voretaq7 Jul 27 '11 at 18:05
Everything on the physical level is connected and "working". Its a rather small network in which the Server and workstations are connected through an 8-port Netgear firewall. The only thing that has changed is I have been attempting to set up a VPN and went into the firewall to forward the necessary ports to the Server. – c.patterson Jul 27 '11 at 18:53

Could be a physical or data link layer problem. I've had switches that failed overnight to auto-negotiate a link speed and provided a half on-half off kind of connection (24 port Linksys Gbit switch). Causes very weird problems.

If you can load websites that aren't cached, your server is obviously able to use its routing table, and takes you through some gateway (all routes will be used for that purpose by your server) to transfer data. Also, this proves that some form of DNS is working. Unless you have a proxy server set up, in which case that server will do all the work for you.

Not being able to ping your gateway from different computer would mean that the gateway could have a problem.

Also, don't forget: if you have a DHCP server or client messing up, you could possibly have an IP address conflict, those can be VERY hard to diagnose. Check for this. I have a Seagate GoFlex Home network attached drive that somehow manages to get the wrong ip-address assigned every single time.

share|improve this answer
C.patterson, usually you can't just 'forward' VPN 'ports' since IPsec, L2TP and PPTP don't have any ports. Did you use the appropriate VPN passthrough options of the router? – Jacob Jul 28 '11 at 14:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.