Jump to content

workhardplayharder

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by workhardplayharder

  1. Nothing from the old domain was salvagable. Started from scratch. Moved all in house pcs to new domain. Having issues with vpn in from home or the road.
  2. I have two cisco asa firewalls bridging a satelite office to the main facility. This has been up and running for around three years now. Recently the domain controller (SBS2003) went up in smoke, literally. long story short, i have setup a new pc with sbs2003 from scratch. used the old domain controllers name and ip address but changed the domain name. my network bridge is still in tact, however no one can VPN into the system from home or on the road. I'm having some trouble getting the cisco box to play nice with radius or the other way around. used a fake name and this is what showed up in event viewer User monkey was denied access. Fully-Qualified-User-Name = CATCOMTEC2\monkey NAS-IP-Address = 192.168.0.5 NAS-Identifier = Called-Station-Identifier = 206.248.24*.** Calling-Station-Identifier = 206.248.24*.** Client-Friendly-Name = asa Client-IP-Address = 192.168.0.5 NAS-Port-Type = Virtual NAS-Port = 26 Proxy-Policy-Name = Use Windows authentication for all users Authentication-Provider = Windows Authentication-Server = Policy-Name = Authentication-Type = PAP EAP-Type = Reason-Code = 16 Reason = Authentication was not successful because an unknown user name or incorrect password was used. used a real account below and see the difference User cworsham was denied access. Fully-Qualified-User-Name = catcomtec2/Users/Chris NAS-IP-Address = 192.168.0.5 NAS-Identifier = Called-Station-Identifier = 206.248.24*.** Calling-Station-Identifier = 206.248.24*.** Client-Friendly-Name = asa Client-IP-Address = 192.168.0.5 NAS-Port-Type = Virtual NAS-Port = 26 Proxy-Policy-Name = Use Windows authentication for all users Authentication-Provider = Windows Authentication-Server = Policy-Name = cctivpn Authentication-Type = PAP EAP-Type = Reason-Code = 66 Reason = The user attempted to use an authentication method that is not enabled on the matching remote access policy. any insights as to the difference in the Fully qualified user name, the errors thrown. why is my authentication server showing as undetermined? please help, i've got to get this back up quick!
×
×
  • Create New...