Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
After a ton of research, I've narrowed it down to my router. Basically, when connecting to the Siege servers, my router will only let one of us receive data because the network itself only has one IP, even though our computers have different static IPs.
I found a solution. I am getting a second public IP address from my ISP, which will completely resolve the problem.
So I just encountered this problem myself last night, and after a ♥♥♥♥♥♥♥♥ of troubleshooting I got it figured out:
First, I want to say that I believe this error can be caused by a bunch of different network configuration conflicts (primarily due to Ubisoft's lazy/♥♥♥♥♥♥ code) and so this solution might not necessarily work for you. However, it can hopefully help you identify some other troubleshooting things to try.
So our setup was: I have a Windows 7 Asus 55vw ROG laptop, my friend has a windows 10 desktop with an 5 year old built in wireless adapter, and we were both connecting to a Arris SBG6700-AC modem/router combo through wifi.
The Problem: Both of us could not connect to R6 at the same time. The first person to connect would get in fine, but the second person would get stuck at "Creating Squad". If, however, the windows 10 pc connected first, then it didn't matter if we shutdown both computers/rebooted them, the windows 7 laptop would get stuck at "Creating Squad" every time while the windows 10 pc would continue to function. The only way to let the windows 7 PC connect again was to reboot the router/modem. (This reboot still would only allow 1 pc on at a time).
The SOLUTION: The Windows 7 laptop could connect through wifi along with the Windows 10 PC ONLY when the Windows 10 PC was connected through a wired connection (and had wifi off). If at any point the Windows 10 PC had started R6 while connected through wifi, then the Windows 7 PC would get stuck at the "Creating Squad" screen until the router/modem was rebooted.
Things that didn't work for us (note, these might work for you):
1. Port forwarding did nothing. I tired forwarding Ubisofts recommended ports, and then later I tried forwarding ports 1200 UDP and 9013 UDP b/c they seemed to be the ports used by R6 the most according to TCPview
2. IMPORTANT: Putting the Windows 7 PC on a wired connection and leaving the Windows 10 PC on wireless DID NOT solve our problem, it had to be the Windows 10 PC that was wired. We did not test having both PC's on a wired connection.
2. Disabling uPnP had no effect on our problem. Neither did enabling uPnP
3. Static IP's had no effect on our problem.
4. Setting one of us as the DMZ host had no effect on our problem.
5. Turning off multicasting had no effect on our problem.
6. Port Triggering had no effect on our problem (however, I'm not super familiar with port triggering and am not necessarily sure I did it correctly)
7. I'm pretty sure this issue has something to do with the fact that Ubisoft wont allow you to change the ports that your game operates through. This causes both PC's to fight over control of the port. I have no idea why Ubisoft doesn't allow this (probably because they are lazy), and unfortunately, I could not find any work around to get R6 to use a different port.
7.5. ^That being said, I'm not exactly sure why wiring in the Windows 10 PC helped if this is a port issue. Maybe this has something to do with how Windows 10 handles ports/ip's as compared to Windows 7? Either way, my games working now, and I spent so much time trying to solve this that I'm done exploring the question.
Hope this helps you solve your troubles! Good luck! (and Ubisoft, if you're listening... please look at this problem, it's pretty ridiculous)
Hi Snowy - could you please tell me which router you bought? We have the same problem, but I've tried a few routers and none work, so it would be good to get one that does - thanks!
D
Hey D,
We haven't pulled the trigger on any routers yet. If we do, I'll be sure to get back to you and let you know what happens!
Here:
https://youtu.be/tApX5efOsSA
I might be a bit late for some of you, but i could be the hero for the one's who still experience this issue. I had the same problem, i kept dc'ing of the squad when i was in it together with my brother or anyone else on the same network.
What i did was enabling UPnP on my router AND modem (or only modem if you are directly connected to the modem of course). When they both are enabled, restart the game (not sure if uplay needs a restart). After a few seconds, it will automatically port-forward your ports for any user that requires it. (if your router/modem doesn't support UPnP, then i don't know what to do unfortunately, but im sure modern one's should support it nowadays).
Your NAT type will be "open" for every game you play when UPnP is enabled on all network devices you pass (router and modem) and port-forwarding the ports manually isn't required anymore. Ever since i enabled it (2 days ago), i never dc'ed of the squad again when my brother was in it too.
I hope i could help others solve their problem too :)
I used a free one Proton VPN