RE: VPN & Mapped Network drives

You do not specify what command you are running but I suspect you are using a
"net use" command.
Try creating a *.bat file that includes the following line preceding the net
use drive command.
net use [device] /delete
The "/delete" command will eliminate the device in use error.

"Wim" wrote:

> Hi,
>
> I am having big problems for a while now with connecting to network drives
> when I work from home over VPN. My employer’s support people haven’t been
> able to find a solution yet and are basically out of solutions. Here’s the
> problem – I’ll try to be as short as possible. Numbers 2, 3 and 4 below are
> results of possible workarounds already tried.
>
> 1. Trying to connect to any mapped network drive results in the (well
> known?) message “an error occurred while reconnecting…… local device name is
> already in use”.
> 2. when I remove all mappings (either when I’m at home or in the office
> before trying again at home) and then try to do “start – run” and type the
> relevant server name, I get a logon screen, and then after I type the
> username and password info, there’s a text balloon coming up saying “The user
> name that you’re trying to logon with is the same name that you are already
> logged on with. That user name has already been tried. (hence the logon
> screen coming up I guess) A domain controller could not be found to verify
> that name.
> 3. another solution was to try and add the drives to My Network Places. This
> results in a windows error message “Run a DLL as an App”
>
> Sometimes it does work when I don’t shutdown the PC at the office, but
> instead Hibernate. Then it’ll be OK using mapped drives for one time at home
> – until I hibernate, shutdown or re-boot again only.
>
> Current workaround is to logon to the PC with a local user. That’s OK, but
> it makes it incredibly irritating to work with VPN – as each and every time I
> use the internet, intranet, outlook or anything I am prompted for my username
> and password.
>
> Like all trained support staff do – it has of course been suggested that my
> home equipment causes the problem – or some settings at my providers. I can’t
> believe this is the case as I’ve recently switched providers and also
> modem/router equipment, but that doesn’t make any difference. Also the
> problem hasn’t always been there, and at least 3 months before or after it
> started there have been no changes in my hardware and provider.
>
> System info:
> Dell M2
> Win XP SP 2 + all fixes
> 1GB memory
> Normally logging on to the company domain.
>
> Thanks for taking the time to read all this – suggestions very welcome.
> Regards
> Wim
>
.

Relevant Pages

  • Re: Bad Command in TSO logon panel
    ... As Barry Schwarz' response has already correctly implied, the TSO logon command is not stored in the users profile data set but in the COMMAND field of the TSO segment of the user's RACF user profile, so changing the user's ISPF profile dataset will have no effect. ...
    (bit.listserv.ibm-main)
  • Re: Second DC cannot authenticate to other DC
    ... Disconnect any mapped drives that might already exist between the two DCs ... If it still fails to connect open the command ... > the SBS domain controller results in a logon prompt. ...
    (microsoft.public.windows.server.active_directory)
  • RE: VPN & Mapped Network drives
    ... Hi Desco, thanks for responding to this issue. ... Please accept I'm just a normal user, ... you is that I just type the servername in the command box. ... >> relevant server name, I get a logon screen, and then after I type the ...
    (microsoft.public.windowsxp.network_web)
  • Re: Practical jokes for mainframe systems programmers
    ... then walk over and proceed to logon as normal. ... "command prompt" of the interactive system we used. ... people's reactions, while FUN was running, was FUN! ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • RE: Drive map issues after SP1
    ... appears that the command only needs to run once and then the drive will be ... the next time you logon the client ... we can add the following line to the logon script ... before the map drive command to delete all the mapped drives: ...
    (microsoft.public.windows.server.sbs)