Page 1 of 2
Connection Attempt Failed to NAT Server
Posted: Mon Feb 09, 2015 3:18 am
by gravyboat
Hi!
One of the players in our (small) group has a problem in multiplayer (I'm the one posting it since I am more fluent in English and have more technical expertise).
When connecting to a game / staging area through direct connect or lobby:
Code: Select all
Attempting Connection to NAT Server...
<MULTI> Connection Attempt Failed to NAT Server.
When trying to host a game same thing:
Code: Select all
Attempting Connection to NAT Server...
<MULTI> Connection Attempt Failed to NAT Server.
Subsequent connection attempts fail.
Connecting to the multiplayer lobby: Works fine.
What I tried with him:
SPOILER: SHOW
-forwarding and using a few different ports, including 31791
-uPnP on router enabled
-dhcp on router dis-/enabled
-dynamic IP/static IP switch
-DMZ the whole machine on the router, bypassing local NAT
-disabling router firewall
-disabling windows firewall
-uninstalling any kind of firewall/antivirus
-setting networking card metric to high/low settings
-checking several netstat things
-checking several ipconfig things
-running executable directly with admin/WinXP compatibility
-uninstalling and re-installing the game
What we could not try:
SPOILER: SHOW
-different ISP
-different local network on same ISP
-different computer in same local network
-traceroute that NAT server (for lack of adress)
So far no joy.
-Additional info-
OS is Windows 7
Version is 1.6100
No mods are or were installed
---
I really don't know what to do anymore here.
Any ideas or any details on that NAT server?
I've only seen it being mentioned
once so far.
Best regards
gravyboat
Re: Connection Attempt Failed to NAT Server
Posted: Mon Feb 09, 2015 3:52 am
by voltigeur
edit: sorry was on a completely wrong tack with my original post.
You're right, seems that a stand alone nat server is being used. If it's the Slitherine one, it is unreliable and there are many complaints with other Matrix games about disconnections etc (eg Close Combat).
Edit 2: the game sends udp packets to 50.56.225.37 which resolves to rackspace ip ranges based somewhere in Texas.
So it seems that your friends machine is having issues reaching that address. Try a tracert? Could be an isp issue.
If anyone from NSD is reading, can I please ask - can an option to bypass the remote nat server be made available (or perhaps there is already this option?) for those who understand port forwarding please (even an .ini setting would be just fine). At least for Waterloo? That would be great for those of us who play multiplayer in Australia (ie all players are in AU...)
cheers
Re: Connection Attempt Failed to NAT Server
Posted: Wed Feb 11, 2015 4:23 pm
by gravyboat
Did some traceroutes to 50.56.225.37
Friend #1
SPOILER: SHOW
Code: Select all
1 <1 ms <1 ms <1 ms easy.box [192.168.2.1]
2 59 ms 38 ms 39 ms ASPIRE-PC [10.218.35.12]
3 48 ms 40 ms 35 ms 92.79.230.129
4 45 ms 47 ms 45 ms 92.79.213.170
5 47 ms 55 ms 48 ms xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26]
6 49 ms 48 ms 58 ms ae8.mpr1.fra3.de.zip.zayo.com [64.125.26.233]
7 60 ms 57 ms 66 ms ae4.cr1.ams5.nl.zip.zayo.com [64.125.32.106]
8 62 ms 55 ms 63 ms ae0.cr1.ams10.nl.zip.zayo.com [64.125.27.62]
9 62 ms 63 ms 66 ms ae9.mpr3.lhr3.uk.zip.zayo.com [64.125.28.242]
10 60 ms 59 ms 59 ms 64.125.28.21
11 138 ms 137 ms 139 ms ae4.cr1.dca2.us.zip.zayo.com [64.125.20.73]
12 181 ms 164 ms 158 ms ae5.cr1.iah1.us.zip.zayo.com [64.125.20.186]
13 167 ms 162 ms 160 ms ae0.cr1.dfw2.us.zip.zayo.com [64.125.20.197]
14 167 ms 165 ms 164 ms ae11.er1.dfw2.us.zip.zayo.com [64.125.20.66]
15 177 ms 171 ms 173 ms 128.177.70.86.IPYX-076520-900-ZYO.zip.zayo.com [128.177.70.86]
16 * * * Zeitüberschreitung der Anforderung. //"request timed out"
17 170 ms 168 ms 170 ms be42.coreb.dfw1.rackspace.net [74.205.108.125]
18 175 ms 169 ms 174 ms po2.coreb-core10.core10.dfw3.rackspace.net [74.205.108.51]
19 165 ms 162 ms 161 ms aggr150b-1-core4.dfw2.rackspace.net [50.56.129.195]
20 168 ms 170 ms 172 ms 50-56-225-37.static.cloud-ips.com [50.56.225.37]
This is the one with the problem.
--
Me
SPOILER: SHOW
Code: Select all
1 3 ms 4 ms 5 ms speedport.ip [192.168.2.1]
2 10 ms 13 ms 10 ms 217.0.119.53
3 11 ms 11 ms 11 ms 217.0.65.246
4 17 ms 14 ms 16 ms 217.239.48.166
5 14 ms 16 ms 15 ms ffm-b12-link.telia.net [213.248.103.169]
6 15 ms 14 ms 16 ms ffm-bb2-link.telia.net [62.115.142.60]
7 101 ms 103 ms 103 ms ash-bb4-link.telia.net [213.155.135.59]
8 144 ms 143 ms 140 ms dls-b21-link.telia.net [213.155.135.3]
9 142 ms 144 ms 141 ms rackspace-ic-302090-dls-bb1.c.telia.net [62.115.33.78]
10 144 ms 151 ms 145 ms 10.25.1.71
11 150 ms 144 ms 144 ms 74.205.108.121
12 147 ms 145 ms 140 ms po1.corea-core9.core9.dfw3.rackspace.net [74.205.108.45]
13 148 ms 150 ms 150 ms aggr150a-1-core3.dfw2.rackspace.net [50.56.129.193]
14 147 ms 142 ms 143 ms 50-56-225-37.static.cloud-ips.com [50.56.225.37]
Working fine, different ISP than #1.
--
Friend #2
SPOILER: SHOW
Code: Select all
1 3 ms 2 ms 2 ms speedport.ip [192.168.2.1]
2 22 ms 21 ms 22 ms 217.0.119.217
3 27 ms 23 ms 25 ms 87.190.168.194
4 26 ms 27 ms 25 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.34]
5 32 ms 25 ms 30 ms ffm-b12-link.telia.net [213.248.103.169]
6 33 ms 28 ms 28 ms ffm-bb1-link.telia.net [62.115.142.14]
7 120 ms 120 ms 114 ms nyk-bb1-link.telia.net [213.155.135.61]
8 160 ms 160 ms 159 ms dls-b21-link.telia.net [213.248.80.142]
9 158 ms 159 ms 158 ms rackspace-ic-302090-dls-bb1.c.telia.net [62.115.33.78]
10 * * * Zeitüberschreitung der Anforderung. //"request timed out"
11 166 ms 164 ms 167 ms be42.coreb.dfw1.rackspace.net [74.205.108.125]
12 161 ms 163 ms 163 ms po2.coreb-core10.core10.dfw3.rackspace.net [74.205.108.51]
13 160 ms 159 ms 161 ms aggr150b-1-core4.dfw2.rackspace.net [50.56.129.195]
14 161 ms 160 ms 165 ms 50-56-225-37.static.cloud-ips.com [50.56.225.37]
This one is working fine as well and has the same ISP as me.
--
Friend #3
SPOILER: SHOW
Code: Select all
1 <1 ms <1 ms <1 ms megateil.wh30.tu-dresden.de [141.30.202.1]
2 <1 ms <1 ms <1 ms 141.30.4.93
3 1 ms <1 ms <1 ms 141.76.0.53
4 <1 ms <1 ms <1 ms 141.76.0.49
5 <1 ms <1 ms <1 ms 141.76.0.37
6 <1 ms <1 ms <1 ms 141.76.0.25
7 3 ms 3 ms 4 ms cr-tub1-hundredgige0-1-0-1.x-win.dfn.de [188.1.243.29]
8 14 ms 14 ms 14 ms xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26]
9 14 ms 14 ms 14 ms ae8.mpr1.fra3.de.zip.zayo.com [64.125.26.233]
10 20 ms 20 ms 20 ms ae4.cr1.ams5.nl.zip.zayo.com [64.125.32.106]
11 21 ms 21 ms 22 ms ae0.cr1.ams10.nl.zip.zayo.com [64.125.27.62]
12 25 ms 25 ms 26 ms ae9.mpr3.lhr3.uk.zip.zayo.com [64.125.28.242]
13 25 ms 25 ms 25 ms 64.125.28.21
14 97 ms 97 ms 97 ms ae4.cr1.dca2.us.zip.zayo.com [64.125.20.73]
15 121 ms 121 ms 122 ms ae5.cr1.iah1.us.zip.zayo.com [64.125.20.186]
16 129 ms 128 ms 128 ms ae0.cr1.dfw2.us.zip.zayo.com [64.125.20.197]
17 130 ms 130 ms 130 ms ae11.er1.dfw2.us.zip.zayo.com [64.125.20.66]
18 132 ms 132 ms 132 ms 128.177.70.86.IPYX-076520-900-ZYO.zip.zayo.com [128.177.70.86]
19 * * * Zeitüberschreitung der Anforderung. //"request timed out"
20 132 ms 132 ms 132 ms be41.corea.dfw1.rackspace.net [74.205.108.113]
21 134 ms 134 ms 134 ms po1.corea-core9.core9.dfw3.rackspace.net [74.205.108.45]
22 134 ms 134 ms 134 ms aggr150a-1-core3.dfw2.rackspace.net [50.56.129.193]
23 133 ms 133 ms 133 ms 50-56-225-37.static.cloud-ips.com [50.56.225.37]
Only has the demo of SoW so far and since that is from before NAT server times the status of his game is yet to be determined. Would be interesting since he has a different ISP than anyone else.
--
On the last note: I told friend #1 to download the demo v1.1 to check with #3 if the pre-NAT-Multiplayer works for him. Still waiting on results, though.
Re: Connection Attempt Failed to NAT Server
Posted: Wed Feb 11, 2015 4:51 pm
by voltigeur
well all three trace routes seem to be able to reach the nat server, and much faster than from where I am (260ms).
So not really sure what is up.
Hopefully Norb may be able to suggest something
cheers
Re: Connection Attempt Failed to NAT Server
Posted: Tue Feb 17, 2015 10:34 pm
by Morsey
I am having the same trouble and I am from Costa Rica it just started on Sunday. I do know that some sites block IP from some countries that are know to be hacker prone, CR is one of them. More than once I have had to ask for my IP to be unblocked from a site or 2.
Here is my tracert
Tracing route to 50-56-225-37.static.cloud-ips.com [50.56.225.37]
over a maximum of 30 hops:
1 35 ms 42 ms 44 ms 10.209.72.1
2 50 ms 48 ms 50 ms 10.178.138.94
3 52 ms 54 ms 50 ms 201.195.126.1
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 95 ms 87 ms 98 ms so-6-1-0.usa.nam-core02.columbus-networks.com [6
3.245.47.125]
9 93 ms 88 ms 87 ms 63.245.5.221
10 88 ms 85 ms 92 ms mai-b1-link.telia.net [213.248.89.161]
11 112 ms 109 ms 109 ms atl-bb1-link.telia.net [62.115.141.161]
12 134 ms 132 ms 116 ms dls-b21-link.telia.net [213.155.133.126]
13 133 ms 126 ms 132 ms rackspace-ic-302090-dls-bb1.c.telia.net [62.115.
33.78]
14 * * * Request timed out.
15 133 ms 128 ms 106 ms be41.corea.dfw1.rackspace.net [74.205.108.113]
16 127 ms 177 ms 138 ms po1.corea-core10.core10.dfw3.rackspace.net [74.2
05.108.49]
17 130 ms 118 ms 126 ms aggr150a-1-core10.rackspace.net [74.205.38.95]
18 126 ms 128 ms 128 ms 50-56-225-37.static.cloud-ips.com [50.56.225.37]
Trace complete.
Re: Connection Attempt Failed to NAT Server
Posted: Wed Feb 18, 2015 12:20 am
by Morsey
I was able to start up a server using a VPN tunnel which gives me an IP from San Jose Cali. with no problem. NorbSoft has blocked Costa Rican and other countries IPS...LMBO
Can I get a refund......LOL
It now works was able to start a server, someone must have had the blocked countries removed. Not an uncommon thing to happen hope friends game works now.
THANKS who ever you are! :cheer:
Re: Connection Attempt Failed to NAT Server
Posted: Wed Feb 18, 2015 8:24 pm
by gravyboat
NorbSoft has blocked Costa Rican and other countries IPS...
[...]
It now works was able to start a server, someone must have had the blocked countries removed.
Since the problem started for you only on Sunday and is gone by Tuesday, less than an hour after your post here, I'd say it's not very likely that there was some country-blocking conspiracy involved. I may be wrong of course, but I guess that would be a different matter.
All three of us (2x working, 1x not working) are from Germany, so no kind of country-blockade here. At worst the specific ISP of friend #1 could be blocked. But then again he probably wouldn't get a returning ping in his tracert then.
--
That being said, a look at mentioned technical options:
A pure VPN like Hamachi probably woouldn't help at all with the specific problem (unless we can include the NAT server in that VPN and change the targeted IP, lol).
A SOCKS proxy or a VPN offering said proxy (as described by Morsey) on the other hand would be interesting. I would very much like to refrain from having to deal with that for just one game, though, as VPNs tend to create all kinds of other problems. So this would be my last last
last resort, really.
--
No news yet about the demo working or not. Them lazy friends. XP
Re: Connection Attempt Failed to NAT Server
Posted: Wed Feb 18, 2015 8:40 pm
by Morsey
It was probably not NORB SOFT/Slitherine should have put the hosting company of the server that was my bad.
I have run into this same problem with other servers companies. GCM SOWMP hosting company Site5 has done it a few times.
Unfortunately Costa Rica is one of the hubs for hacker traffic,within the top 10 world wide so they have a valid reason for blocking them.
Was just going on my past experience.
Either way it is fixed and I appreciate however it was done.
Thanks
Good Points about the VPN. I never use the VPN for gaming I lagg enough as it is. I use it to access some sites in the states that won't let me access them from here. It is also a good tool to see if my CR ip has been blocked.
Re: Connection Attempt Failed to NAT Server
Posted: Mon Feb 23, 2015 12:18 am
by BoldRover
Not sure if gravyboat's friend problem is solved? If not, try using another port in the MP gui.
Re: Connection Attempt Failed to NAT Server
Posted: Fri Feb 27, 2015 3:44 am
by gravyboat
Not sure if gravyboat's friend problem is solved? If not, try using another port in the MP gui.
The original problem still persists. We already tried using a different port to no avail. =(