Re: shared drives and vpn
- From: RW <RW@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 19:45:01 -0800
this is similar situation, this is AD user using laptop offsite laptop is
part of the doamin so user after booting up laptop supply AD user name and
password, laptops let the user login because credentials are cached, now user
logon via VPN (we have firewall configured to use internal DC as LDAP server
so user use AD user name and password to connect via VPN) drives are already
mapped while user logon to doamin in the office by script in GP applied...
mapping drives with "different user name" would make sense if laptop is not
part of domain and user uses different uid and password to logon to laptop
then domain one, which is not the case here... I think somehow because cached
credential are used user cannot be validated by DC when trying to access
shares, why?
"TCol" wrote:
I had similar problem, although not a roaming laptop - but active directory.
user logging in thru vpn from offsite. When mapping the drive thru the vpn,
the user was authenticating to active directory with the vpn logon instead of
the active directory logon. When mapping the drive, I selected "Connecting
using a different user name" and put the active directory username/pswd in
here so when it tries to map to the network share, it authenticates with the
AD instead of VPN credentials.
"RW" wrote:
Thanks for trying but this isn’t our issue, network IP ranges are not
overlapping if this would be the case remote user would not be able to
connect via vpn at all, in vpn config allowed ranges are different from our
internal subnets and remote user can connect no problem this isn’t ipsec
issue… additionally once connected user can map network drives manually if
they were disconnected previously before logging off and leaving LAN (day
before)
This also isn’t dns problem because once connected user can do nslookup
server1 and gets respond from internal dns resolving to
server1.internl_domain.com and its IP
Any other ideas?
"Brian P. Hammer" wrote:
RW, A couple issues similar to those you had. The biggest fix to resolve
all of them was to have the users home network, or the network they were on
a different network. For example, I had a network of 192.168.1.x and home
users with routers with the same network. Changing them to 192.168.10.x
fixed the problem. I also had to make sure DNS was set up correctly. This
seemed to fix the mapped drive issues and intermittent Exchange issues we
were having.
HTH,
Brian
"RW" <RW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:48FEE60F-BDEA-4E59-8C33-F4E6184C221E@xxxxxxxxxxxxxxxx
user logged on laptop offsite with cache credentials (laptop joined to
domain
and all working ok when in the office), connecting then via 3rd party vpn
client cannot access mapped network drives, I created temp shared folder
on
different server and ask to map drive to this one, all work no issues, I
then
create cname in dns for existing file server and ask user to map another
drive to same serverd folder he already had divers mapped using cname and
all
works... so somehow if drives are mapped when user works in lan then go
offsite he cannot access any of those drives over vpn?
any idea?
- References:
- Re: shared drives and vpn
- From: Brian P. Hammer
- Re: shared drives and vpn
- Prev by Date: Is Domain Policy can do?
- Next by Date: Re: Drive Read Only..
- Previous by thread: Re: shared drives and vpn
- Next by thread: RE: shared drives and vpn
- Index(es):
Relevant Pages
|
