Jump to content

Unable to connect to Los Angeles servers


Moofda
 Share

Recommended Posts

Hello, for whatever reason I always get unable to connect to server/ host/party only in Los Angeles area servers. I can connect to Santa Clara/San Jose servers just fine and all other servers without any errors. I'm not sure of the reason, but I've verified the locations with net limiter running. With both ping assist disabled and enabled, I cannot connect to these servers. I have not denied any of them and I always hit allow in the duma interface and netlimiter when they appear before the disconnect happens. 

 

The IP ranges start with 45.etc and 140.etc in los Angeles that I'm having problems with. 

 

Here are a couple of the duma IDS that I saved to allow before they disconnect. Thanks for your help!

 

788ca77229174d52

bd95efba325c171c

788ca77229174d52
788ca77229174d52
Link to comment
Share on other sites

Hey Uncle Fraser, it's always white when it appears. The two server IDs I provided are the ones that say unable to connect to host. I'm getting an r2 soon, so I'll see if the problem persists, and I'll also use net limiter to see if it's happening on my main router without the duma as well for now. Unless you can think of anything else. Just strange that it's strictly the los Angeles servers. 

Link to comment
Share on other sites

  • Administrators

There is literally nothing else blocked on the entire map? If so that is odd because the router won't be blocking it, at least not with the Geo-Filter. If you disable filtering/switch to spectating mode so you can still see where you connect to do you ever get the LA server?

Link to comment
Share on other sites

1 hour ago, Netduma Fraser said:

There is literally nothing else blocked on the entire map? If so that is odd because the router won't be blocking it, at least not with the Geo-Filter. If you disable filtering/switch to spectating mode so you can still see where you connect to do you ever get the LA server?

Well, I can now say that with geo filter off and viewing the server in net limiter, it still refuses to connect. The last thing I can try is to remove duma and see if it fails with main router I suppose. Perhaps my connection doesn't like those servers at all, or they're having issues, who knows meow. 

Link to comment
Share on other sites

Okay, I removed Duma and hardwired back into the asus RT-AX86U Pro and it connected just fine to the LA server, and it was the first one it picked with natural matchmaking. I don't know if there's a setting in duma I'm overlooking. I'm piggy backing off the asus router and just my computer connects to the duma via lan port out from asus to netduma router. laserverreal.png.81172b1b2559800513041c49b58e63a0.pngimage.thumb.png.67eb70407d42e32135b77cbfb9eb95fd.png

Link to comment
Share on other sites

10 minutes ago, Netduma Fraser said:

Have you put the R1 in the DMZ on the Asus? If not please do so then try again

Yeah I already have it in the Asus DMZ. When I originally did that my nat still showed moderate so I had to enable upnp and port forward 3074 start and 3075 end on tcp and udp for it to register as open. I don't know if that has anything to do with a potential failure for those los Angeles servers. 

Link to comment
Share on other sites

  • Administrators
28 minutes ago, Moofda said:

Yeah I already have it in the Asus DMZ. When I originally did that my nat still showed moderate so I had to enable upnp and port forward 3074 start and 3075 end on tcp and udp for it to register as open. I don't know if that has anything to do with a potential failure for those los Angeles servers. 

Was the NAT still showing moderate with the Geo-Filter disabled? Have you double checked the IP in the DMZ is still matching the R1? If the R1 or the Asus has rebooted since you did that and you didn't set a static/reserved IP then it's possible the R1 IP has changed and the DMZ is no longer valid

Link to comment
Share on other sites

1 hour ago, Netduma Fraser said:

Was the NAT still showing moderate with the Geo-Filter disabled? Have you double checked the IP in the DMZ is still matching the R1? If the R1 or the Asus has rebooted since you did that and you didn't set a static/reserved IP then it's possible the R1 IP has changed and the DMZ is no longer valid

It does still show moderate without the port forwarding rule applied, and it's the correct address in the DMZ. I wonder if I should try disabling IPv6 on the duma. For whatever reason it doesn't work correctly anyway, but IPv6 does work when going directly to Asus. 

Link to comment
Share on other sites

Okay, had some time now to test it. Disabling IPv6 helped the NAT in the fact that I don't have to have that port forward rule applied to keep an open NAT. However, I still got failed to connect to a host with a LA server. Geofiltering was not enabled, and it showed up as a white dedicated server in observing mode. This was the server ID: db2d28f3ca7a484d I believe it was one of the 25.etc ip clusters. 

 

Link to comment
Share on other sites

  • Administrators

Glad to hear about the NAT! I can't think of any reason it would specifically block you from playing on a specific server unless there are any servers in your denied list or isn't in your radius etc. Could you let me know about any settings you've adjusted from their defaults?

Link to comment
Share on other sites

I have no idea either why the LA server clusters keep having issues when ran through the r1.  The only settings I can think of that I changed from default are disabling qos/congestion control and changing my pc to ps4 in the device manager for the geo filter. I did notice one strange thing the other day. I was testing strictly using ping assist, so i had the geo on poly mode with no areas selected and just used ping assist. When it tried to connect to that la server, it showed a yellow triangle, but a white ping assist server/ring on top of that yellow triangle layer. I do not have any servers blocked atm. 

Link to comment
Share on other sites

  • Administrators

The white circle will be because you allowed it and then the triangle will be because Ping Assist blocked it. The most likely cause is there are a lot of servers in that location that are mislocated which it's trying to connect you first, with the IDs we can check and move if needed

Link to comment
Share on other sites

7 minutes ago, Netduma Fraser said:

The white circle will be because you allowed it and then the triangle will be because Ping Assist blocked it. The most likely cause is there are a lot of servers in that location that are mislocated which it's trying to connect you first, with the IDs we can check and move if needed

Okay, yeah maybe it is mismatched then. Because ping assist should not have blocked that then, as I had the ping assist at a very liberal setting of 65 and I usually get around 30-35 ping in California servers.  Although, I'm not sure why at that point it still has the same problem with filtering off.

Link to comment
Share on other sites

On 12/27/2024 at 12:55 PM, Netduma Fraser said:

Yeah that is a conundrum as well tbh, something I will need to discuss with the team when they're back

No worries, I double checked as my setup is easy enough to go directly to the asus and it was still able to connect with just the asus. I might try going from modem direct to duma just to check if going through the asus might be causing it. I just have to pick an optimal time to test it out as my family will rage if I mess with the internet haha. Also, left you a dm. Thanks meow. 

Link to comment
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
 Share

×
×
  • Create New...