1 of 1 people found this helpful
from a console you could try
telnet http://localhost 16001
If you get an empty console this indicates that something works at that port (ctrl+] (closing square bracket) to escape from that)
or you try:
netstat -an | more
and see if port 16001 is listening (it should)
Do you have access to management tools? (if yes, does the filemaker service run? (If no, start it (if windows reboot your system)))
rebooting your system can't hurt, can it?
I had a similar issue after updating Java on the server - discovered that I needed the 64 bit version of Java. That fixed my issue.