>Seems that the problem was "Allow the computer to turn off this device to save power" was enabled on the network interface. Since I disabled that, the machines have been running fine.
Glad you got that sorted - and that it was relatively easy!
>Regarding the DHCP issue, a couple years ago I had problems with FPW 2.6 clients losing connectivity to a DBF residing on a Windows 2003 network share, and after much head scratching figured out the connection was lost when the DHCP lease from a garden variety Linksys router expired. ... so with that lesson learned I use only static IPs now ...
Actually, what you ran into was a known problem with a number of Linksys router firmware versions, that were not implementing DHCP properly. That problem was fixed by later Linksys firmware(s). A number of modern routers support free 3rd-party firmware such as dd-WRT and Tomato - I've found the former to be excellent.
Alternately, if you have an MS server on your network, you can disable the router's DHCP server and use MS's instead.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
