No did not ask if u donated to cncnet,
no i didnt ask if u recieved help for ur problem on cncnet.
You got something without asking. You're welcome.
cant connect to others
Started by playdead, Nov 10 2016 02:55 PM
156 replies to this topic
#128
playdead
-
- Members
-
- 12 posts
Corporal
Posted 29 December 2016 - 03:49 PM
Any solution?
I was able to play by using a VPN. But since 2 days i cant connect anymore with or without VPN!
Edited by playdead, 29 December 2016 - 04:34 PM.
#129
playdead
-
- Members
-
- 12 posts
Corporal
Posted 02 January 2017 - 09:37 AM
The only benefit i got from this so called "support forum" is to learn Game Ranger.
Now i play there hassle free with more players.
#130
Posted 02 January 2017 - 11:40 AM
This is the answer u get :::
It's a peer2peer connection.. and NAT (at both sides) is problematic for those kinds of connections.
From the owner of the server and thats it GL
Sue EA / olaf ?
Edited by Showtime, 02 January 2017 - 11:47 AM.
#135
FunkyFr3sh
-
- Members
-
- 17 posts
Corporal
Posted 03 January 2017 - 08:18 AM
There are tools around you can use to test your NAT type, like this one for example:
https://www.codeproject.com/articles/18492/stun-client
If it outputs "SymmetricNat" then your chances to connect are slim to none (you can only connect to those who are not behind any NAT)
"PortRestrictedCone" should probably work, but i'm not sure what happens if the NAT device creates a mapping where the public port doesn't equal the source port. Most Peer2Peer applications can handle such cases just fine, but I'm not sure if Red Alert 2 can handle it (could be that Red Alert 2 only shares your local port with others, but not your public port)
#137
FunkyFr3sh
-
- Members
-
- 17 posts
Corporal
Posted 03 January 2017 - 09:06 AM
That's really weird indeed.
But more and more providers put their users behind NAT because of the ipv4 exhaustion. Most of the time you end up behind a "PortRestrictedCone" NAT where the public port doesn't match the source port.
If it turns out that Red Alert 2 can't handle such cases then it's a bigger problem. It should be easy to update the server to handle such cases though, from what I know, Red Alert 2 is using random source ports, that means the server actually has to share not only the ip, but also the port of each player.
The server could override the port and share the public port instead.
Everything looks like it's all about NAT problems, you guys should at least run a test and paste your results in here. Maybe it's something else, but it's impossible to tell without running tests
#138
Posted 03 January 2017 - 02:43 PM
my latest updates for windows were all on the 8th of december - seems about the right timing. (win 7 pro)
security updates for microsoft .NET framework 4 (16 of them)
microsoft .NET framework 4 Extended (5 of them)
#139
Posted 03 January 2017 - 05:06 PM
my latest updates for windows were all on the 8th of december - seems about the right timing. (win 7 pro)
security updates for microsoft .NET framework 4 (16 of them)
microsoft .NET framework 4 Extended (5 of them)
Easy to test, reinstall ur windows and disable updates, if u are able to play again u know what was causing it.
#140
Posted 03 January 2017 - 06:56 PM
why would u do such hassle when u can just uninstall/undo the most recent updates or just jump back a few weeks in time (via system restore) when ra2 was working properly
btw hpy new year every1!!!
p.s. @olaf stop trolling ppl, love ya 
That's really weird indeed.
But more and more providers put their users behind NAT because of the ipv4 exhaustion. Most of the time you end up behind a "PortRestrictedCone" NAT where the public port doesn't match the source port.
If it turns out that Red Alert 2 can't handle such cases then it's a bigger problem. It should be easy to update the server to handle such cases though, from what I know, Red Alert 2 is using random source ports, that means the server actually has to share not only the ip, but also the port of each player.
The server could override the port and share the public port instead.
Everything looks like it's all about NAT problems, you guys should at least run a test and paste your results in here. Maybe it's something else, but it's impossible to tell without running tests
ra2 uses only 1 port bro, numero 69. olaf's favorite number 
John can't joke
trolololololol, rekin rek
#143
Posted 04 January 2017 - 11:29 AM
Easy to test, reinstall ur windows and disable updates, if u are able to play again u know what was causing it.
On a works PC - i won't be reinstalling Windows. That is a ludacris solution for getting RA2 to work.
#144
Posted 04 January 2017 - 02:32 PM
This is the answer u get :::
It's a peer2peer connection.. and NAT (at both sides) is problematic for those kinds of connections.
From the owner of the server and thats it GL
Sue EA / olaf ?
He was saying it's not his problem. xD
John can't joke
Neither can you, your forum sense of humour is quite horrible.
#145
Posted 19 January 2017 - 03:34 PM
Well its not the win 7 pro edition update( at least not for me ).
My anti virus blocked my win update.(cuple of months behind)
After the update ra2 worked just fine
Edited by Showtime, 19 January 2017 - 03:35 PM.
#149
Posted 25 January 2017 - 11:58 PM
hello all players who can't connect with others play online, I just reseted my password to get a new password of my account and guess what? It got fixed. Now i can connect 1v1 or 2v2 without problems, cheerings PERUnice =)
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
