WHS2011 – Unable to ping Server Name, but CAN ping IP
Home › Forums › Home Theater Computers › WHS2011 – Unable to ping Server Name, but CAN ping IP
- This topic has 13 replies, 4 voices, and was last updated 13 years, 6 months ago by
mikinho.
-
AuthorPosts
-
April 25, 2011 at 10:41 pm #25946
So having a weird problem that I have had in the past and don’t remember how i fixed it. I just finished setting up my WHS2011 and while i can ping it fine by it’s IP address, when I try to ping it by it’s friendly name “SERVER” it doesn’t work.
The server being used is an HP MediaSmart EX495, so if i lose IP access, i would literally have to format and start from scratch.
But that being said, I’ve tried all sorts of things. I’m using a Linksys WRT54g with Tomato 1.28 firmware.
Any thoughts or ideas?
btw, I *think* this is the reason I can’t install the Windows Home Server connector software on one of my systems, but can’t be sure.
April 25, 2011 at 10:45 pm #29762swoon
Can it even ping itself using the name?
April 25, 2011 at 11:36 pm #29765yes, it can ping itself via it’s server name, but it’s strange, it shows the MAC address and not the IP:
Pinging SERVERNAME [fe80::XXX:f7XX:6fXX:1XX%XX] with 32 bytes of data:
Reply from fe80::XXX:f7XX:6fXX:1XX%XX: time<1ms
Reply from fe80::XXX:f7XX:6fXX:1XX%XX: time<1ms
Reply from fe80::XXX:f7XX:6fXX:1XX%XX: time<1ms
Reply from fe80::XXX:f7XX:6fXX:1XX%XX: time<1msPing statistics for fe80::XXX:f7XX:6fXX:1XX%XX:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msApril 26, 2011 at 12:03 am #29769Actually, that looks like an IPv6 address. Maybe you can start with the basics. perform arp -d on the server/client machines. Ping from the client using SERVER as the address and check to see if ARP worked (arp -a).
April 26, 2011 at 12:16 am #29772ok, so i ran arp -d on both server and client. still same thing.
when i did arp -a, i see the following:
Interface: 192.168.1.101 — 0xa
Internet Address Physical Address Type
192.168.1.1 00-0f-66-2c-a1-5e dynamic
192.168.1.131 00-18-dd-01-b7-bc dynamic
192.168.1.139 00-26-2d-00-65-59 dynamic
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa staticApril 26, 2011 at 12:19 am #29773When you did arp -d on the server did you enter “arp -d <client IP>” and then on the client “arp -d <server IP>”. After that, ping from client and perform arp -a on server and client.
April 26, 2011 at 1:03 am #29776ok, so i see this on the server:
Interface: 192.168.1.139 — 0xb
Internet Address Physical Address Type
192.168.1.1 00-0f-66-2c-a1-5e dynamic
192.168.1.115 00-0e-3b-23-0b-31 dynamic
192.168.1.131 00-18-dd-01-b7-bc dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.252 01-00-5e-00-00-fc static
224.0.0.253 01-00-5e-00-00-fd static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff staticAnd this on the client:
Interface: 192.168.1.101 — 0xa
Internet Address Physical Address Type
192.168.1.1 00-0f-66-2c-a1-5e dynamic
192.168.1.115 00-0e-3b-23-0b-31 dynamic
192.168.1.117 f0-b4-79-1e-0b-89 dynamic
192.168.1.131 00-18-dd-01-b7-bc dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa staticSo…what’s it mean? 🙂 Did it work? i tried pinging and no change
April 26, 2011 at 1:23 am #29778The ARP table keeps track of the physical (MAC) addresses that are associated with IP addresses. Looking at your information, I can see that there is no entry for 192.168.1.139 in the client’s table and no entry for 192.168.1.101 in the server’s table. This means that what is most likely happening is the client is unable to resolve the “SERVER” name into an IP address.
Next thing, perform an “ipconfig /all” on each machine and see what it says. Also, just a random idea, try disabling IPv6 on WHS under the Network properties and see what happens.
April 26, 2011 at 1:59 am #29782sonofa…aaron by gosh u got it. i disabled IPv6 and voila, server can ping client, and client can ping server (and it shows IP address)!!
So…stupid question…do i lose anything by not having IPv6?
Thanks aaron
April 26, 2011 at 2:43 am #29783You probably have no reason to use IPv6 right now. It is there for the one day you might.
May 4, 2011 at 2:09 pm #29919[quote=swoon]
You probably have no reason to use IPv6 right now. It is there for the one day you might.
[/quote]
I have noticed some of those older routers with the modified OS on them have given me issues with IPv6.
May 4, 2011 at 4:22 pm #29921I think we might have to convert this to a tip (but hopefully one of you with better understanding of it), because ever since i turned off IPv6 on my Home Server, I never have problems RDPing into it, even with m y Mac. On my old WHS, i would constantly have to login via the IP because for whatever reason it forgot the friendly name.
May 4, 2011 at 4:36 pm #29922Mike,
Can you run a test to determine if the router is the cause of your issue? Just plug your PC and WHS into a dumb switch or direct connect (with crossover if needed). Turn IPv6 back on and see what happens.
May 4, 2011 at 5:27 pm #29923[quote=swoon]
Mike,
Can you run a test to determine if the router is the cause of your issue? Just plug your PC and WHS into a dumb switch or direct connect (with crossover if needed). Turn IPv6 back on and see what happens.
[/quote]
Not important to this conversation but cross-over isn’t needed. 1000BASE-T standard (aka IEEE 802.3ab) requires Auto-MDIX so all Gigabit Ethernet network cards will auto detect and use the cable accordingly.
-
AuthorPosts
- You must be logged in to reply to this topic.