Windows mapping doesn't connect until the first time its Accessed.. rather
than using mapping in the computer, update the registry startup command with
a Subst command.
subst P: \\machine\share
On Mon, Apr 4, 2011 at 9:13 AM, Rohit Gupta wrote:
> I think it just takes a while. Have you tried
what about using the UNC path instead of the mapped drive letter? There may
be some security issues to deal with, but it wont require the mapped drive
to be "mapped" before it can use it as is teh case now.
Jeremy
On Mon, Apr 4, 2011 at 9:50 AM, John Bird wrote:
> When you map the drive tick
When you map the drive tick the optiion to “Restore mapping on logon”. That
way if a user loses the mapping you can just tell them to log out and logon
again to fix it. As long as the network connection is there when the PC
starts that normally works fine. If it doesn’t can be because a pa
I think it just takes a while. Have you tried making the share/map
persistent on the the workstation.
On 3/04/2011 4:53 p.m., Marshland Engineering wrote:
I'm mapping my data to a P: drive across a windows XP
network. Whenever I start one of my networked PC's and I open my app
for the first t
