none
WHS will not appear on my Network. Can only access by IP addres, but not server name. Help!!?? RRS feed

  • Question

  • My WHS machine was working just fine, but just recently it does not appear on my home network. I did not do anything to it, it just suddenly wont appear anymore. I cannot access it by name, only by IP address. Ive already did a server reinstallation and switched routers as well as ethernet adapters. Still no luck. The rest of the computers in my home network show up just fine. I am completely out of ideas. Strangely though, in the Network window, "Server" appears as a device, but I cannot access it. Here is a screenshot:

    http://i43.tinypic.com/2cx9b1t.jpg    (sorry, I dont know how to make it clickable)

    The only way to access is it to go to run > cmd > type in \\ip address, then all my shared network folders will be accessable.

    Any ideas?
    • Edited by dydx Saturday, July 4, 2009 11:58 PM
    Saturday, July 4, 2009 10:47 PM

All replies

  • My WHS machine was working just fine, but just recently it does not appear on my home network. I did not do anything to it, it just suddenly wont appear anymore. I cannot access it by name, only by IP address. Ive already did a server reinstallation and switched routers as well as ethernet adapters. Still no luck. The rest of the computers in my home network show up just fine. I am completely out of ideas. Strangely though, in the Network window, "Server" appears as a device, but I cannot access it. Here is a screenshot:

    http://img25.imageshack.us/i/24595580.jpg/     (sorry, I dont know how to make it clickable)

    The only way to access is it to go to run > cmd > type in \\ip address, then all my shared network folders will be accessable.

    Any ideas?

    First, the image isn't available.

    Can you ping your server, both by name and by IP address?  Can you open a command prompt and run ipconfig /all on one of your clients and your server (through Remote Desktop), and post the results here?
    Saturday, July 4, 2009 11:17 PM
    Moderator
  • Thanks for the quick reply. Ive updated the link to the screenshot above.

    After some more poking around, I think it may have something to do with the DNS not being able to resolve the name properly (not sure if this makes sense). The WHS connector does not work, but, Ive figure out that if I edit the hosts file in C:\Windows\System32\drivers\etc and add the line 192.168.1.119 Server #Windows Home Server, then the WHS connector will work and I will also be able to access \\Server (although it still does not appear in "Network"). I dont want to have to do this on every client, so maybe someone has any ideas or better explanation to what's going on?

    Here is the ipconfig on the server side:

    http://i39.tinypic.com/behcnp.jpg

    and the ipconfig on the client side:
    http://i39.tinypic.com/21tw8x.jpg

    also, here are my static IP settings:
    http://i39.tinypic.com/akdhrk.jpg

     
    Sunday, July 5, 2009 12:11 AM
  • I see your computers are configured to use your router as your local DNS server. Is your router by any chance configured to point to OpenDNS servers? If so, try setting it back to your ISP's DNS servers.
    I'm not on the WHS team, I just post a lot. :)
    Sunday, July 5, 2009 4:34 AM
    Moderator
  • Nope, I have not messed with any of the DNS settings in the router. It is all factory default. However, after doing some more reading, it seems like this is a fairly common problem which I suspect may potentially have something to do with DNS (which I really have no idea what DNS is). Common in the sense that there are a lot of others who have had to manually edit their hosts file in order to get WHS working.
    Sunday, July 5, 2009 4:47 AM
  • I think I may have found a solution. Just thought I would give an update. I went into the WHS machine and did a ipconfig /registerdns and that fixed the issue. My WHS now appears as a computer on my network.

    I hope Microsoft releases some sort of fix for this issue, it seems like alot of users are plagued by this problem as well and it can be frustrating. Modifying the hosts file might get everything working again, but when the time comes that a client requires to restore a machine, it wont work because the client wont be able to find the server on the network.
    Sunday, July 19, 2009 12:18 AM