Daniel,
I would first like to confirm what you have said are the symptoms. You say
that if you open the Explorer you _can_ see the files in the mapped drives,
but you must do this before opening these files from inside the application,
correct? The part I do not understand is where you say that you select the
mapped driver and it goes back to the C: drive. I am not sure I understand
what is exactly happening here. Can you see the rest of the network before
opening these drives in Explorer? Is your wireless network connected
already and can you, for example, browse
www.microsoft.com without any
problems?
I am guessing that this application is somewhat older, perhaps a legacy
application. Is is a 16-bit or 32-bit application, recent or older?
When you mapped the drives, did you set them to reconnect at login?
http://www.microsoft.com/windowsxp/h...nect_drive.asp
My first idea is the following: Directly enter the full file name of the
file you want to open instead of navegating there through the Open File
dialog window. Let's say you have a F: drive, and you want to open the file
F:\documents\mydoc.doc - instead of navegating to F:, then documents, enter
the full path directly into the file name portion of the dialog. I am
interested in what happens in this case, please tell me how that goes.
The other case I am interested in checking is directly accessing these
drives w/o using Explorer. Can you initially open a CMD.EXE window and do a
dir of
F:\, following the above example? Does that cause the problem to later not
happen with the application?
I am not sure why these machines using wireless would behave differently.
There are no settings related to this at all that I know of. Please let me
know the results of the above scenarios.
--
Brian Wehrle
(E-Mail Removed)
Software Test Engineer/Wireless Networking
Microsoft Corp.
"Daniel Eichorn" <Daniel
(E-Mail Removed)> wrote in message
news:5B94D51D-2217-4B44-A11D-(E-Mail Removed)...
> This is an odd problem.
>
> I have a peer-to-peer network, with one machine running XP Pro doing
> nothing
> but file distribution, and six machines running XP Home that have mapped
> drives to folders on the XP Pro machine. The three machines that connect
> directly to my Netgear router using 100-Base T work fine. The four that
> connect via Wi-Fi all have the following problem.
>
> After startup, if I launch any application and try to access the mapped
> drives, it won't work. It can see them in the list of drives to select in
> the
> Open window, but if I try to select them it goes back to the C: drive.
> However, if I open up My Computer, open the mapped drive, close the drive
> window, and then launch the application, it can access the mapped drives
> just
> fine for the rest of the day. Once the machine is shut down and restarted,
> the problem comes back.
>
> I presume there's some setting for mapped drives that is unique to
> wireless
> connections to get them to fully load on startup, but I don't know where
> it
> might be. Can anyone help?
Similar Threads
Linear Mode
