I cannot get FileMaker server to listen on port 2399. There are no firewalls and no other service is using this port.
how do you determine that it is not listening? Are you using netstat?
Hi, Yes I used netstat. But we know FMS is not listening as we cannot establish an ODBC connection. I rang FileMaker Support last week and they suggested that posting here was the best way to get an answer?
I'm slightly confused that you say there is no firewall in place, are you talking about an external firewall, as it would be very unusual to run Windows 2012/2016 without the standard firewall installed as standard, which will need an inbound entry for port 2399.
I would also test port 2399 using Telnet to see if you can get a connection, it should show something similar to the attached with your server name and IP address displayed. Not being able to establish an ODBC connection isn't necessarily proof that the server isn't listening.
If you're testing from High Sierra, where Apple has handily removed both Telnet and FTP from Terminal, Telnet can be reenabled by following the advice here: https://medium.com/@maepyong/regain-telnet-ftp-command-on-terminal-in-macos-high-sierra-3a95b2af6d45 or alternatively use an app, same goes for Windows.
henryking wrote: Hi, Yes I used netstat. But we know FMS is not listening as we cannot establish an ODBC connection
Hi, Yes I used netstat. But we know FMS is not listening as we cannot establish an ODBC connection
There could be different reasons why the connection cannot be established so it's good to start with the basics. On your server, using Task Manager, Details tab. Do you see the FMS xDBC process:
The listener is running. We don't have any firewalls turned on as this server is purely internal.
For your information we are trying to set up an ODBC connection from a python script to bulk update a database.
I'm assuming that the 'test connection' in the system DSN setup is not working?
You mentioned that you used netstat. What netstat options did you use? You are not seeing that the FMS box is listening on that port?
Does the machine you are trying this from have any outgoing connection issues (like outgoing firewall)
Henry, I believe in some cases turning off the firewall is an unsupported configuration for Windows Server, how have you disabled this, Server Manager, netsh or PowerShell?
I take it that the remaining ports 5003 etc. are all working with this configuration? Have you tested with Telnet yet?
Sorry for the later reply, here is a screenshot of the telnet output on the server:
port 2399 is refused where 5003 can connect. I have tried this on another server I have and telnet can connect to both ports.
One thing to mention is on the server where I can connect the odbclistener exe is using 0% cpu whereas on the server I can't connect to it is always using at least 14% so im thinking maybe it could be an install issue.
The firewall setting are the same on each server and they are on the same network.
If you can shed any light on this that would be great.
While you can connect from the same server but can't from remote, it looks firewall (on the server) issue.
The firewall setting are the same on each server
Do you mean it is not OFF?
Recheck there is rule to allow 2399.
I don't have experience on server2016, are there any changes on firewall? Quick searching It looks no information in
Configure the Windows Firewall to Allow SQL Server Access | Microsoft Docs
But fire wall document applies only to 2008R2 and 2012
Add or Edit Firewall Rule
There are too many things to learn for me...
Thanks for replying, I have tried to connect to the port via powershell from the server it is on and it cannot connect.
So it looks like it might be a filemaker problem?
I don't think you every replied whether netstat confirms that the port is open and in listening mode. Can you confirm that?
Retrieving data ...