Tom Clancy's Rainbow Six Siege

Tom Clancy's Rainbow Six Siege

This topic has been locked
SnowyCroww Feb 13, 2016 @ 5:28pm
Can't play with others on same network
I'm sure this has been brought up before, and I have seen the issues mentioned many times for various games over the years.

When playing Rainbow Six: Siege (pc), my roommate and I can not play at the same time. We obviously have completely separate computers, Steam accounts, Uplay accounts, etc. We have a single network for the household, with both of our computers wired to the router.

Alone, we can connect to the servers without a single problem. However, if I am already playing this game, my roommate is unable to connect to the Siege servers at all, and vice versa. The screen says "connecting to Rainbow Six servers," then it proceeds to the "creating squad" loading screen, and this is where the error message appears and puts his game in offline mode.

I have tried port-forwarding, DMZ, disabling/enabling UPnP, and a thousand other things. Has anyone found a fix for this issue at all? Help would be greatly appreciated.

Also, I am aware of Steam's game launcher parameters to set a default port, but does Uplay have a similar feature?
< >
Showing 1-15 of 17 comments
KoalafiedKiller Feb 13, 2016 @ 7:35pm 
Hmm, I do not have this problem when my friend comes over. The only thing is I'm wired to the router and he uses WiFi. Also my NAT is open. Other than that I never did anything specific to get it to work. If your NAT isn't set to open that would probably be the best starting point.
SnowyCroww Feb 14, 2016 @ 12:36pm 
Thanks for the reply. My NAT is Open, and so is my roommates. Apparently there are quite a few people having this problem, but then there are others that seem to have zero issues at all.

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.
Mr Breeze Feb 14, 2016 @ 12:48pm 
I have a single public IP and have had no issues like this with up to 10 people playing R6S in the same house at the same time on the same internet connection. I'm convinced it might be related to how the modem and/or router are handling NAT from the internet to your local LAN or some specific issue with the ISP.
MagicMissile Jul 31, 2016 @ 10:10am 
Has anyone found a solution to this aside from requesting a second wan IP?
VOIDJUICE™ Jan 12, 2017 @ 11:43am 
Hey everyone,

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)
F0r3st12 Jun 26, 2017 @ 1:10pm 
Just moved in with some friends and having this issue now. I haven't tried port forwarding as I think it wouldn't make sense to do that with multiple devices, but have tried messing with uPnP and changing to iPv6 from iPv4. Using a Linksys router. I have played with others on the same network successfully. Hoping this issue gets a little more visibility. I've shared this link on Reddit and posted my own but it seems bound to get buried.
SnowyCroww Jul 27, 2017 @ 10:10pm 
I haven't replied to this post for quite a while, but my problem was solved after simply buying a new router. It's not the most ideal solution for everyone, obviously, but as soon as I set up the new router everything worked flawlessly. I didn't even have to mess with any settings. My suggestion is to just split the cost of a new router with your buddies, and don't get something cheap. We spent about $120 on a decent router at Best Buy. So only $40 each, and have had zero problems playing anything together.
F0r3st12 Aug 1, 2017 @ 8:50pm 
Was talking to my coworker today about doing this exact thing. Thanks for following up on the thread, SnowyCroww.
Rigby Aug 1, 2017 @ 9:00pm 
Originally posted by SnowyCroww:
Thanks for the reply. My NAT is Open, and so is my roommates. Apparently there are quite a few people having this problem, but then there are others that seem to have zero issues at all.

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.
Have you tested this in other games? It might just be siege that's wonked...their servers aren't the greatest. I get disconnected often.
denis.thornton Aug 20, 2017 @ 6:56am 
Originally posted by SnowyCroww:
I haven't replied to this post for quite a while, but my problem was solved after simply buying a new router. It's not the most ideal solution for everyone, obviously, but as soon as I set up the new router everything worked flawlessly. I didn't even have to mess with any settings. My suggestion is to just split the cost of a new router with your buddies, and don't get something cheap. We spent about $120 on a decent router at Best Buy. So only $40 each, and have had zero problems playing anything together.


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
F0r3st12 Aug 23, 2017 @ 11:29am 
Originally posted by denis.thornton:
Originally posted by SnowyCroww:
I haven't replied to this post for quite a while, but my problem was solved after simply buying a new router. It's not the most ideal solution for everyone, obviously, but as soon as I set up the new router everything worked flawlessly. I didn't even have to mess with any settings. My suggestion is to just split the cost of a new router with your buddies, and don't get something cheap. We spent about $120 on a decent router at Best Buy. So only $40 each, and have had zero problems playing anything together.


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!
sfadul Oct 23, 2017 @ 1:50pm 
Hi, this may be a little late, but I found a possible solution for PS4, maybe it works for PC too.

Here:

https://youtu.be/tApX5efOsSA

DreamGoesOn. Feb 21, 2018 @ 1:01am 
Hi

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 :)
Oxide Jun 13, 2019 @ 10:45pm 
I had the same problem the only way I got around this was using a VPN and setting it to Canada.
I used a free one Proton VPN :lunar2019coolpig:
Zakary Jun 21, 2019 @ 9:17pm 
I fixed this Rainbow 6 Siege Error between me & my room mate. By giving every device on my network a static IP.
< >
Showing 1-15 of 17 comments
Per page: 1530 50

Date Posted: Feb 13, 2016 @ 5:28pm
Posts: 17