Need help setting up a Teredo Client
-
Tuesday, June 23, 2009 10:29 AMHi,
I am trying to setup Teredo CLient on Win7 -7229 Ultimate.Can somebody please help me get the teredo to a qualified state, I am using a Linksys BEFSR41 router as a switch.
Here are the IPConfig /all details:
Windows IP Configuration
Host Name . . . . . . . . . . . . : JoooJooo-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : 00-1B-AC-DB-A5-33
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1547:e265:f921:6fa1%11(Preferred)
IPv4 Address. . . . . . . . . . . : 10.223.1.175(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Lease Obtained. . . . . . . . . . : Wednesday, June 23, 2009 4:40:24 PM
Lease Expires . . . . . . . . . . : Thursday, July 01, 2009 10:40:24 PM
Default Gateway . . . . . . . . . : ::
10.223.0.1
DHCP Server . . . . . . . . . . . : 10.223.1.152
DHCPv6 IAID . . . . . . . . . . . : 234887609
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-CC-AC-F0-0019-B9-0E-B1-77
DNS Servers . . . . . . . . . . . : 10.217.160.131
10.216.16.101
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:3C16:2636:F520:FE50(Preferred)
Link-local IPv6 Address . . . . . : fe80::3C16:2636:F520:FE50%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{3905c038-596e--4414-9539-2da3a1624fb1}
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Results from Netsh int Teredo show state:
Teredo Parameters
---------------------------------------------
Type : client
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : 5 seconds
Client Port : unspecified
State : dormant
To get it into a qualified state, I used Ping -6 www.sixxs.net with the following outcome:
pinging www.m.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2001:838:1:1:210:dcff:fe20:7c7c:
Packets: Sent = 4, received = 0, lost = 4 (100% loss)
Subsequent Results from Netsh int Teredo show state:
Teredo Parameters
---------------------------------------------
Type : client
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : 5 seconds
Client Port : unspecified
State : probe (primary server)
Client Type : teredo client
Network : Unmanaged
after a couple of time the state goes to
Teredo Parameters
---------------------------------------------
Type : client
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : 5 seconds
Client Port : unspecified
State : offline
Error : Primary teredo server unreachable over UDP
and eventually the state returns to:
Teredo Parameters
---------------------------------------------
Type : client
Server Name : teredo.ipv6.microsoft.com
Client Refresh Interval : 5 seconds
Client Port : unspecified
State : dormant
Can someone please point me to the mistake that I am doing.Also am ready to debug and give you all the information that you need.
Thanks a ton in advance
Joshua
All Replies
-
Tuesday, July 07, 2009 12:01 AMHello Joshua,
Could you clarify if your machine is directly connected (not behind a NAT)? If so, Teredo will not work as you have a private ipv4 address. -
Tuesday, July 20, 2010 12:33 AM
Teredo is design especially to work behind NAT and even if you private IP
in the beginning it look that your computer already obtained 2001: address which is Teredo Address so I think it is only firewall problem check this link and make sure it is not firewall problem http://support.microsoft.com/kb/968510
-
Tuesday, July 27, 2010 9:57 AM
Hi joshua,
I can see the ipv6 address with teredo prefixx(2001:...). I think ocassionally, your primary teredo server goes unreachable. You can change the teredo server address to Microsoft's teredo server in US region by ip. It can resolve the problem if ur local region teredo server has temporary problem. Type the following to do so:
netsh int ipv6 set teredo client 65.55.158.116
You can also try installing gogo6 client software, they give free static ipv6 address for personal use.
regards,
vasanth
-
Friday, December 03, 2010 12:42 PM
Its because the Teredo state is unqualified - I think this was introduced some time back as a protected mode because IPv6 can traverse stateful firewall rules if the firewall doesnt understand IPv6
To force the teredo state into a 'Qualified' state open up gpedit.msc and under Administrative Templates > Network > TCPIP Settings > IPv6 Transition Technologies; change Teredo Default Qualified to 'enable'
You should have a bit more luck then..
Dean
- Proposed As Answer by Thomas M.T. _ Wednesday, June 20, 2012 6:56 AM
-
Wednesday, June 20, 2012 6:56 AMThis is it. Thanks Dean...
Thomas.


