dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
66

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer to jkj860

Premium Member

to jkj860

Re: [IPv6] IPv6 and Netgear WNDR 3700-100NAS issues

Are you sure that you have the MS TCPIP6 protocol stack installed and enabled for that NIC?

As a test, I just disabled IPv6 in my Netgear WNR1000v2-VC guest router, and connected my notebook to it. Shown below is the NIC properties screen showing that the MS TCPIP6 protocol is installed and enabled, and also what I get for the "ipconfig /all" command under those conditions:





C:\>ipconfig /all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : RWS-6325
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Wireless Network Connection 8:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
        Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.10.18
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::21a:73ff:fe67:2cdc%9
        Default Gateway . . . . . . . . . : 192.168.10.1
        DHCP Server . . . . . . . . . . . : 192.168.10.1
        DNS Servers . . . . . . . . . . . : 192.168.10.1
                                            fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:31:48
        Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:31:48
 
Tunnel adapter Teredo Tunneling Pseudo-Interface:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
        Default Gateway . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled
 
Tunnel adapter Automatic Tunneling Pseudo-Interface:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : C0-A8-0A-12
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::5efe:192.168.10.18%2
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        NetBIOS over Tcpip. . . . . . . . : Disabled
 



Please note from the above, that the NIC still gets a link-local IPv6 address [fe80::21a:73ff:fe67:2cdc%9] even with no IPv6 enabled in the router. Also the pseudo IPv6 tunnels are still showing (but they do not appear in your post).

Next, I disabled the MS TCPIP6 protocol for that NIC and reconnected it to the Netgear router. Shown below is the NIC properties screen showing that the MS TCPIP6 protocol is installed and disabled, and also what I get for the "ipconfig /all" command under those conditions:





C:\>ipconfig /all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : RWS-6325
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Wireless Network Connection 8:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
        Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.10.18
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.1
        DHCP Server . . . . . . . . . . . : 192.168.10.1
        DNS Servers . . . . . . . . . . . : 192.168.10.1
        Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:36:03
        Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:36:03
 
Tunnel adapter Teredo Tunneling Pseudo-Interface:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
        Default Gateway . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled
 
Tunnel adapter Automatic Tunneling Pseudo-Interface:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : C0-A8-0A-12
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::5efe:192.168.10.18%2
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        NetBIOS over Tcpip. . . . . . . . : Disabled
 


Please note from the above, that the NIC no longer gets a link-local IPv6 address, but the pseudo IPv6 tunnels are still showing (but they do not appear in your post).

The only way I could duplicate the "ipconfig /all" results you posted was to uninstall the MS TCPIP6 protocol stack as shown below.





C:\>ipconfig /all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : RWS-6325
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Wireless Network Connection 8:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
        Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.10.18
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.1
        DHCP Server . . . . . . . . . . . : 192.168.10.1
        DNS Servers . . . . . . . . . . . : 192.168.10.1
        Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:44:32
        Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:44:32
 


jkj860
The Final Frontier
join:2002-01-10
Valparaiso, IN

jkj860

Member


NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer

Premium Member

Well, since you do seem to have the MS TCPIP6 protocol installed and enabled, I have no definite explanation for why you are not at least seeing a link local [fe00::xx:xx:xx:xx] IPv6 address for that NIC. I don't think that you have a chance for getting IPv6 connectivity until you get that resolved.

You might start by looking at the Symantec firewall setup (look for something related to ICMPv6, since that might block even setting up basic IPv6 for the NIC). If you don't find anything in the Symantec firewall that is blocking IPv6, then uninstalling the MS TCPIP6 protocol stack, rebooting, and then reinstalling it would be the next step.

NetDog
Premium Member
join:2002-03-04
Hollywood, FL

NetDog

Premium Member

said by NetFixer:

Well, since you do seem to have the MS TCPIP6 protocol installed and enabled, I have no definite explanation for why you are not at least seeing a link local [fe00::xx:xx:xx:xx] IPv6 address for that NIC. I don't think that you have a chance for getting IPv6 connectivity until you get that resolved.

I would agree with this.. You need to see the FE80 before IPv6 will work, it is how all the starting traffic works..

Link-local IPv6 Address . . . . . : fe80::708a:eeee:5566:1234%12

Maybe uninstall the stack and reinstall it, what OS was this on?

jkj860
The Final Frontier
join:2002-01-10
Valparaiso, IN

jkj860 to NetFixer

Member

to NetFixer
Ok i will give that a try.
Edit. Vista OS