Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
HP WHS - After setting up the static IP address - Unable to access to the box ... Help RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello experts,

    I have the HP WHS 485.  After reading this article (http://www.myhomeserver.com/?page_id=20), I decided to set up the static IP address so that I can use it via a web.   Right after changing the IP address, I am unable to access to the box anymore... Unable to ping to it (new or old IP address), unable to "see" it in the network....

    It seems like It is locked out of the network.   Is there a way to set it back or to connect to it?

    Thanks much for your help.

    Wednesday, March 24, 2010 3:04 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello experts,

    I have the HP WHS 485.  After reading this article (http://www.myhomeserver.com/?page_id=20), I decided to set up the static IP address so that I can use it via a web.   Right after changing the IP address, I am unable to access to the box anymore... Unable to ping to it (new or old IP address), unable to "see" it in the network....

    It seems like It is locked out of the network.   Is there a way to set it back or to connect to it?

    Thanks much for your help.

    Assuming that you made a typo somewhere in the IP address/subnet, the only viable way to fix it is Server Recovery (or, if that doesn't work, Factory Reset).  The other option would be to find a way to add a keyboard/mouse/monitor (either through USB or, more likely, by disassembling your server and try to add your own connection).
    Wednesday, March 24, 2010 3:40 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    There's no method that's guaranteed to discover the new IP address of your server. Most methods require you to know the computer's MAC address; on your server, that should be on a sticker on the back of the unit.

    You can check the ARP cache on a home computer (though often this will be empty) to see if you can find your server's IP address that way. You can also check your router's ARP cache to see if it records all devices on your network. Assuming it does (it may not, however, since many consumer routers only track DHCP clients), it should show an IP address for your server. You can use a packet sniffer of some sort, or any of a number of other network diagnostic tools.

    If you aren't able to identify your server's IP address, you'll be down to server recovery, as kariya21 has suggested.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, March 24, 2010 4:21 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you all for your quick response.   I logged into the router and got the IP address that was last assigned to it.  No luck, though.   You mentioned about ARP cache, would you feed me what it is?  I honestly don't understand following your suggestion :(

     

    What would I do if I have the MAC address on the back of the box? 

    thanks all

    I hate to get the server recovery.  It will erase all my data. :(  Not fun!!!!

    Wednesday, March 24, 2010 4:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Interestingly, I just found out that, after unlug the power of the router and the reset the WHS, I am able to ping the server as followed:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\907>ping 907-home-server

    Pinging 907-HOME-SERVER [192.168.1.102] with 32 bytes of data:
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

    Ping statistics for 192.168.1.102:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms

    C:\Users\907>

    However, I still can't remote access to the box using either the server name (907-home-server) or its assocaited IP address.  

    Any clue on this? Pls help. 

    Best regards,

    Wednesday, March 24, 2010 5:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I hate to get the server recovery.  It will erase all my data. :(  Not fun!!!!


    A server _recovery_  keeps all your data - you might be thinking of a new installation that will format all drives.
    --
    Wednesday, March 24, 2010 10:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Interestingly, I just found out that, after unlug the power of the router and the reset the WHS, I am able to ping the server as followed:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\907>ping 907-home-server

    Pinging 907-HOME-SERVER [192.168.1.102] with 32 bytes of data:
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

    Ping statistics for 192.168.1.102:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms

    C:\Users\907>

    However, I still can't remote access to the box using either the server name (907-home-server) or its assocaited IP address.  

    Any clue on this? Pls help. 

    Best regards,


    Did you give enough time for the server to start i.e had it been a couple of minutes since all the lower 3 lights were solid blue - could you access http://192.168.1.102/

    When you set the IP address did you set the netmask to 255.255.255.0, if you set it to something else then you'll have to change the rest of your network to match.

    --
    Wednesday, March 24, 2010 10:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Interestingly, I just found out that, after unlug the power of the router and the reset the WHS, I am able to ping the server as followed:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\907>ping 907-home-server

    Pinging 907-HOME-SERVER [192.168.1.102] with 32 bytes of data:
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
    Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

    Ping statistics for 192.168.1.102:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms

    C:\Users\907>

    However, I still can't remote access to the box using either the server name (907-home-server) or its assocaited IP address.  

    Any clue on this? Pls help. 

    Best regards,


    Did you give enough time for the server to start i.e had it been a couple of minutes since all the lower 3 lights were solid blue - could you access http://192.168.1.102/

    When you set the IP address did you set the netmask to 255.255.255.0, if you set it to something else then you'll have to change the rest of your network to match.

    --


    Thanks for following up with my problem.  No, the http://192.168.1.102 did return the error page as I expected.   And YES, I set the right netmask as 255.255.255.0.  

    A question to all:  how do I run the server recovery?  In the HP site, it instructs me to pop up the HP recovery disk to a computer in the same network and run from there.  My problem is this box is not recognized in the network. 

    Any instruction/suggestion is personally appricated.

    Bests

     

    Thursday, March 25, 2010 2:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    To recover a HP MSS use the following procedure:
    http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01213383&lc=en&dlc=en&cc=us&product=3548165

    It's quite tricky to get the recovery mode started on the MSS, give it a few tries and you will get it.  Connecting your MSS directly to the PC with a network cable (in a lot of cases these days crossover cables are not required as interfaces can auto sense the required connection) is more reliable than going through a router/bridge - something to bear in mind if the server is not found the first or second time.

    --
    Thursday, March 25, 2010 10:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    To recover a HP MSS use the following procedure:
    http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01213383&lc=en&dlc=en&cc=us&product=3548165

    It's quite tricky to get the recovery mode started on the MSS, give it a few tries and you will get it.  Connecting your MSS directly to the PC with a network cable (in a lot of cases these days crossover cables are not required as interfaces can auto sense the required connection) is more reliable than going through a router/bridge - something to bear in mind if the server is not found the first or second time.

    --

    I read this article before and it came to my mind that the HP WHS box is not recognized in the home network, how could the recovery CD run and "find" its box... :)

    One interesting thing about your recommendation is to connect the HP WHS box directly to the laptop via ethernet cable.  I have never thought about this and not sure it works.

    Let me try and take a shot :)

    I'll get you posted how it goes on this; and pls accept my thank to you.

    John.

    Thursday, March 25, 2010 11:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I read this article before and it came to my mind that the HP WHS box is not recognized in the home network, how could the recovery CD run and "find" its box... :)

    HP Thought about that in the recovery process.  When you press the button it's loading a recovery system so it doesn't actually load the incorrect network settings from your windows home server installation.
    --
    Friday, March 26, 2010 9:57 AM