Answered by:
SBS 2011 causing internet connectivity problems

-
We are running a new Lenovo ThinkServer with SBS 2011 Essentials for server software.
We just installed this a few days, and since then, we have been having internet problems. The router/modem shows that we are still connected to the internet, and we are able to access the internet, but each web page either loads very slowly, or fails to load the first time. Google Chrome gives us this message:
This webpage is not available
The server at www.paypal.com can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
After a refresh, it usually works. Any thoughts? We were not having this problem a few days ago with our older server.
Question
Answers
-
The command piped the results to the file c:\iptest.txt. You can open it with notepad and paste the results here. Just tell us which is the server and which is a station.
Windows networks are very dependent on DNS. But Essentials will accept the router for DNS, it uses some clever programing so the server/client and router all work together.
Here are some articles for your reading pleasure:
http://sbs.seandaniel.com/2011/06/basics-of-local-dns-for-small-business.html
http://blogs.technet.com/b/sbs/archive/2011/09/22/running-dhcp-server-on-sbs-2011-essentials-with-a-static-ip.aspx
If you don't find the answer there, look further in both blogs.
Larry Struckmeyer[SBS-MVP]
- Marked as answer by Andy QiMicrosoft contingent staff, Moderator Thursday, July 18, 2013 9:36 AM
-
On the Forwarders tab, all I see is "IP Address", and then beside it "Attempting to resolve.....unable to resolve"
In the Root Hints, I see a list of about 7-8 IP Addresses. I'm not sure what I should be adding to this list. IE. I don't know what ISP DNS is. I tried adding "8.8.8.8 + 8.8.4.4" here, but it wouldn't let me. It said it was invalid.
- Marked as answer by RyanSzu Thursday, July 04, 2013 11:01 PM
-
-
No, but they are far away from you, whereas the DNS servers of your ISP are closer. Besides, those numbers belong to Google and they track everything you do.
Protocol is that you should use the DNS servers of your ISP unless they are unreliable, as some are.
Larry Struckmeyer[SBS-MVP]
- Marked as answer by RyanSzu Thursday, July 04, 2013 11:01 PM
All replies
-
Hard to tell from this distance... <g>
Post up the output from the text file created by the command: ipconfig /all > c:\iptest.txt from both the SBS server and a workstation.
But, the basics are: The SBS should be the DHCP server, not the router, every nic settings should point to the IP of the SBS for DNS. You can check the DNS settings in start - administrator tools - DNS Server. When that opens, right click server name then click the tab for DNS forwarders. In there, and no where else on the network, you should find the ISP (or some known good DNS server) DNS settings.
The fix my network wizard should help you here. Also, run the SBS BPA and fix anything it finds. www.sbsbpa.com
Larry Struckmeyer[SBS-MVP]
-
Hi Larry,
Thanks for the reply. The command: ipconfig /all > c:\iptest.txt yielded nothing when I entered it in the "Run" space. The black command box appeared for half a second and then disappeared.When I opened the Administrator Tools > DNS Server > DNS Forwarders, some kind of network wizard was searching for a solution and then came back "unable to resolve".
I downloaded the SBS BPA, but the report came back with no errors.
The internet is working, albeit differently than before, needing a refresh on almost every page before it will work. For our network, all we want to do is file sharing, we do not want the server involved in our net connectivity. Is there a way to disable all DNS Server roles? I saw a Role page and was trying to stop all services related to web connectivity, but this didn't change anything.
Any ideas are appreciated.
Thanks,
Ryan
-
The command piped the results to the file c:\iptest.txt. You can open it with notepad and paste the results here. Just tell us which is the server and which is a station.
Windows networks are very dependent on DNS. But Essentials will accept the router for DNS, it uses some clever programing so the server/client and router all work together.
Here are some articles for your reading pleasure:
http://sbs.seandaniel.com/2011/06/basics-of-local-dns-for-small-business.html
http://blogs.technet.com/b/sbs/archive/2011/09/22/running-dhcp-server-on-sbs-2011-essentials-with-a-static-ip.aspx
If you don't find the answer there, look further in both blogs.
Larry Struckmeyer[SBS-MVP]
- Marked as answer by Andy QiMicrosoft contingent staff, Moderator Thursday, July 18, 2013 9:36 AM
-
Hi Larry,
If I ran it correctly, here are the 2 outputs.
WORKSTATION (CLIENT):
Windows IP Configuration
Host Name . . . . . . . . . . . . : LV-OFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 68-A3-C4-17-D3-5D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 64-31-50-35-DC-9F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ed49:ed1b:16ad:19de%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.65(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : July-03-13 10:40:07 AM
Lease Expires . . . . . . . . . . : July-05-13 10:40:06 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 308556112
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-3E-BF-93-64-31-50-35-DC-9F
DNS Servers . . . . . . . . . . . : 192.168.1.104
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : 68-A3-C4-17-D3-5C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{81E4EC0A-E4CA-40AD-9D18-54DD089BF8F6}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:8ce:2215:3f57:febe(Preferred)
Link-local IPv6 Address . . . . . : fe80::8ce:2215:3f57:febe%17(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{976653B8-2AED-476D-8BDB-48AE0EE9D4D1}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{39481B07-A644-4F6E-A190-EFF8C48F607C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : YesSERVER:
Windows IP Configuration
Host Name . . . . . . . . . . . . : LV-Server
Primary Dns Suffix . . . . . . . : Liquivision.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Liquivision.localEthernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
Physical Address. . . . . . . . . : 44-37-E6-BB-DF-12
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9941:272a:448e:99b7%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, July 03, 2013 2:02:38 PM
Lease Expires . . . . . . . . . . : Friday, July 05, 2013 9:49:53 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 239351782
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-5B-DB-AE-44-37-E6-BB-DF-12
DNS Servers . . . . . . . . . . . : ::1
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter isatap.{4B5EA38E-C6C8-4FA6-
B221-E81C10F21CBA}: Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : YesTunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes -
Ok, so far that looks OK. Now on the server start - admin tools - DNS Settings.
Right click server name, properties forwarders tab.
Either the DNS servers your ISP assigned you should be in that tap, or you should see a long list under "Root Hints". If only root hints are present, try adding the ISP's DNS settings under Forwarders.
If already there, verify they are correct, and/or try changing them to well known reliable DNS servers for this test. One such, but not the only, is 8.8.8.8 + 8.8.4.4
Larry Struckmeyer[SBS-MVP]
-
BTW, when time allows consider using a different internal IP. 192.168.1.x may cause you issues with VPN's should you every want/need one, and is too easy to guess from the brand of your router. Do something like 192.168.53.x or 153.x. Something not so obvious.
Larry Struckmeyer[SBS-MVP]
-
On the Forwarders tab, all I see is "IP Address", and then beside it "Attempting to resolve.....unable to resolve"
In the Root Hints, I see a list of about 7-8 IP Addresses. I'm not sure what I should be adding to this list. IE. I don't know what ISP DNS is. I tried adding "8.8.8.8 + 8.8.4.4" here, but it wouldn't let me. It said it was invalid.
- Marked as answer by RyanSzu Thursday, July 04, 2013 11:01 PM
-
-
-
No, but they are far away from you, whereas the DNS servers of your ISP are closer. Besides, those numbers belong to Google and they track everything you do.
Protocol is that you should use the DNS servers of your ISP unless they are unreliable, as some are.
Larry Struckmeyer[SBS-MVP]
- Marked as answer by RyanSzu Thursday, July 04, 2013 11:01 PM