Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 2 [3]

Author Topic: Can't get an IPv6 tunnel to work on windows 7.  (Read 43956 times)

brianko

  • Newbie
  • *
  • Posts: 4
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #30 on: April 02, 2010, 11:01:50 AM »

At this point, no netsh commands work without generating the "duplicate name exists" error.  I'm not even too sure what this error refers to, despite some rather extensive googling.

If I could just get past the "duplicate name exists" crap, I'd be on my way to trying this again.
« Last Edit: April 02, 2010, 11:06:00 AM by brianko »
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2671
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #31 on: April 02, 2010, 11:18:28 AM »

http://www.dslreports.com/forum/r23347380-Unable-to-connect-to-IPv6-Newsgroups~start=20

Do you get the error even when your try and remove your tunnel?
Logged

brianko

  • Newbie
  • *
  • Posts: 4
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #32 on: April 02, 2010, 11:27:20 AM »

It's working, thanks for the assist!

ipconfig /all showed another tunnel adapter existed (I probably fat-fingered it when typing in the commands).  "netsh interface ipv6 delete interface IPTunnel2" took care of the problem.

The lesson I took away from this is that "netsh interface ipv6 reset" does not actually reset anything back to the initial install.  It appears to restore a few default settings, but previously-created tunnels are not removed.
Logged

brianko

  • Newbie
  • *
  • Posts: 4
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #33 on: May 05, 2010, 03:33:43 AM »

Just came across another annoying issue that caused my tunnel to go down:  At some point during a Windows update, the following registry entry was reset from "0" to "ff":

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents

With this changed, all IPv6 interfaces were absent from ipconfig /all.  In addition, running the following command produced the dreaded "Element not found" error:

netsh interface ipv6 add v6v4tunnel IP6Tunnel yy.yy.yy.yy xx.xx.xx.xx

Resetting the registry key above to "0" and rebooting got IPv6 working again.
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #34 on: May 05, 2010, 11:52:33 AM »

Odd.  I did updates all the time and never have this happen under XP.  They've really broken this under 7?
Logged

str0AT

  • Newbie
  • *
  • Posts: 4
Re: Can't get an IPv6 tunnel to work on windows 7.
« Reply #35 on: June 05, 2010, 11:38:31 AM »

EDIT: nevermind, it just started to work again - no idea why.

Hello guys, i seem to have a strange problem with my tunnel here:
Yesterday everything worked nicely, fast and stable - but today when i woke up IPv6 was dead (i never turn my PC off, so it cant be a issue related to a reboot)

Maybe someone can see the error in my ipconfig /all?
Beware: The Windows is German, i translated the text for you, so it could look "dumb" at some places.

What i tryed:
Remove IP6Tunnel and reiconfigure it - did not help at all.
Code: [Select]

Windows-IP-Konfiguration | IP Configuration

   Hostname  . . . . . . . . . . . . : QUAD
   Prim„res DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing activated  . . . . . . : No
   WINS-Proxy activated  . . . . . . : No

Ethernet-Adapter LAN-Verbindung:

   Verbindungsspezifisches DNS-Suffix:
   Description. . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
   MAC Address          . . . . . . : 00-19-DB-CE-80-B9
   DHCP activated . . . . . . . . . : Nein
   Autoconfiguration activated. . . : Ja
   Local IPv6-Address             . : fe80::8442:9f6f:d00c:2d79%10(Bevorzugt)
   IPv4-Address . . . . . . . . . . : 192.168.0.5(Bevorzugt)
   Subnet mask  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : fe80::c4ee:99c7:48ad:f889%10
                                       192.168.0.1
   DHCPv6-IAID . . . . . . . . . . . : 251666821
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-11-12-C2-FC-00-21-85-02-8B-E3
   DNS-Server  . . . . . . . . . . . : 195.96.0.4
                                       195.70.224.45
   NetBIOS over TCP/IP . . . . . . . : Aktiviert


Tunneladapter isatap.{A34F4AB9-EC95-4211-924F-8309EE2927AA}:

   Medienstatus. . . . . . . . . . . : disconnected
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter IP6Tunnel: <--- HE Tunnel

   Description. . . . . . . . . . . : Microsoft Direct-Punkt-zu-Punkt-Adapater
   Physical Address. .  . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP activated . . . . . . . . . : No
   Autoconfiguration activated. . . : Yes
   IPv6-Address. . . . . . . . .  . : 2001:470:1f14:aed::2
   Local IPv6-Address . . . . ..  . : fe80::b112:606c:9793:4eb3%17
   Standardgateway . . . . . . .. . : 2001:470:1f14:aed::1
   DNS-Server  . . . . . . . .  . . : 195.96.0.4
                                      195.70.224.45
   NetBIOS over TCP/IP . . . . . . .: Deactivated

Tunneladapter isatap.{2B4B09D1-7961-4CE2-9083-5DB730018B07}:

   Medienstatus. . . . . . . . . . . : disconnected
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter 6TO4 Adapter:

   Medienstatus. . . . . . . . . . . : disconnected
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{E8E8C068-875C-4389-910F-7A7BFC8E0E83}:

   Medienstatus. . . . . . . . . . . : disconnected
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #5
   Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
« Last Edit: June 05, 2010, 01:59:23 PM by str0AT »
Logged
Pages: 1 2 [3]