• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Can not create tunnel 'Element not found' Windows 7

Started by burphur, February 06, 2011, 10:34:37 PM

Previous topic - Next topic

burphur

hi i am having trouble setting up the ipv6 tunnel on my windows 7 machine

i have setup the tunnel on the website but when i try to run the following command

netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.1.121 209.51.161.14

i get the error 'Element not found.'

am i missing something? is their any software/drivers i am suppose to install?

heres the output of my ipconfig /all if it helps
C:\Windows\System32>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : Demonize
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Broadcast
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

Ethernet adapter Local Area Connection 3:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : gogo6 Virtual Multi-Tunnel Adapter
  Physical Address. . . . . . . . . : 02-50-F2-00-00-01
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 2:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Realtek RTL8102E/RTL8103E Family PCI-E Fa
st Ethernet NIC (NDIS 6.20) #2
  Physical Address. . . . . . . . . : 00-1E-33-A2-C6-E6
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : phub.net.cable.rogers.com
  Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Adapter

  Physical Address. . . . . . . . . : 00-24-D2-25-BF-AD
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 192.168.1.121(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : Monday, February 07, 2011 12:54:53 AM
  Lease Expires . . . . . . . . . . : Sunday, April 17, 2011 11:33:53 AM
  Default Gateway . . . . . . . . . : 192.168.1.1
  DHCP Server . . . . . . . . . . . : 192.168.1.1
  DNS Servers . . . . . . . . . . . : 8.8.8.8
                                      8.8.4.4
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
  Physical Address. . . . . . . . . : 00-50-56-C0-00-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 192.168.65.1(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . :
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
  Physical Address. . . . . . . . . : 00-50-56-C0-00-08
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 192.168.159.1(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . :
  NetBIOS over Tcpip. . . . . . . . : Enabled


i hope someone can help me solve this problem i can wait to try out ipv6

comptech

Looks like someone ran across this problem before and this was probably the solution:

Quote from wstreeter:
QuoteA co-worker and I had the same problem. We had to make a change to a registry key and then reboot to get the tunnel to create.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

Normally, the DisabledComponents value does not exist. If the value does not exist or the value data is 0, IPv6 is enabled on all interfaces.

On mine this was set to a non-zero value so I changed it to zero and then rebooted. After that I was able to create the tunnel and IPv6 was functioning great.

From this thread about the same initial issue:
http://www.tunnelbroker.net/forums/index.php?topic=653.0

NKonaya

I have to concure with the reply to your post. My system was balking, and didn't get my original reply out; but your 'ipconfig -all' report lacks the IPv6 Link-Local IP address. Begins with 'fe80:', as in my Ethernet connection section:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : aosake.net
   Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
   Physical Address. . . . . . . . . : 00-17-31-C6-CC-63
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f05:15b0::c0a8:6622(Preferred)

   Link-local IPv6 Address . . . . . : fe80::91d8:c501:13c8:3369%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.102.34(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, February 06, 2011 10:00:07 PM
   Lease Expires . . . . . . . . . . : Thursday, March 16, 2147 5:08:04 AM
   Default Gateway . . . . . . . . . : 192.168.102.1
   DHCP Server . . . . . . . . . . . : 192.168.102.1
   DHCPv6 IAID . . . . . . . . . . . : 234886961
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-8E-B4-DC-00-17-31-C6-CC-63

   DNS Servers . . . . . . . . . . . : 192.168.102.1
   NetBIOS over Tcpip. . . . . . . . : Enabled


burphur

thnx guys i got it working, and can now browse ipv6

i came accross that post b4 telling me to check for that registry key, i did but didnt see it
i think the problem i had was i expanded the 'Parameters' key instead of just clicking it and checking the right pan

thanks again