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
regardless for the reason you should see if you can find such a setting in your router that keeps wifi clients apart from one another.
the other possible thing to look at is the IP you are using. within your lan/wifi you are probably assigned a RFC 1918 IP (such as 192.168.x.x or 10.x.x.x or similar) but from the internet you would connect in via your public IP given to you by your ISP. So depending on where you are (same lan or across internet) you would use a different address to connect to the server.
That is the best advice I can give from a generic network perspective. I have zero actual experience in the games protocol and settings and any quarks it may have. I also assume you know how to and have successfully done port forwarding and/or setting up a dmz on your router as you seem to have said as much.
Both systems were hardwired to the router (Att Fiber) before the server upgrade.
After the server upgrade the server remained hardwired, but I had it plugged into the 1GB port of the router, which used to be the port my main system was connected to.
Prior to upgrading the server to my wife's old i7 9700K (I know, over kill), I had also decided to try and eliminate some of the cables in my office by running my main on wifi since my MB has wifi 6.
Reconnecting my main to the hardwire 1GB port on my router and the server to one of the other ports seems to be the fix, unless there was something else I did along the way.
Regardless, it's working again and it runs WAAAAAAAAAAAAAY better than it did on the even older 7th gen i3 I had it running on before.
Lesson learned, HARDWIRE IS ALWAYS BETTER!