Menu
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
423 Views
Message 1 of 13
Flag for a moderator

Rainbow 6 Siege connection Issues

My R6S has been having a constant issue with lags and stutters that are killing it for me. I've tried everything that wasn't technical up until now and it hasn't solved anything:

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1402750000-2.538256 qam25
2218750000-140256 qam11
3226750000-138256 qam12
4234750000-1.238256 qam13
5242750000-1.440256 qam14
6250750000-1.440256 qam15
7258750000-1.538256 qam16
8266750000-1.440256 qam17
9274750000-1.440256 qam18
10282750000-1.738256 qam19
11290750000-238256 qam20
12298750000-238256 qam21
13306750000-238256 qam22
14314750000-1.938256 qam23
15322750000-1.738256 qam24
16410750000-2.238256 qam26
17418750000-238256 qam27
18426750000-2.238256 qam28
19434750000-2.238256 qam29
20442750000-2.738256 qam30
21450750000-3.238256 qam31
22458750000-4.537256 qam32
23466750000-4.438256 qam33
24474750000-3.938256 qam34



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.9320
2Locked40.3320
3Locked38.6190
4Locked38.9220
5Locked40.3250
6Locked40.3240
7Locked38.9180
8Locked40.3260
9Locked40.3160
10Locked38.9200
11Locked38.6170
12Locked38.9210
13Locked38.6330
14Locked38.9380
15Locked38.9300
16Locked38.6340
17Locked38.6170
18Locked38.9280
19Locked38.6120
20Locked38.6120
21Locked38.6350
22Locked37.62020
23Locked38.6750
24Locked38.6470

 

0 Kudos
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
421 Views
Message 2 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1603000004.15512064 qam1
2394000004.05512064 qam4
3462000004.1512064 qam3
4537000004.3512064 qam2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

Network Log

Time Priority Description

04/08/2020 19:28:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2020 20:14:24noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2020 20:07:52Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/08/2020 06:46:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/07/2020 17:42:16noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/07/2020 17:42:16ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/07/2020 03:44:6ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2020 17:55:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2020 13:46:0ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2020 07:13:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/07/2020 10:37:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/07/2020 10:37:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/07/2020 10:37:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/07/2020 18:48:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2020 07:20:0noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2020 07:20:0ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2020 01:48:50ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2020 22:37:13criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2020 20:17:45ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2020 09:18:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

By these dates i believe they were all logged when i was trying to play the game.

0 Kudos
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
417 Views
Message 3 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

Also i tried contacting Ubisoft but they told me to do port forwarding on the router through my computer but they didn't exactly tell how to fill in the fields and they pretty much just quit the case by saying i need to contact you guys on how to fill in the fields. But other people in here seem to have solved it another way so i'll try that before changing setting on my router.

0 Kudos
Reply
Highlighted
  • 3.25K
  • 135
  • 190
Forum Team
Forum Team
361 Views
Message 4 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

Thanks for the post Xornedge and welcome to our community.

 

We can't see any errors on our side, is this happening through wired connections? 

 

Thanks, Emily.

0 Kudos
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
350 Views
Message 5 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

It is happening since before i bought an internet cable if that is what you are asking. But i don't know much as to why. As i mentioned before they couldn't find a problem so they told me to do port forwarding but i don't know what i should be changing. So i though of asking or using an alternative solution if you guys had any.
0 Kudos
Reply
Highlighted
  • 3.25K
  • 135
  • 190
Forum Team
Forum Team
350 Views
Message 6 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

If you're running a Hub 3 on the connection you can find some steps to set up port forwarding here

 

Thanks, Emily.

0 Kudos
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
322 Views
Message 7 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

Alright but what does it mean by "Local Start Port" and what should i put there?

I got some info about the ports i need from the website:

TCP: 13000, 13005, 13200, 14000, 14001, 14008, 14020, 14021, 14022, 14023, 14024
UDP: 6015

0 Kudos
Reply
Highlighted
  • 2.28K
  • 167
  • 300
Superfast
312 Views
Message 8 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

Here's an example (For port forwarding to work you also have to assign a static IP to you device under 'Advanced Settings/DHCP/Reserved IP addresses):

0 Kudos
Reply
Highlighted
  • 11
  • 0
  • 0
Joining in
283 Views
Message 9 of 13
Flag for a moderator

Re: Rainbow 6 Siege connection Issues

I still haven't set the rules up, I don't know what to put in the fields that ask for port ranges. I've searched on google but i don't get it. It says to set all of the port fields to 80. Is that what i actually need to do in this situation? I don't want to mess up the router.

Xornedge_1-1596966355189.png

 

 

0 Kudos
Reply
Highlighted
  • 2.28K
  • 167
  • 300
Superfast
274 Views
Message 10 of 13
Flag for a moderator
Helpful Answer

Re: Rainbow 6 Siege connection Issues

So you've given your device a static IP?

When creating the rule just type the same port number four times.

So you will have one rule for each port.

For protocol just match what's been defined in you previous post.

You can always remove the rules if the don't work.