Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Networking problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am not sure what happened, but my home network has gone mad.

    I am sort of new to servers and networking stuff, but I was able to follow instructions and setup WHC with LAMP and SAMBA servers using virtual pc 2007 and ubuntu and it was working well. and then out of nowhere I started to have problems.

    Here are my problems: Not sure what's going on.

    On my XP pro client computer to WHS:
    I can't access anything on internet such as (www.google.com).
    I can access WHS default page by 192.168.1.2 but i can't access it thru microsoft i.e. davidnjina.homeserver.com
    I can access homepage on Linux virtual machine by 192.168.1.10 but I can't access via internet davidnjina.homelinux.com/personal
    WHC console is green and I can connect to WHC. I have all access to shared folders on WHC.
    I can't access my router 192.168.1.1 from this computer.

    From any other computer on the network,

    By the way, all these were working perfectly last night.

    The funny thing is when I use MS diagnostic, it said that 192.168.1.2 (WHS) was unreachable via port 80, 8080, 443 and a few others I can' remember.

    FYI, I have NETGEAR WPN824 v2 router. I've forward port 80 to WHS and 8080 to virtual linux. In my router admin page, I see the 192.168.1.19 (XP computer I am having problem with), but it's name isn't listed unlike other connected computers.

    After seeing these problem, I wanted to restore my XP to a backup I saved couple days ago. The restore CD loads and it says that I have a handful network service (or folders I don't remember exactly), but then it can't find WHC. I try to do it manually and it says I have no network.


    Can you comment on how I might resolve my problem? What I mentioned above was all working fine last night.

    Thanks in advance.

    Davd

    Tuesday, January 6, 2009 6:43 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    if I am understanding correctly, you have virtualized parts of your network? You should be aware that this is an unsupported scenario for Windows Home Server. That's not to say it won't work (and I usually prefer to "test to destruction' in a virtual environment), but it represents a much more advanced technical capability than the target audience for WHS is expected to have. You really should not host your server in a virtual environment, use your server as a virtual machine host, or join "clients" which are vitrual machines to your server.

    That said, the issue you describe seems to point to a name resolution issue. You can test this further: try to ping each machine on your network from each other machine, both by name and by IP address. You can try turning off name servers (NetBIOS, DNS, WINS, etc.) on any of your computers (particularly the Linux machine/VM), pointing all your computers to your router as their default name server, and let your router forward requests it can't resolve.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, January 7, 2009 12:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    nymphaeles said:

    1)  investigate and find out what network card you have in the PC:  go to system property, hardware, device manager, network adapters
    2)  down load and decompress the network driver on to a USB thumb drive.

    Windows Home Server collects drivers for certain critical hardware (storage controllers, network adapters) as part of every backup. To load drivers for a computer you want to restore:
    1. On any computer on your network which is joined to the server, start the WHS console.
    2. Open a backup for the computer you want to restore.
    3. In the root of the backed up C: partition, you will find a folder "Windows Home Server Drivers for Restore". Copy that entire folder to a flash drive.
    4. Boot the computer you want to restore using the Restore CD.
    5. When asked for drivers, use the flash drive you've loaded the drivers on.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, January 7, 2009 12:23 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Not sure where you you want to start?  Do you want to
    1)  Restore from backup? --> troubleshoot the "WHS not found"   OR
    2)  Troubleshoot the issues with your network.  --> will need more info
    No sweat :)
    Tuesday, January 6, 2009 8:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I think if I can restore the network then restoring backup will be easy. I can't restore my pc without fixing the network problem. Any suggestion would be appreciated.

    David
    Tuesday, January 6, 2009 8:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If you need to restore your PC, start with
    1)  investigate and find out what network card you have in the PC:  go to system property, hardware, device manager, network adapters
    2)  down load and decompress the network driver on to a USB thumb drive.
    3)  booting your PC from a Home PC Restore CD.
    4)  select to install network card driver
    5)  if you have the correct network card driver, the restore will find your Windows Home Server and ask for password.
    6)  Restore your PC from the date you know your PC was working OK.
    Post your feedback here....
    Wednesday, January 7, 2009 4:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    if I am understanding correctly, you have virtualized parts of your network? You should be aware that this is an unsupported scenario for Windows Home Server. That's not to say it won't work (and I usually prefer to "test to destruction' in a virtual environment), but it represents a much more advanced technical capability than the target audience for WHS is expected to have. You really should not host your server in a virtual environment, use your server as a virtual machine host, or join "clients" which are vitrual machines to your server.

    That said, the issue you describe seems to point to a name resolution issue. You can test this further: try to ping each machine on your network from each other machine, both by name and by IP address. You can try turning off name servers (NetBIOS, DNS, WINS, etc.) on any of your computers (particularly the Linux machine/VM), pointing all your computers to your router as their default name server, and let your router forward requests it can't resolve.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, January 7, 2009 12:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    nymphaeles said:

    1)  investigate and find out what network card you have in the PC:  go to system property, hardware, device manager, network adapters
    2)  down load and decompress the network driver on to a USB thumb drive.

    Windows Home Server collects drivers for certain critical hardware (storage controllers, network adapters) as part of every backup. To load drivers for a computer you want to restore:
    1. On any computer on your network which is joined to the server, start the WHS console.
    2. Open a backup for the computer you want to restore.
    3. In the root of the backed up C: partition, you will find a folder "Windows Home Server Drivers for Restore". Copy that entire folder to a flash drive.
    4. Boot the computer you want to restore using the Restore CD.
    5. When asked for drivers, use the flash drive you've loaded the drivers on.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, January 7, 2009 12:23 PM
    Moderator