Check the energy saver preferences: computers connecting to FMP should NOT go to sleep.
Thanks Vaughan, I'll check that out.
As a follow up, it was the energy setting on the client computer as Vaughan suggested. When the computer went to sleep, it dropped the connection to FM Server. In both instances the client computers were new so the settings were original. I just needed to change them.
In case it was not clear, the FileMaker Server computer NEVER sleeps.
hi vaughan and michele,
i am new to filemaker server (just last week deployed my first solution... i didnt even know what a port was... that took a while...) and actually configured the host machine to sleep after 15min but to wake with incoming network activity and it seems to work fine... is this a bad idea (to allow sleep)?
John may need to be sleep deprived,
Yes, very bad idea. When the computer goes to sleep any connected guests will lose connection to the DB. I'm not sure if the OS even identifies a FM client request as "network activity" that would require not to wake up. But you should never allow a FM Host computer, be it FMS or FMP, to go to sleep.
thanks ch0c0halic... as far as i can tell, it does seem to wake the server when i try to access it while it was it's sleeping (i'm only on os10.6)... but i see your point about it going back to sleep while users are connected. i will disable sleep and rename the server "arjuna" in honor of the mytholigical hindu warrior who conquered sleep. thanks again!
FileMaker Server 13 on OSX Mavericks (non-server).
Just had a problem with a client losing connections and also having a terrible time logging on in the morning - getting failed logins because the connection was so slow.
It turned out to be the default settings on the energy saver! only spotted alfter tracing through the system logs.