Ports are open, but online games still won't work

Perry2611

Commendable
Mar 26, 2016
26
0
1,530
I had some issues earlier today booting up a free trial of FF14. The game wasn't able to connect to the databases, so it kept giving me an error message and booted me out. This is not the first time this has happened, as I recall having issues joining MC servers and playing multiplayer in rocket league. I did some searching and came to the conclusion that I had to forward some ports. I have done so for a while now, triple checking just to be sure, but to no avail. Not sure what part I'm missing here.

Additional information: All firewalls are offline, no programs that control the firewalls, ethernet cable.
 


I remember I tried a solution along the lines of DMZ earlier, but not sure if it's the one you're suggesting. Could you elaborate or link me a step by step tutorial?
What I did earlier was make my IPv4 the DMZ host. The IP didn't change when I restarted the modem either, so I guess it's static (?). Also, the ports I'm trying to open are on PC.
 
Alright, screw this garbage. They had no idea how to fix it, and tried to connect me to higher management line that cost's 10$ at startup and 8$ per minute, where my issue may or may not be solved.
-
I'll be ending this connection and be signing up for a new one shortly. Hopefully another provider will be more competent in forwarding ports, or at the least not block my attempts to forward ports manually.
 


I do. I attempted to forward some ports on my ps3 as well, but no luck. It had internet, but was unable to connect to psn. Making it dmz host didn't give any results either, sadly.
 
For the ones that are curious about the issue.
The company responsible for my network had purposely blocked the ports on my router. They do this if the network is experiencing a large increase in traffic. Often occurs when malware is present on the pc, but can also be for other reasons. So I didn't change provider, but it cost me a bit to call and ask them to disable it.
I guess my case is a very rare one, because I haven't seen a single thread stating that this could be the issue. Ah, well, at least it's fixed now.