DCS Client can not see local server in Google Fiber DMZ behind FW \ VM Network

[Shazzer]

I am stumped by an issue of why a client can not see a server in the server browser. Now before I get the (Put the google fiber modem into bridge mode etc. etc.), This is not an option due to Google TV box on the network. Also, We have multiple servers and Google Fiber only allows one DMZ Client

The person\DCS Client can put in the IP\port and can log in with no issues. Everyone else in the world can see the servers.....Works perfect... If I shutdown PFSense and move a single server to the DMZ IP. The server shows up in the server browser list.....

I have tried opening every TCP\UDP port to the 192. Network, 1:1 NAT, Multicast etc..... How does DCS Client look for servers? There has to be something I am missing

 

Edited November 24, 2021 by Shazzer
correction

[zildac]

I am stumped by an issue of why a client can not see a server in the server browser. Now before I get the (Put the google fiber modem into bridge mode etc. etc.), This is not an option due to Google TV box on the network. Also, We have multiple servers and Google Fiber only allows one DMZ Client

The person\DCS Client can put in the IP\port and can log in with no issues. Everyone else in the world can see the servers.....Works perfect... If I shutdown PFSense and move a single server to the DMZ IP. The server shows up in the server browser list.....

I have tried opening every TCP\UDP port to the 192. Network, 1:1 NAT, Multicast etc..... How does DCS Client look for servers? There has to be something I am missing

 

Does the local client when working see the internal ip of the server or the Natted public?

[Shazzer]

When I can get it to show up - 192.168.1.180:random-port. That is the "Outbound" NAT source port of the vm coming out of PFSense. Trying to connect to it fails (As expected).

The client IP is 192.168.1.253...Technically anything on the 192 network would only pass thru the first NAT from inside VM network 10.0.0.X to the 192.168.1.180. I would expect to see on that client the 192.168.1.180:103XX. That is what I am hung up on.....