VPN & Home Folder mapping

  • Thread starter Thread starter Marcelo Rizzo
  • Start date Start date
M

Marcelo Rizzo

I am trying to map a home folder across a vpn connection using a batch file.
net use x: \\server_name\%username%$

The problem is the script sees the local username and not the one used by
the vpn.
Is there a environment variable for the username used in the vpn or is there
a work around (other than using the actual username)?

Much appreciated

Marcelo Rizzo
 
Have you tried:
net use x: \\server_name\%username%$ /user:domain\username

This works for me!

-s-
 
That has the same effect.
I am trying not to hard code the users name in the logon script so I can use
the script for multiple users.

Cheers,
M
 
You are seeing normal behavior. The username use for VPN is *only* for
that. All it does is create the VPN connection, it does not have anything to
do with authentication on the network you are seeking resources in.

Assuming this is not a Win98 machine, at the Control-Alt-Del prompt there
is a checkbox that is for logging on with a choosen dial up connection.
Enable that and choose the VPN connection. It will then establish the VPN
connection with the Conectiod credentials before you go into the desktop and
then present the main credentials (from Crtl-Alt-Del prompt) to the Remote
network and log you into the remote network as if you were on a LAN. This
implies two things:

1. You have an account on the remote network
2. Your machine is a member of the remote network's Domain.


If it is a Win9x machine;
1. Make the Workgroup Name is the same as the Remote Domain.
2. Set it to *not* log into the domain,..it'd be a waste of time because
it'd probably never find the DC dependably.
3. Delete the existing local *.pwl file on your machine
4. Create a new *.pwl file by logging into Win9x again, but use a matching
password so the username and password locally in Win9x is the same as the
Remote Account
5. Cross your fingers and hope for the best and don't expect "perfect"
behavor as if it was on the LAN in a normal manner.
 
I was afraid of that.
Unfortunatelly, the users I support don't want that hassle. Too much work
they say. Oh well!!

Thank you all nonetheless.
M

Phillip Windell said:
You are seeing normal behavior. The username use for VPN is *only* for
that. All it does is create the VPN connection, it does not have anything to
do with authentication on the network you are seeking resources in.

Assuming this is not a Win98 machine, at the Control-Alt-Del prompt there
is a checkbox that is for logging on with a choosen dial up connection.
Enable that and choose the VPN connection. It will then establish the VPN
connection with the Conectiod credentials before you go into the desktop and
then present the main credentials (from Crtl-Alt-Del prompt) to the Remote
network and log you into the remote network as if you were on a LAN. This
implies two things:

1. You have an account on the remote network
2. Your machine is a member of the remote network's Domain.


If it is a Win9x machine;
1. Make the Workgroup Name is the same as the Remote Domain.
2. Set it to *not* log into the domain,..it'd be a waste of time because
it'd probably never find the DC dependably.
3. Delete the existing local *.pwl file on your machine
4. Create a new *.pwl file by logging into Win9x again, but use a matching
password so the username and password locally in Win9x is the same as the
Remote Account
5. Cross your fingers and hope for the best and don't expect "perfect"
behavor as if it was on the LAN in a normal manner.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Marcelo Rizzo said:
That has the same effect.
I am trying not to hard code the users name in the logon script so I can use
the script for multiple users.

Cheers,
M

batch
file. used
by is
there
Click to expand...
Click to expand...
 
Marcelo Rizzo said:
I was afraid of that.
Unfortunatelly, the users I support don't want that hassle. Too much work
they say. Oh well!!
Click to expand...

Then they are victems of their own lazyness.
 
Back
Top