Veselko Posted January 5, 2006 Posted January 5, 2006 Hi everybody, I have established remote administration of FM Server 7, and everything works fine year and half. But, we changed internet connectivity in office ( ADSL instead of wireless ) and local IP addresses was changed. After that, I couldn't establish remote administration. When I try to connect on server via FileMaker Server Admin, it brings me message: " Could not connect to FileMaker Server “(IP)”. " Connectivity with server from all machines and to all databases works perfect, just remote administration failed. Port 5003 is open. Any suggestions how to solve problem? TIA
Wim Decorte Posted January 5, 2006 Posted January 5, 2006 You get that error after you select the server from "local servers"? Or does the server not show up there? Make sure your server is on a static IP address and try connecting to it using that IP address or the server name. Port 5003 is the data port and is not used for administration. If you're trying to do remote admin through NAT then it won't work. It's not meant to work.
Veselko Posted January 5, 2006 Author Posted January 5, 2006 You get that error after you select the server from "local servers"? After that I get error message. If you're trying to do remote admin through NAT then it won't work. It's not meant to work. Sorry, but what is NAT? Agin, remote admin worked perfect before setting up new internet connection in office. I just change IP ( to new IP of servers machine ) in window where do selection the server from "local servers"?
Wim Decorte Posted January 6, 2006 Posted January 6, 2006 Sorry, but what is NAT? Agin, remote admin worked perfect before setting up new internet connection in office. I just change IP ( to new IP of servers machine ) in window where do selection the server from "local servers"? NAT = Network Address Translation. This is done by the router that sits between the internet and your LAN. When traffic comes in on the public (internet) IP address of the router it can direct that traffic to servers in your LAN based on the port # the traffic comes in on. Also called "port forwarding". It's not clear from your post if your "remote admin" means: - admin from another machine in the LAN, or - admin from a machine through the internet (won't work unless you make a VPN connection to your LAN first) Make sure the version of the SAT tool on your remote machine matches the version of FMS.
Veselko Posted January 9, 2006 Author Posted January 9, 2006 In my case, "remote admin" means your first solution - admin from another machine in the LAN.
Wim Decorte Posted January 9, 2006 Posted January 9, 2006 Ok. Make sure the server is not running a software firewall. Also try the SAT tool from another machine and see if it fails from everyhere.
Veselko Posted January 12, 2006 Author Posted January 12, 2006 Ok. Make sure the server is not running a software firewall. Also try the SAT tool from another machine and see if it fails from everyhere. I have checked, and Server machine is not running some software firewall. Also, I try SAT from 2 another machines; one with earlier installing SAT, and one with first time established (for this test only) SAT, and same thing happens, with same message: “Could not connect to FileMaker Server “(IP)”.”
Wim Decorte Posted January 12, 2006 Posted January 12, 2006 One thing you haven't answered yet: you're sure the version of SAT is the same as the version revision of FMS on the server? SAT installed from the CD won't work if you already updated FMS to 8v2 (or 7v4)
Veselko Posted January 13, 2006 Author Posted January 13, 2006 One thing you haven't answered yet: you're sure the version of SAT is the same as the version revision of FMS on the server? SAT installed from the CD won't work if you already updated FMS to 8v2 (or 7v4) Both of them are from CD (7.0v1), without updating.
Veselko Posted May 15, 2006 Author Posted May 15, 2006 Hallo everybody! After few monhts without Remote Administration, I start from beginning with establishing Remote Administration, and quickly find an answer for my problem. Exceptions for machines with Remote Administration in Windows FireWall under Port 50006 wasn't correct. They was for old IP; after changing connectivity in offce to ADSL, IP for another machines was changed too, not only for server. Cheers!!!
Recommended Posts
This topic is 6766 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now