I apologize if this has been covered in the forums and I missed it, looked everywhere.

Using dbsrvr 4.49 C/S (running as a service)  on a win10 Pro box as a database server. Application runs on a separate workstation. Connection successful using network addresses  (application= 192.168.1.101, server= 192.168.1.230).  Same  application outside the network (ex. 47.48.49.1) will not connect. Port 12005 (TCP and UDP) forwarded to 192.168.1.230.  Tried firewall with rules allowing dbsrvr.exe all ports as well as with all firewalls off on both boxes. Port check (portchecktool.com) shows port open when service is running  and closed when service is not running as expected - making me think port is getting all the way to the executable. All folders have ‘Everyone/read&write’ permissions. Network discovery on on both boxes. Using Local System account for service logon.  Same behavior with dbsys utility.  Running out of stuff to check….

Any and all suggestions GREATLY appreciated.

On 10/12/2020 3:50 PM, Emory Geiger wrote:
> Using dbsrvr 4.49 C/S (running as a service)  on a win10 Pro box as a database server. Application runs on a separate workstation. Connection successful using network addresses  (application= 192.168.1.101, server= 192.168.1.230).  Same  application outside the network (ex. 47.48.49.1) will not connect. Port 12005 (TCP and UDP) forwarded to 192.168.1.230.  Tried firewall with rules allowing dbsrvr.exe all ports as well as with all firewalls off on both boxes. Port check (portchecktool.com) shows port open when service is running  and closed when service is not running as expected - making me think port is getting all the way to the executable. All folders have ‘Everyone/read&write’ permissions. Network discovery on on both boxes. Using Local System account for service logon.  Same behavior with dbsys utility.  Running out of stuff to check….
>
> Any and all suggestions GREATLY appreciated.

Only need 12005 TCP for but this setup in general should work fine - i
have something similar running in multiple sites with no problems.

I found the usual suspects in case like this are almost always :

1. Firewall/Anti-virus on the PC where DBSRVR is installed

2. Actual networking config on PC with dbsrvr - make sure default
gateway is the internet router

3. Internet firewall and port forwarding

Considering your app on LAN works OK i would lean to #2 or #3 but would
personally do following

1. Turn off windows 10 firewall on the system running DBSRVR (and also
Anti-virus if one is running)  - just for duration of test

2. Check IP settings of the PC with dbsrvr - things like default gateway
and/or static routes to make sure it routes back to internet direct with
no proxies etc

3. re-check 12005 is open and see if firewall does any logging for
incoming connections (if not then DBSRVR would log something as long as
it got a connection).

I personally like using telnet to check TCP connectivity (i.e. "telnet
<Public ip> 12005" should connect).

Alternatively just to use something easier to check - like simple HTTP
server on same PC on 8080 serving a simple html file and duplicate the
port forwarding for this port just to have a a simple way to check this
with browser.

Raul

Thanks very much, Raul. It turned out to be the anti-virus as you suspected.