SBS2011 Client machines randomly unable to get to external websites
Hi All,
I have done two Clean Installs on two new servers recently, one was my own and one is a customer, both are exhibiting the same problem.
At random times during the day some uses will go onto websites they have been on many times before and just get the usual webpage cannot be displayed.
Because this happens on my own network I have tried maually putting my routers IP address in the CLIENT machines DNS (ipv4) and this "Seems" to cure it.
My question is should I put my router IP address somewhere in the servers settings other than the wizzard used to setup the server in the first place? As a second DNS maybe?
Both servers seem in good health, they backup, they retrieve updates and everyone logs on without problem,
Both routers in both companies are Draytek 2820n and 2830n and I have used drayteks for years
I have done two Clean Installs on two new servers recently, one was my own and one is a customer, both are exhibiting the same problem.
At random times during the day some uses will go onto websites they have been on many times before and just get the usual webpage cannot be displayed.
Because this happens on my own network I have tried maually putting my routers IP address in the CLIENT machines DNS (ipv4) and this "Seems" to cure it.
My question is should I put my router IP address somewhere in the servers settings other than the wizzard used to setup the server in the first place? As a second DNS maybe?
Both servers seem in good health, they backup, they retrieve updates and everyone logs on without problem,
Both routers in both companies are Draytek 2820n and 2830n and I have used drayteks for years
Sushil Sonawane
Use default gateway your router ip address on the client side and server site in NIC card. In router dns setting use your isp provide dns IP address.
Hi,
The servers - What's the DNS Server setup?
Open the DNS server and right click on the server select properties
Select the Forwarders tab
The DNS server Forwarders can be what your ISP provides or you can use something like google's DNS server 8.8.8.8
Once you have the DNS settings as they should be you can use the monitoring tab and test the DNS
The check your DHCP server. You did not say where you are getting DHCP from (I always usw the router / firewall rather than the WIndows server)
First DHCP server should the the SBS server the second can be the Draytek or a real DNS server on the Internet.
That should sort the DNS for the clients.
Regards
Gordon
The servers - What's the DNS Server setup?
Open the DNS server and right click on the server select properties
Select the Forwarders tab
The DNS server Forwarders can be what your ISP provides or you can use something like google's DNS server 8.8.8.8
Once you have the DNS settings as they should be you can use the monitoring tab and test the DNS
The check your DHCP server. You did not say where you are getting DHCP from (I always usw the router / firewall rather than the WIndows server)
First DHCP server should the the SBS server the second can be the Draytek or a real DNS server on the Internet.
That should sort the DNS for the clients.
Regards
Gordon
seems your DNS box isn't able to get you the data that you want, which box is your DNS pointing to for name resolution.
You could either point your client machine directly to your ISP and avoid your DNS, while this may work 100% for your internet sites, this would cause issues for your internal server name resolution.
OR you could fix the issue with your DNS, cause pointing your client machine to router is never a recommended solution. if this was the solution, MS never would have created the concept of DNS forwarders or root-hints.
Regards,
Exchange_Geek
You could either point your client machine directly to your ISP and avoid your DNS, while this may work 100% for your internet sites, this would cause issues for your internal server name resolution.
OR you could fix the issue with your DNS, cause pointing your client machine to router is never a recommended solution. if this was the solution, MS never would have created the concept of DNS forwarders or root-hints.
Regards,
Exchange_Geek
ASKER
Dear Exchange_Geek
The NIC card on both servers were only pointing to themselves, I have added the router IP address as a second DNS now, I hope that was what you were suggesting?
Because this is intermittant it may take a couple of days to see the results
The NIC card on both servers were only pointing to themselves, I have added the router IP address as a second DNS now, I hope that was what you were suggesting?
Because this is intermittant it may take a couple of days to see the results
ASKER
Hi FdpxAP-GJL
Both servers were only pointing at themselves for DNS, I have added the router as a second DNS on the nic card in the servers to see if this works.
I have always been unsure as to which device (server or router) its best to use for DHCP, but interestingly my system is set by the Server and on my customers LAN its set by the Draytek router, I guess that as we are both having the same problem that the DHCP is NOT the cause, is that a fair assumption?
Both servers were only pointing at themselves for DNS, I have added the router as a second DNS on the nic card in the servers to see if this works.
I have always been unsure as to which device (server or router) its best to use for DHCP, but interestingly my system is set by the Server and on my customers LAN its set by the Draytek router, I guess that as we are both having the same problem that the DHCP is NOT the cause, is that a fair assumption?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Exchange_Geek
Thanks for that, I have added both the ISP's and 8.8.8.8 to both machines forwarders,
Next week will be a good test, thanks
Thanks for that, I have added both the ISP's and 8.8.8.8 to both machines forwarders,
Next week will be a good test, thanks
Wonderful. All the best.
Regards,
Exchange_Geek
Regards,
Exchange_Geek