1
I have a Windows Server 2008 R2 Domain Controller. I can RDP, ping, and access the webserver while in the local area network on the LAN NIC. But I cannot RDP, ping, or access the webserver while outside the network.
If I restart the server, however, I can do all 3 for a small period of time (about 2-3 minutes). After that, the server no longer responds to any requests.
I have made sure that all the correct ports are open and have even tried turning of the firewall: no luck.
Why would requests from the WAN not work while requests from the LAN are?
Devin
Posted 2012-10-09T00:15:36.573
Reputation: 11
Actually, VPN connection requests to the WAN work, but nothing else. – Devin – 2012-10-09T00:19:48.537
Does your service provider have port blocking in place? My theory goes like this, you get a new IP address when you shut off/turn back on the server, and it takes a minute for the network to engage port blocking for the new address (by using an IDS). Trying to use multiple different ports over a short period of time (a few minutes) may look like a scan and cause the system to defend your server. Or I'm completely wrong and it's internet gremlins. – Everett – 2012-10-09T04:59:52.590
Another option would be DNS configuration issue, unless you're doing everything by IP address (you don't mention either one). – Everett – 2012-10-09T05:02:46.393
The server operates on our University's network and has a static IP. The server is re-installed every semester and this is the first time I have had an issue like this. Could be DNS, as active directory automatically configures a DNS server. I don't know a lot about DNS though, so that may very well be where my issue lies. – Devin – 2012-10-09T17:24:10.850