• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 517
  • Last Modified:

Windows Server 2008 R2 - Intermittent client internet access

I have recently setup my office Windows Server 2008 R2 and everything seems to be working fine apart from that the clients internet access is intermittent.

For some reason, nearly every morning users don't have internet access on their network computers. I then restart the server and their internet access is restored.

I am using my server as a proxy server and I am serving my client computers with internet access via 'Routing and Remote Access'.

The LAN IP range is 10.10.10.0 /8
The WAN IP range is 192.168.1.3 /24

Any assistance would be greatly appreciated.

Let me know if you require any additional information.
0
clictime
Asked:
clictime
  • 2
1 Solution
 
teletechtoddCommented:
How is the network configured- Is the server handing out DHCP? I am guessing the server get address automatically on WAN port and that is connected to comcast modem, seeing the scheme on the WAN. If not, what device is in place as your modem/router upstream of the server? Are you really using the server as a proxy or just using routing and renmote access to serve DHCP and using the server as a router? I have seen where the server DHCP service does not work properly and the PCs behind it are not getting an IP address from it.
0
 
clictimeAuthor Commented:
The server is acting as a DHCP server and the default gateway, DHCP server, DNS server on the client pcs are all pointed to 10.10.10.1 which is the IP address of the server.
0
 
teletechtoddCommented:
my bad. I got the ranges mixed. So 192.168.1 is your "public" range to the server and 10.10.10 is the private range..

What is the servers gateway, 192.168.1.1? When the server hads out DHCP are the PCs getting DNS of 10.10.10.1, 192.168.1.1 or the public DNS of your ISP?

When one of the PCs looses internet, the test should go as follows (folloiwng the route to internet):
from PC:
1. ping PC gateway address (10.10.10.1)
2. ping server WAN address (192.168.1.3)
3. ping server gateway address (192.168.1.1)
4. ping internet address (8.8.8.8)
This will tell where the connectivity issue lies. If all pings successfull, verify DNS:
type nslookup,
type the name of a website i.e. yahoo.com, and see if the PCs DNS server will resolve the name to an IP address. If that does not work then it is definitely a DNS issue and not connectivity. Try setting the PC to use a different DNS server such as a global 8.8.8.8 server and test again.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now