locked
Problem connecting to WHS on laptop RRS feed

  • Question

  • Hi,

    I am a long time WHS user, since first public Beta.  Always been an excellent product with no real problems.  Well I am now having an unusual problem I can't figure out.

    I can access my WHS on all computers except one laptop.  I have been able to for the past four months without issue until the other day.  What I can't figure out is that the laptop still can run a backup, but it is not able to login to the console or even see the shared folders on server.  The server does appear in the network discovery, however, when I click on the server icon, the webpage is unavailable and IE gives me the usual check internet, DNS is not reachable, etc.

    When I try to log-in via console, it says "This computer cannot connect to your home server.  Check your network connection and make sure the home server is powered on.  If you home server has recently restarted, try again in a few minutes."

    When I click on the Shared Folders on Server shortcut on the desktop, it says "Network Error: Windows cannot access \\SERVER  check spelling of the name.  Otherwise there might be a problem with your network...click to diagnose."  When I diagnose I get a " "SERVER" is not a valid host name" message.

    Now, like I said I can access the WHS on all other PCs in house (other laptop, desktop and media center).

    The laptop in question is running Vista Home Premium SP1, all up to date.  I have even reinstalled the connector software from the server (via USB drive since I could not access server) and reinstalled OK, Found server during install, shows completed OK, just as it always has in the past.

    Restarting Server does not help.  WHS is up to date.

    Any ideas?

    Thanks in advance!
    Saturday, February 21, 2009 5:16 PM

Answers

  • Well I restored the laptop to a week ago and the problem is gone.  Still no idea what caused the issue.  The only network related incident between when it was fine and when it stopped working correctly was connecting to two public wifi spots.

    I appreaciate everyone's help and suggestions.

    Thanks!
    Monday, February 23, 2009 12:55 AM

All replies

  • It sounds like a name resolution issue to me. Has anything been changed on your network recently? On the computer having a problem? From the computer having a problem, you could try pinging the server by name and by IP address, then try the same from another computer. If you can ping it by IP address but not name, that's another indication of name resolution problems on your network.
    I'm not on the WHS team, I just post a lot. :)
    Saturday, February 21, 2009 5:19 PM
    Moderator
  • Hi Ken,

    Thanks for the quick reply.

    I was able to ping via IP but not by name.  I could ping both on my desktop machine.

    There have been no recent changes to my network or any problems on the laptop.

    If this is a naming problem, any ideas on how to correct?  I'm confused since the name is the same and working fine on the other machines.

    Thanks again!
    Saturday, February 21, 2009 5:58 PM
  • bw8755 said:

    Hi Ken,

    Thanks for the quick reply.

    I was able to ping via IP but not by name.  I could ping both on my desktop machine.

    There have been no recent changes to my network or any problems on the laptop.

    If this is a naming problem, any ideas on how to correct?  I'm confused since the name is the same and working fine on the other machines.

    Thanks again!


    You might try flushing the DNS list from the client that doesn't work.  From a cmd prompt type:

    ipconfig /flushdns

    Saturday, February 21, 2009 10:15 PM
    Moderator
  • Thanks for the suggestion Kariya21, unfortunately, that did not work.  Still can ping via IP but not name. 
    Saturday, February 21, 2009 10:18 PM
  • Here's something else I found.  If I right-click on the WHS connector icon and select "Shared Folders" I get a WHS Connector message "Cannot open Windows Home Server shares.  Please check the access permissions and try again."
    Sunday, February 22, 2009 12:14 AM
  • bw8755 said:

    Thanks for the suggestion Kariya21, unfortunately, that did not work.  Still can ping via IP but not name. 


    Can you run ipconfig /all from both the client that doesn't work as well as one that does, then post both of them here?
    Sunday, February 22, 2009 12:22 AM
    Moderator
  •  Here you go:

    From Laptop that will not access Server:

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Brian>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Brian-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Peer-Peer
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Wireless LAN adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
       Physical Address. . . . . . . . . : 00-21-5D-2F-2A-F4
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::b462:e59c:6309:9072%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.190(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Saturday, February 21, 2009 6:41:32 PM
       Lease Expires . . . . . . . . . . : Sunday, February 22, 2009 6:41:32 PM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Bluetooth Network Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 00-22-69-D8-F0-E5
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-13-77-AC-28-0A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{FC3A0F40-7CC9-4D17-A2F2-826F050DA
    C01}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{88B1650C-9DBA-4DD3-8303-7DFF51835
    262}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{A9AAD2CD-5386-40A6-913F-FCDEABCAD
    D11}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 13:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:ce9:3521:3f57:ff41(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::ce9:3521:3f57:ff41%14(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 14:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : 6TO4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Brian>




    From Desktop that works correctly:

    Microsoft Windows [Version 6.0.6000]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Brian>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Brian-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2
       Physical Address. . . . . . . . . : 00-17-31-BB-5D-73
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
       Physical Address. . . . . . . . . : 00-17-31-BB-54-DA
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::c99c:b0d1:6cad:fcf2%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.197(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Thursday, February 19, 2009 3:48:31 PM
       Lease Expires . . . . . . . . . . : Sunday, February 22, 2009 3:48:30 PM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 201332529
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{52294642-8BCA-4C7F-9185-C68DA7684
    56A}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:2c49:1b9e:b91f:c62d(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::2c49:1b9e:b91f:c62d%10(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{0E7FEAF0-BC05-452E-A1B4-D96FADF21
    DDC}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 10:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{52294642-8BCA-4C7F-9185-C68DA7684
    56A}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 13:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{52294642-8BCA-4C7F-9185-C68DA7684
    56A}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.197%19(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Brian>



    Thanks!
    Sunday, February 22, 2009 1:17 AM
  • It looks like your problem PC is not using NetBIOS for name resolution. If NetBIOS is turned off on a computer for some reason, it will use WINS, and if there's no WINS server, name resolution will fail.

    Please make sure that NetBIOS over TCP/IP is enabled on the computer you're having trouble with (this is for XP; the operations are basically the same for Vista):
    • Open the Network Connections folder.
    • Right click the network connection that's active and select Properties from the context menu.
    • Double click the TCP/IP protocol; you want the v4 protocol if both v4 and v6 are listed.
    • Click the Advanced button.
    • Select the WINS tab.
    • Click the Enable NetBIOS over TCP/IP radio button and confirm your way back out.


    I'm not on the WHS team, I just post a lot. :)
    Sunday, February 22, 2009 3:49 AM
    Moderator
  • Hey Ken,  Just did that but still have the same issue.

    Sunday, February 22, 2009 3:59 AM
  • I just thought of something, I don't think it's much but thought I'd mention it.  Over the past few days I was on two public wifi networks.  Could something have changed when I connected to those that is now affecting my network connection on the laptop?

    Also, I did try connecting to my router wired, but had the same results.
    Sunday, February 22, 2009 4:08 AM
  •  Any other ideas to try?  I'm debating on doing a restore from about a week ago, to which I know I didn't have this issue.  Does this sound like the next best step?

    Thanks
    Sunday, February 22, 2009 4:24 PM
  • Well I restored the laptop to a week ago and the problem is gone.  Still no idea what caused the issue.  The only network related incident between when it was fine and when it stopped working correctly was connecting to two public wifi spots.

    I appreaciate everyone's help and suggestions.

    Thanks!
    Monday, February 23, 2009 12:55 AM