Re: Routing and Remote Access - Authentication Failure
- From: "Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 May 2009 11:52:58 -0400
"Matrixx333" <matrixx333@xxxxxxxxx> wrote in message news:ffd8287f-27ed-4638-8923-fbddada9407b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Speaking of Domain or Workgroup, the account you are using to
establish the connection must either be in AD or configured in the
local SAM of the VPNSERVER if it is a workgroup. If you are on a
domain and have an account in AD, I would suggest looking at the
Remote Access Policies in Routing and Remote Access. Is the username a
member of a group that hasn't been configured with a Remote Access
Policy? Does the AD account have dial-in permissions? Also the client,
server, and policy all have to be configured with at least one common
authentication protocol and encryption strength.
Hope this helps.
Good point, Matrixx! I didn't ask where the user account was created.
Ace
.
- References:
- Routing and Remote Access - Authentication Failure
- From: George Valkov
- Re: Routing and Remote Access - Authentication Failure
- From: Matrixx333
- Routing and Remote Access - Authentication Failure
- Prev by Date: Re: Routing and Remote Access - Authentication Failure
- Next by Date: Re: How max sessions per user support a windows 2003 folder share?
- Previous by thread: Re: Routing and Remote Access - Authentication Failure
- Next by thread: Re: Routing and Remote Access - Authentication Failure
- Index(es):
Relevant Pages
|
