Hi Mike, Have you tried mapping to the server by IP address. Example on the wireless laptop connect would be to map drive W: to \\192.168.47.100, where \\192.168.47.100 is the IP of the server. That has worked for me in the past as well. I do this connection under the admin user and password to get to the server and reconnect at login. The laptop should automatically connect to the network drive when it boots up.
Do you have a firewall appliance on the server? That may be another issue. Maybe the secure wireless connection needs time to check out the encryption key between the laptop and the firewall appliance. Since it connects when you use Windows Explorer, perhaps you can wait a minute before launching the local app. We also use a loader to check for updates on the server and then download the latest version to the local workstation. But you're right, if you can't connect to the server, nothing else matters. Al > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Mike yearwood > Sent: Monday, March 03, 2008 2:19 PM > To: profox@leafe.com > Subject: RE: drive map re-connection > > Hi Al > > The network guy set it up as static IPs. It's strange because simply > clicking on the drive in Windows explorer re-establishes the > connection. Actually that makes me wonder if any of the WSH drive and > or file interrogation APIs would work. > > We're using a loader/launcher to copy down the latest exe to the local > PC, but that doesn't work if the connection isn't up. :) > > Mike > > > Message: 5 > > Date: Mon, 3 Mar 2008 13:22:07 -0500 > > From: "Alan Lukachko" <[EMAIL PROTECTED]> > > Subject: RE: drive map re-connection > > To: [EMAIL PROTECTED] > > Message-ID: <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset="us-ascii" > > > > Don't know if you're using DHCP or static IP for the network connection, > but > > when we had problems keeping a connection to Windows Server 2003, we > > switched the workstations under Win XP Pro to static IPs. We mapped the > > network drive on the workstation to the server using the Server admin > rights > > and giving the necessary users access to the network drive. > > > > Each workstation has the VFP 9.0 app installed locally with a link to > the > > network drive. With the exception of a physical cable problem (cable > > accidentally cut), this has worked for over 3 years. When I take my > laptop > > into do maintenance, I set up a static IP and reconnect to the network. > I > > have a network drive mapped on the laptop to the client's server. I do > not > > have to log in through Windows Explorer. It works until I disconnect. I > must > > admit that the laptop is not connected for more than a couple of hours. > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
