Hi Len, Are you familiar with the command line tool, ping? One of the things you can do is ping the host from the workstation - you just need to know the IP address of the host. Type ping ipaddress and let it run for at least a few minutes, then stop it with Control-C. I pasted some sample data below. First note the summary info at the bottom, specifically the %packet loss. It should be zero. The round-trip #'s should be under 10 ms for a LAN and under 200-500 ms for a WAN. Also note the column labeled icmp_seq= these should be continuous numbers. If any are missing, that's a bad sign. The next problem will be figuring out why your ping times are slow. It could be the software firewall or other background process on the workstation or the server, or it could be a physical networking issue. HTH -- Steve Moore Cumberland, Maine S:~ steve$ ping 10.0.75.10 PING 10.0.75.10 (10.0.75.10): 56 data bytes 64 bytes from 10.0.75.10: icmp_seq=0 ttl=64 time=4.096 ms 64 bytes from 10.0.75.10: icmp_seq=1 ttl=64 time=4.044 ms 64 bytes from 10.0.75.10: icmp_seq=2 ttl=64 time=4.161 ms 64 bytes from 10.0.75.10: icmp_seq=3 ttl=64 time=3.995 ms 64 bytes from 10.0.75.10: icmp_seq=4 ttl=64 time=4.082 ms 64 bytes from 10.0.75.10: icmp_seq=5 ttl=64 time=4.210 ms 64 bytes from 10.0.75.10: icmp_seq=6 ttl=64 time=3.957 ms 64 bytes from 10.0.75.10: icmp_seq=7 ttl=64 time=4.032 ms 64 bytes from 10.0.75.10: icmp_seq=8 ttl=64 time=4.129 ms 64 bytes from 10.0.75.10: icmp_seq=9 ttl=64 time=3.955 ms 64 bytes from 10.0.75.10: icmp_seq=10 ttl=64 time=4.118 ms 64 bytes from 10.0.75.10: icmp_seq=11 ttl=64 time=3.884 ms ^C --- 10.0.75.10 ping statistics --- 12 packets transmitted, 12 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 3.884/4.055/4.210/0.091 ms On Aug 19, 2011, at 5:58 AM, Leonard Siskin, DC wrote: > I have been an amateur Filemaker user for years and run my chiropractic office on a database I built starting in FM5. > > I am using 2 computers, one opens the file using FM11 and one opens it remotely FM 10. > > The system always worked flawlessly but recently the network loses communication with the host spontaneously and I have to re-open the database from the remote location. > > I’ve checked my security software and replaced my router and all three switches the office uses but the problem still exists. > > Sometimes connectivity is lost every few minutes and after several times re-opening the database from the remote computer it will say not enough memory to open the database (I am using a core i7 processor, windows 7 professional and one of the two has 12GB ram and the other, 18GB). Sometimes I receive an error message stating the maximum number of licensed users are already using the software and it shuts filemaker down on the remote computer. (Both computers have licensed software) The only way to re-open the database on the remote computer is to shut down filemaker on both computers and reopen the database then re-open from the remote location. > > Does anyone have any idea why this is happening or how to fix it???? > > I really appreciate the input from the group as many of the conversations here have shed light on using the system better. > > I’d appreciate any feedback anyone has. > > Thanks. > > Len > > > Leonard Siskin, DC > Siskin Family Chiropractic > 326 US Highway 22 > Suite 6B > Green Brook, NJ 08812 > www.SiskinChiropractic.com > [log in to unmask] > Phone: 732-752-6606 > Fax: 732-752-6643 >