locked
WHS v1 **no longer** visible on my home network RRS feed

  • Question

  • I've had an HP Home Server for just over a year and for the most part it has run very well. In the past two weeks something has gone strangely wrong. One day mid-backup the system just fell off our home network. Here's what I know:

    Equipment:

    - Server: Windows Home Server SP 2, running on HP E5200

    - Other machines:

    • 2 x Windows 7 Laptops (Dell XPS m1530 and Dell XPS L501x), running Ultimate and Professional
    • 1 x Windows Vista laptop (older Dell Inspirion) 
    • Macbook Air (doesn't even speak to the Home Server)
    • SqueezeBox - our music system

    - Router: DLink Dir-615 - it appears to have no real DNS capacity, instead it just forwards to the ISP

    Underlying problem

    I can ping the home server via its IP address and even remote desktop to it. But I can't get to it by name. 

    I've spent sometime studying: http://blogs.msdn.com/b/eldar/archive/2007/04/28/windows-home-server-client-join-troubleshoooting-hints.aspx and clearly I have a name resolution problem. However all the other PC's see each other so I would think that the PC to PC name resolution (via UPNP) isn't blocked.

    So I'm confused. What do you think happened? How do debug it? How can I get it to work again without resorting to host files which will leave the Squeezebox in the cold? 

    Any thoughts?

    Cheers

    Mark Levison

     

     


    Blog: http://www.notesfromatooluser.com
    Friday, September 23, 2011 1:55 AM

All replies

  • I should add although I don't seem to be able to configure the router's dns implementation when I run ipconfig /all in this machine it reports the DNS is: 192.168.0.1 so in theory the router should be handling things.

    Very confused in Ottawa

    Mark Levison


    Blog: http://www.agilepainrelief.com/
    Friday, September 23, 2011 2:02 AM
  • Yes, probably it's a name resolution error. Do you use a third party DNS provider? Do you know if your ISP does? Those can sometimes cause issues, though Microsoft released an update quite a while back which helped resolve this for clients of the server (i.e. computers with the connector installed). That update won't help your Macbook or your Squeezebox, I'm afraid.
    I'm not on the WHS team, I just post a lot. :)
    Friday, September 23, 2011 1:22 PM
    Moderator
  • Try doing IPCONFIG /FLUSHDNS on the server and all the clients. This will flush the local DNS caches. I also suggest rebooting your router.
    qts
    Friday, September 23, 2011 1:31 PM
  • Hmmm it gets more interesting. It would appear the laptop I'm using right now is the only one that can't see the homeserver. I will start a new thread.
    Blog: http://www.agilepainrelief.com/
    Tuesday, October 11, 2011 4:25 PM
  • Are you connecting the laptop via wireless?  Have you got the WHS ports blocked on the router?
    qts
    Thursday, October 13, 2011 3:26 PM