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
1268819	2012-04-10 03:55:00	To get them to reply Via IP address and typing in their name, on your last picture, untick Internet protocol V6. This HAS to be done on both computers then the computer you ping will reply by its IP after you ping its name. See pic below, same PC's, top Ping is with with IPV6 unticked on BOTH, bottom reply is with IPV6 on both. 3706 Snap:Erayd posted before me :)	wainuitech (129)
1268820	2012-04-10 04:13:00	WT - you don't need to disable IPv6 on both ends to achieve that result; disabling on one is sufficient (ideally the machine you're pinging from).	Erayd (23)
1268821	2012-04-10 06:18:00	Tried pinging 3 different W7 PC's, Mines was set to IPV4 only, two replied back with the IPV6 figures and one didn't. Dont know why that happened though, wasn't till it was disabled on both did it reply with an IP address (IPV4).:confused:	wainuitech (129)
1268822	2012-04-10 08:38:00	...Mine was set to IPV4 only, two replied back with the IPV6 figures...This means that the PC you were pinging from still had IPv6 enabled and wasn't actually set to IPv4 only, despite what you may have thought. ICMPv6 packets were being sent and received, which means both PCs were speaking IPv6.	Erayd (23)
1268823	2012-04-10 10:12:00	Nope not in this case. It was from this PC, & as mentioned Mines was set to IPV4 only.( I even double checked) I did a ping to different PC's one after the other, why two decided not to play nice I dont know. I went out to the workshop, disabled IPV6 on the two that didn't respond like expected, came back inside and they worked. Went back out again and put them on again and this time they did work like the previous one that did. The first test -- The one that did respond correctly was the first one, the second and third ones were the ones that played up. Something must have gone pear shaped somehow.	wainuitech (129)
1268824	2012-04-10 11:10:00	Nope not in this case. It was from this PC, & as mentioned Mines was set to IPV4 only.( I even double checked)I can guarantee that it wasn't set to IPv4 only - if it had been, it would have been unable to send and receive IPv6 ping (this is technically impossible without a functional IPv6 stack), and you stated above that you were receiving an IPv6 ping response. This means that either you are mistaken about IPv6 being disabled, or you are mistaken about receiving an IPv6 ping response. Perhaps you disabled IPv6 on a different interface than the one that was actually being used - I don't suppose you have a WiFi network it may have sneaked out on?	Erayd (23)
1268825	2012-04-10 11:49:00	IPV6 was unticked and saved, there was only IPV4 active. There is only one wired adaptor, all are desktop PC's with no wireless. The only wireless device attached to the LAN at that time was my Cell phone, and thats certainly not the same name. :) I know what you are saying regarding not being possible if it was unactive, but I can guarantee 100% I was not mistaken, and I did untick and save/apply it. I was here, I unticked it, and I saw it as such. As well as this fact, Had I unticked IPV4 instead of IPv6 then I would have killed my internet connection, as Telstra doesn't yet support IPV6 actively , only IPv4, and that didn't happen. As I said it appears it didn't actually deactivate right away like it was meant to, even after unticking and saving. Thats the only reason I can see because it still used IPV6 for some reason and a few seconds later it didn't, something obviously didn't do what It was meant to, I didn't change any other settings. It doesn't matter anyway - the Op wanted to know why he was getting the results and the answer was given.	wainuitech (129)
1268826	2012-04-10 11:55:00	As I said it appears it didn't actually deactivate right away like it was meant to, even after unticking and saving. Thats the only reason I can see because it still used IPV6 for some reason and a few seconds later it didn't, something obviously didn't do what It was meant to, I didn't change any other settings. That's a good point - Windows is strange enough that this is actually a very plausible possibility, and maybe whatever was set in the UI somehow didn't end up actually being applied before you ran the ping command.	Erayd (23)
1 2