Direct connect and UDP hole punch failed

[Ramaled]

When I try to connect to any server, the game gives me this message

"Attempting to find server
Direct connect and UDP hole punch failed
Requesting relay token
No response from any available relay
Connection to server has failed"

This is on every server I've tried, I've erased every mod and tried to connect to a vanilla server and it gives me the error too

I've given the game permission in the firewall and I've completely shutted down the firewall and it still gives me the error.

I've tried to forward ports 5121 and 5123, I dont know if I've done it succesfully because it still fails to connect

I've also tried to install the development build and play on a server with a friend who also has the same version, still the same message

I don't know what to do, when I bought the game the first day it worked just fine, but then it started to fail every connection. Any ideas?

[DefiantShade]

https://steamcommunity.com/app/704450/discussions/0/1696043263490494797/

Try this post hopefully helps you out.

[AvatarOfWar]

I had the same exact problem, and went through Beamdogs dedicated support forum, but got zero help from them. Later on I saw they quietly slipped in a one-liner comment in some patch notes about fixing a problem related to this, which mysteriously happened around the time my problem fixed itself.

Basically, the problem was with servers that change the port they accept incoming connections on. Sometimes it would just... change... for no reason (at least, none I could figure out), but the server browser won't reflect that.

If you are logging in to this server through your Favorites or History, try clicking "server details" and looking at the IP address. Then go to the master server list, find your server, then click "server details" on that. I'll bet the port address is different. You should then be able to log in through the server list, even if you can't log in through your favorites.

But, that didn't ALWAYS work for me either... but I don't know if theres any better help to be had on this issue. :(

[AvatarOfWar]

Originally posted by DefiantShade:

https://steamcommunity.com/app/704450/discussions/0/1696043263490494797/

Try this post hopefully helps you out.

The only thing thats in that entire thread is "try port-forwarding" and a link to a completely different problem (first-time logging into a server and being rejected due to username).

[Julius Borisov]

@Ramaled I recommend to file this issue on support.baldursgate.com - our bug tracker where you can hear directly from the QA.

[Shezza]

Possibly related issue

https://steamcommunity.com/app/704450/discussions/0/1748980761798997501/

deleting cdkey.ini and letting steam fetch a new one fixed this for me

[AvatarOfWar]

Dude, there have been 7 months time and at least 2 patches that addressed this problem already. This has been solved for a while now.

[APP0LL0]

@avatarofwar where has this been fixed? You know whic patch or where one can be found am having problems connecting now..

[AvatarOfWar]

Why would I know? I quit NWN:EE before I even made that LAST angry post regarding necroposting a dead thread.

[Velovar]

just got the game... same problem

[Ettanin]

Originally posted by https://steamcommunity.com/games/704450/announcements/detail/1590258590964020046:

Networking relays are still nonfunctional. We will have to address further-reaching changes to the network protocol for the upcoming console release. Any related fixes and features, such as better NAT traversal, have been postponed for now.

Until this is fixed you or the server need a dedicated IPv4 address and Port 5121 UDP forwarded. Nwn has no support for IPv6.

If your ISP grants you DSLite only (shared IPv4 and dedicated IPv6) , the only way to fix this is by getting a VPN that grants a dedicated IPv4 address or using tunnel services like Hamachi on both clients and server.

[Nilruin]

Originally posted by AvatarOfWar:

Dude, there have been 7 months time and at least 2 patches that addressed this problem already. This has been solved for a while now.

This is definitely not solved. I was running a server fine, up until yesterday, when my friends began getting this exact same error. Nothing has changed, settings-wise, on my end.

[Ettanin]

Originally posted by Nilruin:

Originally posted by AvatarOfWar:

Dude, there have been 7 months time and at least 2 patches that addressed this problem already. This has been solved for a while now.

This is definitely not solved. I was running a server fine, up until yesterday, when my friends began getting this exact same error. Nothing has changed, settings-wise, on my end.

Look at the date of that post... No need to flame them for something that has been solved in the past and is currently broken intentionally for other reasons.

[Nilruin]

Is it broken intentionally by Beamdog? and if so, what for?

[Ettanin]

Originally posted by Nilruin:

Is it broken intentionally by Beamdog? and if so, what for?

"Networking relays are still nonfunctional. We will have to address further-reaching changes to the network protocol for the upcoming console release. Any related fixes and features, such as better NAT traversal, have been postponed for now."

See current dev build notes. This Note also applies for the current stable Version. The only fix currently is getting a dedicated IPv4 address and forwarding UDP 5121. Dual Stack lite users need to get a VPN that provides a dedicated IPv4 address because IPv6 is not supported.

[Nilruin]

It worked two days ago, when I last ran a server. If it stopped working, that's usually considered an error of some kind. If this isn't considered an error, and Beamdog intentionally broke server-side support from Steam, I want a refund, because this game isn't working as when purchased.