Share via

IPv6 problem with Ethernet interface

Anonymous
2010-10-19T15:16:27+00:00

Hello,

I have a Lenovo R-Series notebook with Windows XP SP3 fully patched installed. For my work, I need an IPv6 connection (IPv6 is successfully installed on my laptop). Now I see a very strange problem with it. Here are the details:

*) Ethernet with IPv4 only and deactivated WLAN works fine

*) Ethernet with IPv4 AND IPv6 don't work correctly. It seems that the v4 connection is prefered over the v6 connection (shouldn't it be the other way round?). Additionally, websites are opened extremely slow, with lots of visual problems, or they do not open at all. Here is my ipconfig (it is in german language, sorry).

Beschreibung. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

        Physikalische Adresse . . . . . . : 00-0A-E4-C6-9F-FE

        DHCP aktiviert. . . . . . . . . . : Ja

        Autokonfiguration aktiviert . . . : Ja

        IP-Adresse. . . . . . . . . . . . : 192.168.2.32

        Subnetzmaske. . . . . . . . . . . : 255.255.255.0

        IP-Adresse. . . . . . . . . . . . : 2a01:190:1702:0:b0:8bcb:9715:6d9

        IP-Adresse. . . . . . . . . . . . : 2a01:190:1702:0:20a:e4ff:fec6:9ffe

        IP-Adresse. . . . . . . . . . . . : 2a01:190:1702:1:b0:8bcb:9715:6d9

        IP-Adresse. . . . . . . . . . . . : 2a01:190:1702:1:20a:e4ff:fec6:9ffe

        IP-Adresse. . . . . . . . . . . . : fec0::1:1:0:0:1%5

        IP-Adresse. . . . . . . . . . . . : fec0::5:0:0:3%5

        IP-Adresse. . . . . . . . . . . . : fec0::1:0:0:1%5

        IP-Adresse. . . . . . . . . . . . : fe80::20a:e4ff:fec6:9ffe%7

        Standardgateway . . . . . . . . . : 192.168.2.1

                                            fe80::21e:f7ff:fe79:4ae9%7

                                            ::

        DHCP-Server . . . . . . . . . . . : 192.168.2.1

        DNS-Server. . . . . . . . . . . . : 81.16.150.4

                                            81.16.151.4

                                            fec0:0:0:ffff::1%5

                                            fec0:0:0:ffff::2%5

                                            fec0:0:0:ffff::3%5       

        Primärer WINS-Server. . . . . . . : 192.168.2.247

Pings are sent, as described above, over v4. Interestingly, the pings look good (websites still open extremely slow):

Ping www.ripe.net [193.0.6.139] mit 32 Bytes Daten:

Antwort von 193.0.6.139: Bytes=32 Zeit=25ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=24ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=24ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=24ms TTL=242

*) Ethernet with IPv4 only and activated WLAN with IPv4 and IPv6 work fine too

Ping www.ripe.net [2001:610:240:22::c100:68b] mit 32 Bytes Daten:

Antwort von 2001:610:240:22::c100:68b: Zeit=27ms

Antwort von 2001:610:240:22::c100:68b: Zeit=28ms

Antwort von 2001:610:240:22::c100:68b: Zeit=28ms

Antwort von 2001:610:240:22::c100:68b: Zeit=27ms

Ping dns1.nextlayer.at [2a01:190:1764:150::4] mit 32 Bytes Daten:

Antwort von 2a01:190:1764:150::4: Zeit=16ms

Antwort von 2a01:190:1764:150::4: Zeit=172ms

Antwort von 2a01:190:1764:150::4: Zeit=5ms

Antwort von 2a01:190:1764:150::4: Zeit=6ms

*) Lastly, Ethernet with IPv4 and IPv6 and activated WLAN with IPv4 and IPv6 has the same problem as Ethernet IPv4 IPv6 without WLAN, websites open extremely slow or not at all. This time, sometimes pings are sent through v4 and sometimes through v6:

Ping www.ripe.net [193.0.6.139] mit 32 Bytes Daten:

Antwort von 193.0.6.139: Bytes=32 Zeit=27ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=25ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=27ms TTL=242

Antwort von 193.0.6.139: Bytes=32 Zeit=25ms TTL=242

Ping dns1.nextlayer.at [2a01:190:1764:150::4] mit 32 Bytes Daten:

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

Ping ipv6.l.google.com [2a00:1450:8005::93] mit 32 Bytes Daten:

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

Zielhost nicht erreichbar.

So it really seems that there is an (driver?) IPv6 problem at the Ethernet interface? The NIC driver is from the Windows Update site. My colleague had the same problem with his Windows XP SP3. He then installed Windows 7, and all works perfectly.

Is there a trick to solve this really strange problem?

Thanks in advance

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2010-11-03T10:05:31+00:00

    Unfortunately I do not have an XP Computer that runs IPv6 but I'll try to look around.

    Hi,

    could you find an XP computer that runs IPv6?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-10-20T14:46:50+00:00

    Hi Jack,

     

    I work for an ISP which has already fully deployed native IPv6 in it's network, inside and outside.

    Hi

    Good to see that it is already in action.

    Unfortunately I do not have an XP Computer that runs IPv6 but I'll try to look around.


    Jack-MVP Windows Networking. WWW.EZLAN.NET

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-10-20T07:36:02+00:00

    Hi Jack,

    I work for an ISP which has already fully deployed native IPv6 in it's network, inside and outside. As you can see in my first post, IPv6 over WLAN works perfectly, and all my colleagues who are working with Windows 7 have no problems with IPv6 at all over Ethernet only. So I can gurantee that my ISP and all my periphals are IPv6 compatible.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-10-20T00:42:02+00:00

    Hi

    IPv6 does not work over regular Internet connection. If you are part of special project that has IPv6 over the Internet make sure that all your ISP, and your peripherals are PVv6 compatible.


    Jack-MVP Windows Networking. WWW.EZLAN.NET

    Was this answer helpful?

    0 comments No comments