EventID 20189 when trying to connect client to Windows 2003 RRAS V

Whenever my users try and connect to my VPN, they get this message:

Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20189
Date: 6/30/2006
Time: 4:21:18 PM
User: N/A
Computer: XXXX
Description:
The user xxxxxx connected from xx.xx.xx.xxbut failed an authentication
attempt due to the following reason: Authentication was not successful
because an unknown user name or incorrect password was used.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


This has been our VPN server for a year or so. Had some hardware crash, did
a repair install, and now users can connect, but not do anything on our
network. Also if I try pinging the IP assigned to the client, I get a result
I've never seen before.

ping 192.168.1.180

Pinging 192.168.1.180 with 32 bytes of data:

Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.

The response is coming from the IP of the VPN server, not the client. This
is bewildering to me....

I have one remote access policy configured, for which I used the wizard to
create. It is just set to allow access to users in 4 different Domain Groups.

You may receive above errors if you configure Dial-in Media incorrectly. This troubleshooting link may help,

Event ID Troubleshooting Event ID 20189 - The user <username> connected from xxxx but failed an authentication attempt due to the following reason: The user tried to connect using ...
www.chicagotech.net/wineventid.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"SushiSean" <(E-Mail Removed)> wrote in message news:2AAFF47A-7796-4311-B2B0-(E-Mail Removed)...
Whenever my users try and connect to my VPN, they get this message:

Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20189
Date: 6/30/2006
Time: 4:21:18 PM
User: N/A
Computer: XXXX
Description:
The user xxxxxx connected from xx.xx.xx.xxbut failed an authentication
attempt due to the following reason: Authentication was not successful
because an unknown user name or incorrect password was used.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


This has been our VPN server for a year or so. Had some hardware crash, did
a repair install, and now users can connect, but not do anything on our
network. Also if I try pinging the IP assigned to the client, I get a result
I've never seen before.

ping 192.168.1.180

Pinging 192.168.1.180 with 32 bytes of data:

Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.
Reply from 192.168.1.91: TTL expired in transit.

The response is coming from the IP of the VPN server, not the client. This
is bewildering to me....

I have one remote access policy configured, for which I used the wizard to
create. It is just set to allow access to users in 4 different Domain Groups.