Forum Home
Press F1
Thread ID: 124124	2012-04-07 23:27:00	What's up with Windows 7 ping messages using CMD	undiejuice (16495)	Press F1

Post ID	Timestamp	Content	User
1268809	2012-04-07 23:27:00	Hiya, I've got an ethernet network at home. (not wireless) At the moment I have just installed two PCs with Windows 7, but the funny thing is, I want to set these two computers with its own IP address. I know how to do this using Windows XP. I think I have done this correctly in Windows 7 using the IPv4 address. (Internet Protocol Version4) TCP/IP via Local Area Connection (properties) My reason for doing this is so I can access these computers remotely in another room via WAKE UP on local network (WOL), so I need a IP address for this to work. The strange thing is, when I ping these computers I get something like: Pinging one of my Windows 7 computers, I receive the message below: Pinging LOUNGE [fe80::936:b979:41:de5%12] with 32 bytes of data: Reply from fe80::936:b979:41:de5%12: time<1ms Reply from fe80::936:b979:41:de5%12: time<1ms Pinging my XP computer, I receive the address like the one below: Pinging ROOM1 [192.168.1.18] with 32 bytes of data: Reply from 192.168.1.18: bytes=32 time<1ms TTL=128 So my question is how do I correct this issue in Windows 7 so it will show up like the above example in Windows XP? Note: Communication between each computer is fine, except for the IP address issue here. Thanks.	undiejuice (16495)
1268810	2012-04-07 23:59:00	Looks like you're using IPv6 on the windows 7 computers. From memory IPv6 is installed by default but requires a DHCP to serve out IPv6 addresses. You might want to check if your router etc has IPv6 DHCP enabled and if so disable it.	Webbnzl (8810)
1268811	2012-04-08 00:28:00	Mine does the same thing with w7 / XP --- If you ping the W7 computer by its Name you get as you have put, but ping it by its actual IP address and you will get its IP as a reply.	wainuitech (129)
1268812	2012-04-08 09:02:00	Don't you need an Ethernet MAC address to wake up the computer? Anyway, you should be able to use ping -4 lounge to ping the W7 machines using IPv4 only - they'll have both IPv6 & IPv4 addresses.	MushHead (10626)
1268813	2012-04-08 10:02:00	It is because IPv6 is enabled on both the machine you are pinging from, and the machine you are pinging. And no, you shouldn't need to know the IP address to use WOL, but you will need to know the MAC address. Standard WOL uses subnet broadcast with a target MAC address.	inphinity (7274)
1268814	2012-04-08 18:24:00	@Webbnzl: Unfortunately I am using the IPv4 on my Windows 7 computer. Thanks @Wainuitech: Your right. It seems ridiculous to me that users with Windows 7 expects us to write the entire ip address instead of the computer name? Thanks @MushHead: Yes you are correct you need a mac address and Windows 7 both include IPV6 x IPv4 addresses. I do have a mac address for all computers as well. Pinging computers which are Windows 7, are not clear cut like PC's of earlier Windows versions. Thats the bit i am trying to figure out, if I am not doing something right. If Wainuitech is experiencing the same thing, it appears to me it has to be related to Windows 7, not my ip address. Thanks.	undiejuice (16495)
1268815	2012-04-09 01:19:00	IPv6 addresses that start with fe80 are link-local addresses which don't come via DHCP.	Agent_24 (57)
1268816	2012-04-10 02:59:00	@Webbnzl: Unfortunately I am using the IPv4 on my Windows 7 computer. ThanksYou're using IPv6 as well - the address given in the ping replies is an IPv6 link-local address. @Wainuitech: Your right. It seems ridiculous to me that users with Windows 7 expects us to write the entire ip address instead of the computer name? ThanksIt doesn't expect that; you can quite happily use the name (as your ping command demonstrates). @MushHead: <snip> Pinging computers which are Windows 7, are not clear cut like PC's of earlier Windows versions. Thats the bit i am trying to figure out, if I am not doing something right. If Wainuitech is experiencing the same thing, it appears to me it has to be related to Windows 7, not my ip address. Thanks.You seem to be a bit confused about what you're seeing. What you are describing isn't actually a problem at all, it's simply normal behavior. When IPv6 is available (which in your case, it is), it will be used - IPv4 will only be used if an application explicitly requires it, or if the resource isn't available over IPv6. Both your system and the ping command are behaving exactly as they ought to be.	Erayd (23)
1268817	2012-04-10 03:34:00	@Eryd and Anyone reading this.... Okay, can you clarify what steps I must I do so the name of the computer I want to ping will not appear like as the IP version 6? Attached to this message are current screen shots of my PC at the moment for both IPV6 and IPV4. Cheers.	undiejuice (16495)
1268818	2012-04-10 03:53:00	Okay, can you clarify what steps I must I do so the name of the computer I want to ping will not appear like as the IP version 6?Why do you want this? IPv6 is already working fine, and unless you're doing something rather strange, there's no reason why you can't just continue with things the way they are now. If you wish to force the ping command to use IPv4, use 'ping -4 lounge'. MushHead has already mentioned this in post #4. Alternatively, you can disable IPv6 completely on the relevant NIC (your third screenshot). As mentioned earlier though, there's no need to take either of these steps - your system is working perfectly already. Why do you believe that something needs to be changed?	Erayd (23)
1 2