Jump to content

empty servers no players


Recommended Posts

First off, sounds like heaven. You should be happy about it.

Solution: While in-game in your empty lobby, type netstat -a -b into your command prompt and wait for Rockstar's UDP ports to pop up or use Resource Monitor on Windows 10 to confirm that Rockstar is indeed attempting to listen with port 6672. If you cannot see the port or it says "Not allowed, unrestricted access" (or something like that), then something on your computer is blocking their port that is required for matchmaking.

Go into windows firewall and create a new rule that allows listening for port 6672. You can just disable all of Windows Firewall temporarily to see if that is the problem. Check your router too, go into the admin panel and make sure that port 6672 is capable of listening and is allowed. Another idea here is just that your Internet is so bad that Rockstar feels like you cannot maintain connection to other players, in that case, they will intentionally put you in a solo lobby to solve the issue.

You can call your router's company and ask for support on this or check your router's manual online, they can likely point you to creating a new rule on your router to let Rockstar's ports through. If your router is owned by your ISP (such as a rented router), your ISP should be able to assist you on ports being unintentionally blocked.

Edited by poopypoopypoop
  • Like 2
Link to post
Share on other sites
4 hours ago, poopypoopypoop said:

First off, sounds like heaven. You should be happy about it.

If you want to play solo, sure. I know you are meaning this toward those who use mods though. It has been a growing issue.

Link to post
Share on other sites

I will post what i read in the command prompt, maybe you can help me understand what's wrong.

 

  Proto  Indirizzo locale       Indirizzo esterno       Stato
  TCP    0.0.0.0:135            DESKTOP-GH7FT3D:0      LISTENING
  RpcSs
 [svchost.exe]
  TCP    0.0.0.0:445            DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    0.0.0.0:5040           DESKTOP-GH7FT3D:0      LISTENING
  CDPSvc
 [svchost.exe]
  TCP    0.0.0.0:5432           DESKTOP-GH7FT3D:0      LISTENING
 [postgres.exe]
  TCP    0.0.0.0:7680           DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    0.0.0.0:49664          DESKTOP-GH7FT3D:0      LISTENING
 [lsass.exe]
  TCP    0.0.0.0:49665          DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    0.0.0.0:49666          DESKTOP-GH7FT3D:0      LISTENING
  Schedule
 [svchost.exe]
  TCP    0.0.0.0:49667          DESKTOP-GH7FT3D:0      LISTENING
  EventLog
 [svchost.exe]
  TCP    0.0.0.0:49668          DESKTOP-GH7FT3D:0      LISTENING
 [spoolsv.exe]
  TCP    0.0.0.0:49669          DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    0.0.0.0:54365          DESKTOP-GH7FT3D:0      LISTENING
  PolicyAgent
 [svchost.exe]
  TCP    127.0.0.1:15292        DESKTOP-GH7FT3D:0      LISTENING
 [Adobe Desktop Service.exe]
  TCP    127.0.0.1:51837        lmlicenses:65001       ESTABLISHED
 [nvcontainer.exe]
  TCP    127.0.0.1:51840        DESKTOP-GH7FT3D:0      LISTENING
 [NVIDIA Web Helper.exe]
  TCP    127.0.0.1:65001        DESKTOP-GH7FT3D:0      LISTENING
 [nvcontainer.exe]
  TCP    127.0.0.1:65001        lmlicenses:51837       ESTABLISHED
 [nvcontainer.exe]
  TCP    192.168.1.9:139        DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    192.168.1.9:51879      104.18.24.243:http     CLOSE_WAIT
 [SkypeApp.exe]
  TCP    192.168.1.9:52044      mil04s04-in-f10:https  CLOSE_WAIT
 [googledrivesync.exe]
  TCP    192.168.1.9:52054      a104-102-30-92:https   CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52055      a104-102-30-92:https   CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52056      a104-102-30-92:https   CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52060      mil04s04-in-f10:https  CLOSE_WAIT
 [googledrivesync.exe]
  TCP    192.168.1.9:52085      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52086      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52087      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52088      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52089      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52091      a2-19-192-43:https     CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52112      a2-22-33-204:http      CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:52116      a104-102-29-249:http   CLOSE_WAIT
 [WinStore.App.exe]
  TCP    192.168.1.9:54515      40.67.254.36:https     ESTABLISHED
  WpnService
 [svchost.exe]
  TCP    192.168.1.9:54554      mil04s04-in-f10:https  ESTABLISHED
 [googledrivesync.exe]
  TCP    192.168.1.9:54556      mil04s25-in-f74:https  CLOSE_WAIT
 [googledrivesync.exe]
  TCP    192.168.1.9:54627      40.67.254.36:https     ESTABLISHED
 [OneDrive.exe]
  TCP    192.168.1.9:54910      localhost:7678         ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:54914      wq-in-f188:5228        ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:54933      a2-22-32-10:https      CLOSE_WAIT
 [Video.UI.exe]
  TCP    192.168.1.9:54979      209-50-61-119:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55466      vodafone:http          ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55481      104.17.64.4:https      TIME_WAIT
  TCP    192.168.1.9:55485      104.17.64.4:https      TIME_WAIT
  TCP    192.168.1.9:55492      104.16.51.111:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55503      104.18.74.113:https    TIME_WAIT
  TCP    192.168.1.9:55550      a2-22-32-252:https     ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55557      a104-102-28-159:https  ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55561      199:https              ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55569      a104-83-144-28:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55587      104.244.42.195:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55638      104.27.173.17:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55640      vodafone:http          ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55671      185.63.144.5:https     TIME_WAIT
  TCP    192.168.1.9:55677      server-13-226-162-76:https  ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55684      69.173.144.165:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55685      151.101.242.2:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55686      185.64.189.110:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55693      147:https              ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55696      85.159.234.28:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55699      prebid:https           ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55702      a104-102-29-65:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55703      a2-22-33-114:https     ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55705      178.250.2.152:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55706      185.64.189.112:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55708      ec2-52-59-161-228:https  ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55709      104.16.190.66:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55710      151.101.13.194:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55711      ec2-3-123-66-234:https  ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55716      a23-77-213-228:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55745      80.252.91.53:https     TIME_WAIT
  TCP    192.168.1.9:55746      vodafone:http          ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55748      13.64.117.133:https    TIME_WAIT
  TCP    192.168.1.9:55749      mil07s08-in-f14:https  TIME_WAIT
  TCP    192.168.1.9:55750      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55751      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55752      104.255.106.49:https   TIME_WAIT
  TCP    192.168.1.9:55753      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55754      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55760      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55761      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55762      104.255.106.49:https   TIME_WAIT
  TCP    192.168.1.9:55763      https-95-140-230-157:https  TIME_WAIT
  TCP    192.168.1.9:55764      104.255.106.56:https   TIME_WAIT
  TCP    192.168.1.9:55766      104.255.106.56:https   TIME_WAIT
  TCP    192.168.1.9:55767      185.56.66.49:https     ESTABLISHED
 [RDR2.exe]
  TCP    192.168.1.9:55770      ec2-52-57-98-188:https  TIME_WAIT
  TCP    192.168.1.9:55772      ec2-3-120-19-19:https  TIME_WAIT
  TCP    192.168.1.9:55774      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55775      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55776      104.255.106.56:https   TIME_WAIT
  TCP    192.168.1.9:55777      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55778      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55779      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55780      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55781      104.255.106.56:https   TIME_WAIT
  TCP    192.168.1.9:55785      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55786      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55787      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55788      104.255.106.56:https   TIME_WAIT
  TCP    192.168.1.9:55789      185.56.66.33:30217     ESTABLISHED
 [RDR2.exe]
  TCP    192.168.1.9:55790      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55791      192.81.241.100:https   TIME_WAIT
  TCP    192.168.1.9:55795      https-95-140-230-157:https  TIME_WAIT
  TCP    192.168.1.9:55801      vodafone:http          ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55802      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55806      80.252.91.52:https     TIME_WAIT
  TCP    192.168.1.9:55807      104.255.106.49:https   TIME_WAIT
  TCP    192.168.1.9:55808      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55809      ec2-34-215-169-116:https  TIME_WAIT
  TCP    192.168.1.9:55810      104.255.106.49:https   TIME_WAIT
  TCP    192.168.1.9:55811      104.255.106.52:https   TIME_WAIT
  TCP    192.168.1.9:55812      a104-104-54-161:https  FIN_WAIT_2
 [RDR2.exe]
  TCP    192.168.1.9:55816      69.173.144.141:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55817      69.173.144.141:https   ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55818      72.251.249.13:https    TIME_WAIT
  TCP    192.168.1.9:55822      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55823      104.255.106.53:https   TIME_WAIT
  TCP    192.168.1.9:55824      a-0001:https           ESTABLISHED
 [SearchUI.exe]
  TCP    192.168.1.9:55825      72.251.249.13:https    ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55827      536:https              ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55829      13.107.246.10:https    ESTABLISHED
 [SearchUI.exe]
  TCP    192.168.1.9:55830      204.79.197.254:https   ESTABLISHED
 [SearchUI.exe]
  TCP    192.168.1.9:55831      131.253.33.254:https   ESTABLISHED
 [SearchUI.exe]
  TCP    192.168.1.9:55832      204.79.197.222:https   ESTABLISHED
 [SearchUI.exe]
  TCP    192.168.1.9:55833      80.252.91.52:https     ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55834      538:https              ESTABLISHED
 [chrome.exe]
  TCP    192.168.1.9:55835      80.252.91.52:https     ESTABLISHED
 [chrome.exe]
  TCP    [::]:135               DESKTOP-GH7FT3D:0      LISTENING
  RpcSs
 [svchost.exe]
  TCP    [::]:445               DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    [::]:5432              DESKTOP-GH7FT3D:0      LISTENING
 [postgres.exe]
  TCP    [::]:7680              DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    [::]:49664             DESKTOP-GH7FT3D:0      LISTENING
 [lsass.exe]
  TCP    [::]:49665             DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    [::]:49666             DESKTOP-GH7FT3D:0      LISTENING
  Schedule
 [svchost.exe]
  TCP    [::]:49667             DESKTOP-GH7FT3D:0      LISTENING
  EventLog
 [svchost.exe]
  TCP    [::]:49668             DESKTOP-GH7FT3D:0      LISTENING
 [spoolsv.exe]
  TCP    [::]:49669             DESKTOP-GH7FT3D:0      LISTENING
 Impossibile ottenere informazioni sulla proprietà
  TCP    [::]:54365             DESKTOP-GH7FT3D:0      LISTENING
  PolicyAgent
 [svchost.exe]
  UDP    0.0.0.0:500            *:*
  IKEEXT
 [svchost.exe]
  UDP    0.0.0.0:4500           *:*
  IKEEXT
 [svchost.exe]
  UDP    0.0.0.0:5050           *:*
  CDPSvc
 [svchost.exe]
  UDP    0.0.0.0:5353           *:*
 [chrome.exe]
  UDP    0.0.0.0:5353           *:*
 [chrome.exe]
  UDP    0.0.0.0:5353           *:*
 [chrome.exe]
  UDP    0.0.0.0:5353           *:*
 [chrome.exe]
  UDP    0.0.0.0:5353           *:*
  Dnscache
 [svchost.exe]
  UDP    0.0.0.0:5355           *:*
  Dnscache
 [svchost.exe]
  UDP    0.0.0.0:6672           *:*
 [RDR2.exe]
  UDP    0.0.0.0:49446          *:*
 [Launcher.exe]
  UDP    0.0.0.0:54446          *:*
 [chrome.exe]
  UDP    0.0.0.0:55612          *:*
 [RDR2.exe]
  UDP    0.0.0.0:57549          *:*
 [chrome.exe]
  UDP    0.0.0.0:58088          *:*
 [chrome.exe]
  UDP    0.0.0.0:58504          *:*
 [chrome.exe]
  UDP    0.0.0.0:61470          *:*
 [SkypeApp.exe]
  UDP    0.0.0.0:62758          *:*
 [Launcher.exe]
  UDP    0.0.0.0:63443          *:*
 [nvcontainer.exe]
  UDP    0.0.0.0:63646          *:*
 Impossibile ottenere informazioni sulla proprietà
  UDP    127.0.0.1:1900         *:*
  SSDPSRV
 [svchost.exe]
  UDP    127.0.0.1:10070        *:*
 [NVIDIA Web Helper.exe]
  UDP    127.0.0.1:49664        *:*
  iphlpsvc
 [svchost.exe]
  UDP    127.0.0.1:50537        *:*
 [nvcontainer.exe]
  UDP    127.0.0.1:63634        *:*
  SSDPSRV
 [svchost.exe]
  UDP    192.168.1.9:137        *:*
 Impossibile ottenere informazioni sulla proprietà
  UDP    192.168.1.9:138        *:*
 Impossibile ottenere informazioni sulla proprietà
  UDP    192.168.1.9:1900       *:*
  SSDPSRV
 [svchost.exe]
  UDP    192.168.1.9:5353       *:*
 [nvcontainer.exe]
  UDP    192.168.1.9:63633      *:*
  SSDPSRV
 [svchost.exe]
  UDP    [::]:500               *:*
  IKEEXT
 [svchost.exe]
  UDP    [::]:4500              *:*
  IKEEXT
 [svchost.exe]
  UDP    [::]:5353              *:*
 [chrome.exe]
  UDP    [::]:5353              *:*
 [chrome.exe]
  UDP    [::]:5353              *:*
  Dnscache
 [svchost.exe]
  UDP    [::]:5355              *:*
  Dnscache
 [svchost.exe]
  UDP    [::]:61470             *:*
 [SkypeApp.exe]
  UDP    [::]:63444             *:*
 [nvcontainer.exe]
  UDP    [::1]:1900             *:*
  SSDPSRV
 [svchost.exe]
  UDP    [::1]:5353             *:*
 [nvcontainer.exe]
  UDP    [::1]:49665            *:*
 [postgres.exe]
  UDP    [::1]:63632            *:*
  SSDPSRV
 [svchost.exe]
  UDP    [fe80::51b1:da5b:bbc7:eeae%9]:1900  *:*
  SSDPSRV
 [svchost.exe]
  UDP    [fe80::51b1:da5b:bbc7:eeae%9]:63631  *:*
  SSDPSRV
 [svchost.exe]

Link to post
Share on other sites

 UDP    0.0.0.0:6672           *:*
 [RDR2.exe]

This is the port that should be working for you to have matchmaking work. I would check it in the "Resource Monitor" for windows 10 and tell me if it says "Not Allowed, not restricted" on port 6672. It should say "allowed, not restricted" if it's working as intended. If not, you need to fix it on your own router or firewall. If it is working, I think there's something going on with your Internet that is making people get dropped for your lobbies and I would ask your ISP what is wrong. Just check router first because this is the most common cause of blocked ports.

Link to post
Share on other sites

I would add that when I first logged on after boycotting the spring updates I was not aware of other players being in defensive.  I spent a few days just thinking I never saw anyone.. but then I started seeing payers who were not visible on the map... I was slow on uptake.

I suppose I'm asking if the person who is not seeing any players is aware of defensive mode... or is he looking at the player list that shows with our dailies.

I mean a person who played a year ago logging n would think the server empty... because when i was a level 1 we could see every player on the map... not so much now.

Link to post
Share on other sites
47 minutes ago, Darconios said:

I would add that when I first logged on after boycotting the spring updates I was not aware of other players being in defensive.  I spent a few days just thinking I never saw anyone.. but then I started seeing payers who were not visible on the map... I was slow on uptake.

I suppose I'm asking if the person who is not seeing any players is aware of defensive mode... or is he looking at the player list that shows with our dailies.

I mean a person who played a year ago logging n would think the server empty... because when i was a level 1 we could see every player on the map... not so much now.

Unless I'm misunderstanding something, players in Defensive Mode should still show up on the player list in sessions.  They will also show up on the radar as faded blips but they are still visible.   

 

  • Like 1
Link to post
Share on other sites
14 hours ago, poopypoopypoop said:

 UDP    0.0.0.0:6672           *:*
 [RDR2.exe]

This is the port that should be working for you to have matchmaking work. I would check it in the "Resource Monitor" for windows 10 and tell me if it says "Not Allowed, not restricted" on port 6672. It should say "allowed, not restricted" if it's working as intended. If not, you need to fix it on your own router or firewall. If it is working, I think there's something going on with your Internet that is making people get dropped for your lobbies and I would ask your ISP what is wrong. Just check router first because this is the most common cause of blocked ports.

thanks again for your help

 

i entered the router and created an access for the listed port, still when i take a look to the resource monitor i can't find no program using that port.  red dead 2 is said to be using port 11340.

 

i really don't get it. one month ago everything was working. My connection is good, i don't think that's the problem

Link to post
Share on other sites
4 minutes ago, vinbaker42 said:

thanks again for your help

 

i entered the router and created an access for the listed port, still when i take a look to the resource monitor i can't find no program using that port.  red dead 2 is said to be using port 11340.

 

i really don't get it. one month ago everything was working. My connection is good, i don't think that's the problem

If it was working at one point, maybe clearing your cache could help. Go into documents and delete the whole "Rockstar Games" folder which has all of your local files in it. I'm curious how you've been living with this issue for one month btw, have you asked Rockstar? They probably could have offered troubleshooting advice to you.

Link to post
Share on other sites

i was not playing online, that's why i didn't notice for a all month. I will write to them now. 

 

10 hours ago, poopypoopypoop said:

If it was working at one point, maybe clearing your cache could help. Go into documents and delete the whole "Rockstar Games" folder which has all of your local files in it. I'm curious how you've been living with this issue for one month btw, have you asked Rockstar? They probably could have offered troubleshooting advice to you.

what cache are you talking about exactly? If i delete the complete folder, i will lose my game saves

Link to post
Share on other sites
2 hours ago, vinbaker42 said:

i was not playing online, that's why i didn't notice for a all month. I will write to them now. 

 

what cache are you talking about exactly? If i delete the complete folder, i will lose my game saves

Sorry, I didn't realize you had a single-player save and just assumed you were on RDO which is all saved on their servers. Instead, open your Rockstar launcher, go to settings, click Red Dead then click "delete local profiles". Rockstar does backup your saves on the cloud if you have it on and I would keep them there too because sometimes it is absolutely necessary to clear these local files. They get messed up a lot, would suck to accidentally delete a single-player save. You could manually backup the save then put it back, it's in C:\Users\\Documents\Rockstar Games\Red Dead Redemption 2\Profiles.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

LATEST RDR2 NEWS CLIPS

×
×
  • Create New...