QUOTE(nymerine @ Mar 6 2014, 12:33 PM)
Yeah you can try, but your previous modem can ping6 out, your PC can't, suspecting its your PC problem?
Edit : Woops, misread your post about your modem can ping6 out.
Edit 2 : Alright, telnet to your TM modem, and run this
CODE
ip6 ping 2404:6800:4001:803::1004
Just making sure it's not a problem with your network devices.
TM Riger modem can't pinging IPv6, dont have route table, so in D-Link show
QUOTE(Raki @ Mar 6 2014, 12:51 PM)
in cmd, type "ipconfig /all"
how many ipv6 address are you assigned for your network adapter?
also try "netsh interface ipv6 show subinterfaces" and see your MTU for your internet bound network interface
try ping with this "ping google.com -6 -l 1432"
CODE
C:\Users\Anime4000>netsh interface ipv6 show subinterfaces >d:\mtu.txt
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4294967295 1 0 6321119 Loopback Pseudo-Interface 1
1280 5 0 0 isatap.imouto
1280 1 1828281290 807466729 Teredo Tunneling Pseudo-Interface
1492 1 915337 4312659 Local Area Connection
1500 5 0 152 VPN - VPN Client
1280 5 0 0 isatap.{6E8BEADE-2E81-4424-A6FF-FD587B5089D4}
1280 5 0 31680 isatap.{A3B894E5-72FD-4711-B00F-A9629574143F}
1280 5 0 0 isatap.{DFD0B9EB-90DD-41CB-84AC-096F5D0C51AF}
1280 5 0 0 isatap.{84E2790B-100F-4E66-A3D8-DFAEC4265651}
1430 5 0 248 LAN Bridger Connection
1500 1 0 185699 VMware Network Adapter VMnet1
1500 1 0 182717 VMware Network Adapter VMnet8
CODE
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Anime4000>ping -6 -l 1432 google.com
Pinging google.com [2404:6800:4003:c00::8b] with 1432 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2404:6800:4003:c00::8b:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Anime4000>ping -6 -l 1280 google.com
Pinging google.com [2404:6800:4003:c00::8b] with 1280 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2404:6800:4003:c00::8b:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Anime4000>
EDIT:
Pinging my desktop PC using WAN and Link-Local
CODE
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Anime4000>ping 2001:e68:4410:419e:60ae:c44c:1887:5870
Pinging 2001:e68:4410:419e:60ae:c44c:1887:5870 with 32 bytes of data:
Reply from 2001:e68:4410:419e:60ae:c44c:1887:5870: time=6ms
Reply from 2001:e68:4410:419e:60ae:c44c:1887:5870: time=3ms
Reply from 2001:e68:4410:419e:60ae:c44c:1887:5870: time=2ms
Reply from 2001:e68:4410:419e:60ae:c44c:1887:5870: time=2ms
Ping statistics for 2001:e68:4410:419e:60ae:c44c:1887:5870:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 6ms, Average = 3ms
C:\Users\Anime4000>ping anime4000-pc
Pinging Anime4000-PC [fe80::44b9:711e:4893:fea3%48] with 32 bytes of data:
Reply from fe80::44b9:711e:4893:fea3%48: time=1ms
Reply from fe80::44b9:711e:4893:fea3%48: time=1ms
Reply from fe80::44b9:711e:4893:fea3%48: time=1ms
Reply from fe80::44b9:711e:4893:fea3%48: time=1ms
Ping statistics for fe80::44b9:711e:4893:fea3%48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Users\Anime4000>
This post has been edited by Anime4000: Mar 6 2014, 03:02 PM