locked
WHS Server Cannot Access Internet RRS feed

  • Question

  • Despite what I naively believe to be diligent efforts, I've been unable to identify the reason that my WHS server no longer can access the internet.  (Unfortunately, I can't associate the problem with any particular system/configuration change as it went unnoticed for many months.)  Just to be clear - I'm talking about basic internet access to receive WHS and antivirus updates - I am NOT trying to configure remote access or a network home page as my ISP precludes server use (sigh). 

    Background:
         Wired & wireless home network with apparent good connectivity across network.
         Backups and RDP from all clients to Server work fine...
         Other network clients all have full internet access.
         Server IP is DHCP assigned via a static reservation in the Verizon router.  (I've also experimented with a static address on the Server side with the same non-results.)  Current IPCONFIG/ALL results for my Server are reproduced below:  (bolding added)

    Windows IP Configuration  [Server]
       Host Name . . . . . . . . . . . . : HPSERVER-DAVIS
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : SiS191 1000/100/10 Ethernet Device
       Physical Address. . . . . . . . . : (masked for security)
      
    DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
      
    IP Address. . . . . . . . . . . . : 192.168.1.254
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       Lease Obtained. . . . . . . . . . : Sunday, January 02, 2011 6:18:41 AM
       Lease Expires . . . . . . . . . . : Monday, January 03, 2011 6:18:41 AM

    The Server can successfully ping other home network clients and the router/gateway.  When attempting to ping internet addresses, however, it appears to resolve the IP properly but times out (on the return path?).  See results of Server ping to www.google.com below:

    Pinging www.l.google.com [74.125.227.20] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 74.125.227.20:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    NSLookup confirms that the DNS (via the router IP) is resolving properly.  Thus, the problem acts like a router or firewall inbound configuration issue but the other clients successfully use the same router IP (192.168.1.1) as the Gateway and DNS Server without any trouble (see Sample Client ipconfig/all below)

    Windows IP Configuration [Sample Client]    

    Host Name . . . . . . . . . . . . : Bart-HP
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home

    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Intel® 82567V-2 Gigabit Network Connection
       Physical Address. . . . . . . . . : 00-26-18-8E-14-2D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::25ff:4e3c:1f5b:268%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Friday, December 31, 2010 12:13:23 PM
       Lease Expires . . . . . . . . . . : Sunday, January 02, 2011 8:57:34 PM
      
    Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 234890776
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7E-1D-07-00-26-18-8E-14-2D
      
    DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.home:
    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 . . . . : Yes

    Tunnel adapter Local Area Connection* 11:    

    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:4137:9e76:24c3:b43:9f1d:5ee2(Preferred)
       Link-local IPv6 Address . . . . . : fe80::24c3:b43:9f1d:5ee2%13(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    The "route print" command on the Server produces the following result:

    IPv4 Route Table

    ===========================================================================

    Interface List

    0x1 ........................... MS TCP Loopback interface

    0x10003 ...00 0a e4 85 af 1c ...... SiS191 1000/100/10 Ethernet Device

    ===========================================================================

    ===========================================================================

    Active Routes:

    Network Destination        Netmask                          Gateway               Interface                            Metric

     0.0.0.0                                0.0.0.0                             192.168.1.1         192.168.1.254                     20

    127.0.0.0                            255.0.0.0                         127.0.0.1              127.0.0.1                              1

    169.254.0.0                       255.255.0.0                     192.168.1.254    192.168.1.254                     30

    192.168.1.0                       255.255.255.0                 192.168.1.254    192.168.1.254                     20

    192.168.1.254                   255.255.255.255            127.0.0.1             127.0.0.1                              20

    192.168.1.255                   255.255.255.255            192.168.1.254    192.168.1.254                     20

    224.0.0.0                            240.0.0.0                          192.168.1.254    192.168.1.254                     20

    255.255.255.255               255.255.255.255            192.168.1.254    192.168.1.254                     1

    Default Gateway:       192.168.1.1

    ===========================================================================

    Persistent Routes:

    None

     

    I'm pulling my hair out over this as I'm sure it's something really stupid on my part...  Any ideas or additional troubleshooting suggestions would be greatly appreciated.

    • Edited by AE5JD Wednesday, January 5, 2011 2:14 AM Add'l info...
    Tuesday, January 4, 2011 10:43 AM

Answers

  • This is now resolved - although it's still not clear EXACTLY what was preventing the Server internet connection, removal of the static IP reservation in the Router DHCP permitted the connection.  Now I'm just specifying a static IP on the Server itself and all is well... 
    • Marked as answer by AE5JD Saturday, January 8, 2011 11:09 PM
    Saturday, January 8, 2011 11:09 PM