OK - After talking it through with another individual, I uninstalled all the network adapters, re-installed, and reset the TCP/IP Stack - so I back at a default config, that should work!
For the sake of this I am using two platforms:
- Windows 7 Professional Latpop - called 'LONDON'
- Windows 7 Ultimate Desktop PC - called 'PRAGUE'
The IPCONFIG from 'Prague' is ...
Code:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::c579:2fea:585e:2a4a%10
IPv4 Address. . . . . . . . . . . : 192.168.1.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:100a:3574:a964:c437
Link-local IPv6 Address . . . . . : fe80::100a:3574:a964:c437%11
Default Gateway . . . . . . . . . : ::
Tunnel adapter isatap.home:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
The IPCONFIG from 'London' is
Code:
Wireless LAN adapter Wireless Network Connection 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::391f:8f25:1768:733b%20
IPv4 Address. . . . . . . . . . . : 192.168.1.64
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Local Area Connection* 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : {{REMOVED MY OP}}
Ethernet adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Whilst on the laptop, 'London' I can ping 'Prague' fine, both using IPv4 and IPv6
Code:
C:\Users\david>ping prague
Pinging PRAGUE.home [192.168.1.120] with 32 bytes of data:
Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.1.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Users\david>ping prague -6
Pinging Prague [fe80::c579:2fea:585e:2a4a%20] with 32 bytes of data:
Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
Ping statistics for fe80::c579:2fea:585e:2a4a%20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
But when on the PC, 'Prague'
Code:
C:\Users\david>ping london
Pinging london.home [192.168.1.64] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.64:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\david>ping london -6
Pinging London [fe80::391f:8f25:1768:733b%10] with 32 bytes of data:
Reply from fe80::391f:8f25:1768:733b%10: time<1ms
Reply from fe80::391f:8f25:1768:733b%10: time<1ms
Reply from fe80::391f:8f25:1768:733b%10: time<1ms
Reply from fe80::391f:8f25:1768:733b%10: time<1ms
Ping statistics for fe80::391f:8f25:1768:733b%10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The same is true if I try to remote desktop into the laptop, 'London'. I can do it whilst using a IPv6 address, but not when it defaults to IPv4.
I have never seen it when IPv4 fails, when IPv6 succeeds. What is going on with my IPv4 traffic?