[SOLVED] Teredo problems

[Nyaalit]

I've been trying to play Forza Horizon online but when i click on find multiplayer game it searches forever and i heard its caused because of "Teredo". My knowledge about networking is next to nothing but i tried the things that came out first in google such as:

1. Check your Internet connection.
2. Uninstall and reinstall the Teredo adapter.
3. Check if the startup type of IP Helper is set to automatic.
4. Set the Teredo server name to its default.
5. Delete unnecessary entries.

And none of them worked for me
When i do "netsh interface teredo show state" in cmd it displays
Type: client (Group Policy)
Server Name : win1910.ipv6.microsoft.com
Client Refresh Interval : 30 seconds (Group Policy)
Client Port : 3544
State : offline
Error : Client is in a managed network
Am not even sure this is the right place to ask but this is my first post in this forum. Please help.

 

[LinuxDevice]

This is entirely speculation, and my only knowledge of Teredo is what I've read about it. Teredo seems to act as an adapter for newer IPv6 addresses which need to traverse IPv4-only networks. If for some reason such a tunnel reaches an end point which does not allow continuing of the IPv6, then I could see the need to use some other end point. Or, if you have control of some of the addresses, if the address is available in both IPv6 and IPv4, then you could skip using Teredo by manually setting to the IPv4 address (if it exists, and if you have that ability to edit the address).

Similarly, if your software does work with IPv6 over Teredo, then I suspect that if your DNS server only looks at IPv4, then your address lookup is what is really failing. Normally DNS provides a dotted-decimal address (or the IPv6 equivalent) for a named address. A DNS server which serves an entirely IPv4 net might not even bother to convert an IPv6 even if the name to number request arrives intact. Naming a different DNS server, which serves IPv6, and which your Teredo can be pointed to, would likely solve the problem if DNS is the problem.

 

[Nyaalit]

This is entirely speculation, and my only knowledge of Teredo is what I've read about it. Teredo seems to act as an adapter for newer IPv6 addresses which need to traverse IPv4-only networks. If for some reason such a tunnel reaches an end point which does not allow continuing of the IPv6, then I could see the need to use some other end point. Or, if you have control of some of the addresses, if the address is available in both IPv6 and IPv4, then you could skip using Teredo by manually setting to the IPv4 address (if it exists, and if you have that ability to edit the address).

Similarly, if your software does work with IPv6 over Teredo, then I suspect that if your DNS server only looks at IPv4, then your address lookup is what is really failing. Normally DNS provides a dotted-decimal address (or the IPv6 equivalent) for a named address. A DNS server which serves an entirely IPv4 net might not even bother to convert an IPv6 even if the name to number request arrives intact. Naming a different DNS server, which serves IPv6, and which your Teredo can be pointed to, would likely solve the problem if DNS is the problem.

I barely understood what you said and i also don't know how to name a different DNS server

 

[LinuxDevice]

I barely understood what you said and i also don't know how to name a different DNS server

Someone else will have to help with that, but the gist is that the internet was originally all IPv4 protocol (version 4 internet protocol). Almost everything still uses that protocol. IPv6 was invented to deal with running out of address space since there are so many devices no on the internet. Some older software was never told how to use IPv6, and must use IPv4. End user software wouldn't be able to directly reach an IPv6 address if running on a purely IPv4 network (a network not capable of understanding IPv6).

However, a tunnel can use IPv4 to talk to some other point in the network which goes through IPv4-only network route hops and pass traffic which the IPv4 hardware and software has no need to understand...but the tunnel needs a second computer somewhere out in the wild to accept the other side of the tunnel. This is apparently what the purpose of Teredo is...to run on IPv4-only networks and to provide a tunnel to some outside part of the world which is not so antiquated, and that outside world end point would understand the newer IPv6.

DNS is a service to look up a name and find a numeric address. All routing, under the covers, uses numeric addresses. When you web browse or do anything going to a remote address with a name, e.g., "tomshardware.com", then DNS looks up the numeric version of the address before sending out a request to connect. DNS is almost always set up automatically by Windows. If your hardware and software combination is not capable of IPv6, then the DNS server which was automatically set up might also ignore IPv6 requests and never convert the name to an address. The automatic DNS setup could possibly have no knowledge of Teredo and ignore it. If DNS is the issue, then you need to move your DNS server setup away from the automatically set up DNS, and aim it instead at a DNS server which is further down the internet line at or after the Teredo end point (the far end of the tunnel). In theory this would guarantee using a DNS server which understands IPv6.

But to emphasize, I am just guessing. And someone else would have to be able to tell you how to set up an alternate DNS from an IPv6-capable DNS server.

 

[Nyaalit]

Someone else will have to help with that, but the gist is that the internet was originally all IPv4 protocol (version 4 internet protocol). Almost everything still uses that protocol. IPv6 was invented to deal with running out of address space since there are so many devices no on the internet. Some older software was never told how to use IPv6, and must use IPv4. End user software wouldn't be able to directly reach an IPv6 address if running on a purely IPv4 network (a network not capable of understanding IPv6).

However, a tunnel can use IPv4 to talk to some other point in the network which goes through IPv4-only network route hops and pass traffic which the IPv4 hardware and software has no need to understand...but the tunnel needs a second computer somewhere out in the wild to accept the other side of the tunnel. This is apparently what the purpose of Teredo is...to run on IPv4-only networks and to provide a tunnel to some outside part of the world which is not so antiquated, and that outside world end point would understand the newer IPv6.

DNS is a service to look up a name and find a numeric address. All routing, under the covers, uses numeric addresses. When you web browse or do anything going to a remote address with a name, e.g., "tomshardware.com", then DNS looks up the numeric version of the address before sending out a request to connect. DNS is almost always set up automatically by Windows. If your hardware and software combination is not capable of IPv6, then the DNS server which was automatically set up might also ignore IPv6 requests and never convert the name to an address. The automatic DNS setup could possibly have no knowledge of Teredo and ignore it. If DNS is the issue, then you need to move your DNS server setup away from the automatically set up DNS, and aim it instead at a DNS server which is further down the internet line at or after the Teredo end point (the far end of the tunnel). In theory this would guarantee using a DNS server which understands IPv6.

But to emphasize, I am just guessing. And someone else would have to be able to tell you how to set up an alternate DNS from an IPv6-capable DNS server.

Thanks for the thorough explanation but i managed to fix it with a vid i saw. Am not even sure what i did but it worked.
Here's a link to the vid :

View: https://www.youtube.com/watch?v=OCc0BiPHpR8

 

[LinuxDevice]

Thanks for the thorough explanation but i managed to fix it with a vid i saw. Am not even sure what i did but it worked.
Here's a link to the vid :

View: https://www.youtube.com/watch?v=OCc0BiPHpR8

The video is basically changing a server. This is probably changing to a server (the outside world end point) with better IPv6 support. Don't know.