General information
Category:
Coding, syntax & commands
Environment versions
Network:
Windows 2003 Server
>>I have a VFP8 app (which I can recompile for VFP9 if necessary) running on 4 Windows XP Pro SP2 PC's. All PC's are opening a DBF on the Windows 2003 server via a mapped drive Z: network share. To eliminate any DHCP lease timeout issues, all PC's (and server) are assigned static IP addresses (10.0.0.x) on the LAN. The 2 PC's connected right next to the Windows 2003 Server on the same switch never get an error. However, the 2 PC's that are in distant parts of the building connected via a VLAN get a mapped drive Z: does not exist error every so often. I tried changing the autodisconnect registry key on those PC's thinking it was the 15 minute autodisconnect "feature", but this had no effect. When I look in My Computer, drive Z: is there, with no red X on it. If I click on drive Z:, it takes perhaps 5 seconds to pull up the folders on the server, and all is well again. If there was a way to lengthen the timeout of my USE statement, to perhaps 10 seconds, I think this error would go away. Seems like VFP gives up a little too quickly.
>>
>>I've tried running a ping -t 10.0.0.10 in a minimized DOS box to keep the TCP connection alive to the server, but this has no effect.
>>
>>I've tried running a minimized VFP app that does a DIR Z:\ every 30 seconds to keep alive, but this has no effect.
>
>You should set the autodisconnect to -1 on the server not on the PC. The server is the gay who disconnects users :-)
>And to answer your question: no you can't do that (AFAIK) but you could write your own routine to open files.
That's a controversial thing to say about a server.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only