Thank you for your post.
If you have never installed FileMaker Server on that machine, and another instance of FileMaker is also not installed and running on that machine, then something is blocking port 5003.
A caller to our Technical Support department in March reported a similar issue, and it turned out Cisco AnyConnect was also using port 5003. Once that was uninstalled, FileMaker Pro would launch successfully and Network Sharing could be used.
Wow, TSGal… you are awesome! You are correct!! This did the trick!!
I ALSO had Cisco AnyConnect installed on my machine, and that was apparently blocking FileMaker. As soon as I uninstalled the Cisco AnyConnect software, FileMaker started working normally again!!
A few additional questions about this issue:
1. Since this is a known issue that could be affecting others as well, do you think that you could create a FileMaker KnowledgeBase Article about this situation? I was trying to figure this situation out for months before posting on the forum and got this answer from you.
2. I wonder if there is any way to run BOTH Cisco AnyConnect AND FileMaker on my machine, if I'm interested in peer-to-peer FileMaker sharing?? I rarely do peer-to-peer FileMaker sharing on my machine, but it would be nice to have the ability to have both apps on my machine.
3. Why is Cisco AnyConnect blocking port 5003? Isn't that officially reserved by the IANA (Internet Assigned Numbers Authority) for FileMaker's exclusive use only?
4. Do you know how the caller figured out that Cisco AnyConnect was blocking port 5003? Do you know what piece of software he used to figure out which software was blocking which ports? I've been downloading all sorts of software for months, trying to figure out which software was blocking port 5003, and I couldn't find any tools that gave me my definitive answer. I even ran specialized Terminal commands that I found on the Internet, and the never told me that Cisco AnyConnect was the problem. Would be really great to figure out how to troubleshoot port problems like this in the future.
1. I have made a request for a Knowledge Base Article.
I also located another user on the forum who ran into a similar issue back in June, 2010 with FileMaker Pro 11:
2. I'm not familiar with Cisco AnyConnect to know if FileMaker Pro and Cisco AnyConnect can co-exist.
3. Port 5003 is NOT reserved by FileMaker, Inc. Only port 591 has been registered.
4. The Support Technician had the customer open Terminal and run the command:
sudo lsof -n -P -i :5003
This revealed which PID was listening on port 5003. Then, checked Activity Monitor to see if a process corresponded to PID 152. This returned "acwebsecagent", and the parent process and Process Group is "vpnagentd (100)". The customer had an older version of the software "Cisco AnyConnect VPN Client", but since the VPN wasn't working in Mavericks, it was replaced with "Cisco AnyConnect Secure Mobility Client".
The customer then ran the command:
... which removed the problem blocking FileMaker Sharing over port 5003, and it did not break the VPN functionality.
I'm going to also document this in the KBL. I am assuming that this same issue could occur on windows systems.
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
Thanks, TS Gal!!
This is fantastic!! Thanks so much, TSGal! :)
I just installed the preview version of OneDrive for Business on the mac and was getting this same message. Uninstalled it and the message went away. I guess OneDrive for Business is using 5003...
I am just exactly running onto this one...
So my question is following : If my customer install a brand new dedicated machine to host the FileMaker databases, will FileMaker Pro on other machines be able to connect to this host, even if their Cisco Anyconnect is left in its actual state ?
Thank you so much for your help which is much appreciated.
Oh and just to be sure : i guess there is actually no way to change the FMP internal port from 5003 to another ?
OK, problem solved, thanks to your (technician's) tip above, TSGal.
Even if the IT guy here said it will not be possible to change it without break the VPN functionality, i nevertheless tested this solution with the less critical computer and it worked : after terminalized the command and restarting computer (just to be sure), FileMaker Pro 13 was able to share files AND Cisco AnyConnect Secure Mobility Client was able to establish connection.
Thus, my new customer is able to use his new timesheet and accounting FileMaker Pro solution and, ending the past accounting year with the old hosted solution which use this VPN.
She send you her greetings and thanks !!!