Serious connectivity issues - need serious help from knowledgable networking people!!!!!!!!!

[illusion]

That was a hell of an edit George

As I understand it - and I've been out of the industry for six years now so I well may be wrong - no. NAT Firewall cares only about the TCP/UDP ports, if there is a pinhole for the traffic or if there has been a recent request from the network internally.

Maybe if you have no firewall at all you could use port 80 to access the routers web interface directly - but as I understood it that routers kept external and internal traffic segregated so that you'd need some sort of PC intrusion first.

Right, you would need to already be on the network to packetsniff for the router, or to connect to the local default router IP. So you could do it, but probably not remotely, at least at the hardware level..

 

[BigDGeorge]

Let's change gears for a minute. The OP issue was not being able to establish a connection to UOF after installing a new router. He then disabled the router firewall which allowed connection to UOF. I was going to walk him through port forwarding with the firewall re-enabled, but he said he was able to connect to UOF after re-enabling the firewall and before doing the port forward edit.

Why would this have occurred?

I'm under the impression most home routers have very strict inbound filters by default, but more loose outbound restrictions. When he would launch UOF shouldn't the connection to UOF occurred and been established for both inbound and outbound connection to UOF, because the source originated from inside his network? Or was his routers outbound settings too strict to even allow it to reach to begin with?

 

[illusion]

Let's change gears for a minute. The OP issue was not being able to establish a connection to UOF after installing a new router. He then disabled the router firewall which allowed connection to UOF. I was going to walk him through port forwarding with the firewall re-enabled, but he said he was able to connect to UOF after re-enabling the firewall and before doing the port forward edit.

Why would this have occurred?

I'm under the impression most home routers have very strict inbound filters by default, but more loose outbound restrictions. When he would launch UOF shouldn't the connection to UOF occurred and been established for both inbound and outbound connection to UOF, because the source originated from inside his network? Or was his routers outbound settings too strict to even allow it to reach to begin with?

It's possible by default whatever his router brand was only had the common ones open (80, 443, 21, 22, etc). This UO server being ran on a somewhat odd port of ****. The disable/re-enable could've cleared any defaulted restrictions out of the box. That's just a guess though.