locked
Network problems... can't find WHS on network please help! RRS feed

  • Question

  • I'm at a loss. My WHS setup has been running flawlessly for a long time, but last week it stopped working and I can't find out what's wrong.

    Setup:
    * WHS (SP2) connected wired to broadbandmodem
    * Macbook (OS-X and Vista Home Premium) connects wirelessly to same broadbandmodem
    * Logitech Squeezebox connects wirelessly to broadbandmodem
    * All necessary ports are forwarded through the firewall

    What I can't figure out is why none of the computers can't find the WHS on the network when I use the wifi connection and they do seem to find each other when I use a wired connection for both computers.

    When I try to open the WHS console from Vista while I use the wireless connection on my macbook Vista reports it can't find the WHS. (grey icon) When I plug in my network cable the icon turns to green and it even updates my connector software. Same thing happen when using Remote desktop. Wireless connection: WHS can't be found. Wired connection: no problem.

    When I go through my .homeserver.com domain everything works a okay....


    What I've tried:
    * Replaced network cable - didn't work
    * Rebooted WHS - didn't work
    * Gave WHS a static IP - didn't work
    * Disabled firewalls on modem and WHS - didn't work
    * Followed the FAQ steps to connect to WHS if it's on a different subnet - didn't work
    * Ran connector trouble shooter - passed all tests (when notebook uses wired connection)
    * Shouted at the box - you guessed... didn't work

    I've ran the ipconfig /all command on both the Vista machine (wired/wireless) and the WHS. I'll append the output. Any help is much appreciated. Thanks!

    Robbert


    Ipconfig WHS

    Host Name . . . . . . . . . . . . : XXXX
  
    Primary Dns Suffix  . . . . . . . :
  
    Node Type . . . . . . . . . . . . : Unknown
  
    IP Routing Enabled. . . . . . . . : No
  
    WINS Proxy Enabled. . . . . . . . : No

    Connection-specific DNS Suffix  . :
  
    Description . . . . . . . . . . . : Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
  
    Physical Address. . . . . . . . . : XXXXXXXXX
  
    DHCP Enabled. . . . . . . . . . . : Yes
  
    Autoconfiguration Enabled . . . . : Yes
  
    Default Gateway . . . . . . . . . : 192.168.0.1
  
    DHCP Server . . . . . . . . . . . : 192.168.0.1
  
    DNS Servers . . . . . . . . . . . : 213.46.228.196
                                      
    62.179.104.196

    Ipconfig Vista wireless network connection
    Connection-specific DNS Suffix  . :
  
    Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
  
    Physical Address. . . . . . . . . : XXXXXXXXXX  
    DHCP Enabled. . . . . . . . . . . : Yes
  
    Autoconfiguration Enabled . . . . : Yes
  
    Link-local IPv6 Address . . . . . : XXXXXXXXXX(Preferred)
  
    IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
  
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
  
    Lease Obtained. . . . . . . . . . : zaterdag 20 december 2008 12:41:46
  
    Lease Expires . . . . . . . . . . : zaterdag 27 december 2008 13:02:03
  
    Default Gateway . . . . . . . . . : 192.168.0.1
  
    DHCP Server . . . . . . . . . . . : 192.168.0.1
  
    DNS Servers . . . . . . . . . . . : 213.46.228.196
                                      
    62.179.104.196
  
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ipconfig Vista wired network connection
       Connection-specific DNS Suffix  . :
  
    Description . . . . . . . . . . . : Marvell Yukon 88E8058 PCI-E Gigabit Ether
net Controller
  
    Physical Address. . . . . . . . . : XXXXXXXXX
  
    DHCP Enabled. . . . . . . . . . . : Yes
  
    Autoconfiguration Enabled . . . . : Yes
  
    Link-local IPv6 Address . . . . . : XXXXXXXX(Preferred)
  
    IPv4 Address. . . . . . . . . . . : 192.168.0.16(Preferred)
  
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
  
    Lease Obtained. . . . . . . . . . : zaterdag 20 december 2008 12:47:57
  
    Lease Expires . . . . . . . . . . : zaterdag 27 december 2008 13:47:56
  
    Default Gateway . . . . . . . . . : 192.168.0.1
  
    DHCP Server . . . . . . . . . . . : 192.168.0.1
  
    DNS Servers . . . . . . . . . . . : 213.46.228.196
                                      
    62.179.104.196
  
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Saturday, December 20, 2008 2:36 PM

Answers

  • Hi Olaf,

    Thanks for taking the time to reply. Much appreciated! I tried the proposed solution but it didn't work. With some help from the people at the Wegotserved forum I found out what was wrong: the firmware in the Thomson modem/router. They 'updated' mine with older firmware which causes/caused this situation. They assured me that a new firmware version will be available soon. So let's pray ;)

    Again... thanks and take care!
    • Marked as answer by Punkmachine Sunday, December 21, 2008 12:55 PM
    Sunday, December 21, 2008 12:55 PM

All replies

  • Hi Robbert,
    broadbandmodem = router?
    Try to change the DNS server IP address setting in the DHCP settings  to the address of your router 192.168.0.1 (on the server also enable NetBIOS over TCP IP on the WINS tab of Advanced TCP/IP properties and reboot both the client and the server. Validate, if ipconfig /all shows the proper DNS server now. Be a bit patient for the time it needs to build up the NetBIOS name resolution on the browse master after reboot.

    (It does currently point to an external DNS server directly, which may cause the client to try resolving the home server name there.)

    In a short attempt you can try also, if pulling the Internet connection cable from the router helps to solve the issue.
    Best greetings from Germany
    Olaf
    Saturday, December 20, 2008 5:30 PM
    Moderator
  • Hi Olaf,

    Thanks for taking the time to reply. Much appreciated! I tried the proposed solution but it didn't work. With some help from the people at the Wegotserved forum I found out what was wrong: the firmware in the Thomson modem/router. They 'updated' mine with older firmware which causes/caused this situation. They assured me that a new firmware version will be available soon. So let's pray ;)

    Again... thanks and take care!
    • Marked as answer by Punkmachine Sunday, December 21, 2008 12:55 PM
    Sunday, December 21, 2008 12:55 PM