vpn authentication problems on some remote workstations

  • Thread starter Thread starter Jason Gallas
  • Start date Start date
J

Jason Gallas

When a user connects to the VPN (Windows 2000 RADIUS over WatchGuard
Firebox) I expect the following to happen:

1. Authenticated to shares automatically - the user can freely browse shares
without being asked for a password.
2. Authenticated to exchange server automatically - the user can open
his/her email and check it without being asked for a
username/password/domain.

However, on some systems (mainly windows 2000 pro) users connect to shares
fine but have problems authenticating to the Exchange 5.5/Windows 2000
server. They are asked again for their username/password/domain. I thought
that connecting to the vpn took care of this? I have searched the web and
have found other users that had the same/similar problems but have had no
luck finding any solutions. I even tried some registry modifications to no
avail. I have also tried making the laptop a member of a workgroup the same
as the domain name and making a username/password on that laptop to match
the domain username/password which also didnt' work. Any help would be
greatly appreciated
 
Hi - wrong newsgroup? Try microsoft.public.win2000.networking.

I'm not sure your assumptions are correct, unless the computers are joined
to the domain and the user is logging into the domain w/cached credentials.
And re browsing remotely - much depends on your VPN setupcapabilities.
 
"Lanwench [MVP - Exchange]"
Hi - wrong newsgroup? Try microsoft.public.win2000.networking.

I'm not sure your assumptions are correct, unless the computers are joined
to the domain and the user is logging into the domain w/cached credentials.
And re browsing remotely - much depends on your VPN setupcapabilities.

Reposted in public.win2000.networking.

The firewall is setup correctly to allow access to every port for every vpn
user. For most people that connect via vpn everything works fine. They are
able to browse shares and connect to outlook without entering their
username/password/domain again. It is an isolated incident on a couple
machines.
 
I'll take a look for it there to follow the thread.

Jason Gallas wrote:
 
Back
Top