Clients can connect to our server, but not to the Internet
Posted on 2014-04-30
We have just moved to a serviced office and are configuring our Domain Controller. The Server itself can connect to the Internet, and client computers are connecting to the server fine (e.g. I created a new user in AD, and that user was able to log onto a client PC). However, the client PCs do not connect to the Internet at all. Here is our setup:
The serviced office providers advised us that our Default Gateway IP is 10.182.212.113. They advised that the DNS Server is 126.96.36.199*. Our Scope is 10.182.212.114-126.
Therefore, I have gone to the Ethernet connection and changed the IPv4 settings. IP address (for the server) is set to 10.182.212.114, Subnet Mask is 255.255.255.240. Default Gateway is 10.182.212.113. Preferred DNS Server is 127.0.0.1 (though I have previously tried it at 10.182.212.114), while the alternate DNS Server is 188.8.131.52.
AD, DHCP and DNS have been installed on the DC. DHCP Scope has been configured so that it is 10.182.212.120-26.
Following some Googling, I have added a forwarder to the server in the DNS Manager which points to 184.108.40.206.
All this to no avail. While logged in as a user on the client network, I can ping to the DC, I can ping to the default gateway, but I can't get an Internet connection, even though the DC has an Internet connection. Any advice?
I'm not a server guy, I'm a business owner attempting to set up a relatively simple network for my new employees in a serviced office environment.
Thanks in advance!