Hello, my software vendor needs to connect to port 1583 to access a specific database. They are hosting a website to put the information online and are having trouble getting connected. I have the path set up on the firewall to allow their specific IP address to my internal server and am port forwarding 1583 but the vendor is getting a "connection timed out" when they try to connect. I noticed when I monitored the server ports it seems like the port is listening.  Any help would be appreciated.

Here is the text from the netstat /an I ran on the server:

C:\WINDOWS>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:53             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1029           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1045           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1047           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1494           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1583           0.0.0.0:0              LISTENING
 

No problems in my testing environment

I've changed the firewall to REJECT everything both sides and added a DNAT rule for port 1583 (which includes an ACCEPT rule for accessing that port on the firewall). Database access works just fine.

One note though: you cannot add a client DSN this way (on Windows anyway). It seems that several of the dialogs in de DSN setup wizard depend on transactional access. What I did was add a dummy DSN and then change the registry entries to the correct named database and the firewalls "external" IP.