We have a windows 2008 r2 server and it is implement shares to 2 of our machines. The win 2008 r2 server does not do an DHCP role for now, the router is doing that for a while.
The problem is on the client, we point the DNS to the server so GPO's can work, but after a day the internet on the client goes down.
This is because I changed the DNS on the client from 192.168.1.1 (router) to 192.168.1.122 (server). I have read up on DNS issues and decided to add a forwarder on the servers DNS settings to our ISP IP address (which is static).
However I do not really want to place DHCP role on the server as yet, but do not want to move DNS back to 192.168.1.1, because the clients take ages to log in and the GPO's will not work.
What can I do to make sure that the Internet does not go down after a day? The main problem is the clients cannot resolve the routers DNS, even if I set it as alternative on the clients IP settings.
The problem is on the client, we point the DNS to the server so GPO's can work, but after a day the internet on the client goes down.
This is because I changed the DNS on the client from 192.168.1.1 (router) to 192.168.1.122 (server). I have read up on DNS issues and decided to add a forwarder on the servers DNS settings to our ISP IP address (which is static).
However I do not really want to place DHCP role on the server as yet, but do not want to move DNS back to 192.168.1.1, because the clients take ages to log in and the GPO's will not work.
What can I do to make sure that the Internet does not go down after a day? The main problem is the clients cannot resolve the routers DNS, even if I set it as alternative on the clients IP settings.
