grovenetsupport
asked on
SBS 2003 VPN Password problem
Silly one here, we have an sbs 2003 server running routing and remote access. All existing VPN users are fine and work ok but we cannot setup new ones. I have not looked after the server for long so have inherited the build. All we get off Win 7 and Win 8 clients is username or password are incorrect when we know they work.
Could someone point me in the right direction as I have never had this before its normally simple. I have had both VPN connection settings side by side and they are matched identically but still no luck?
Could someone point me in the right direction as I have never had this before its normally simple. I have had both VPN connection settings side by side and they are matched identically but still no luck?
ASKER
No event logs are clear I checked this hoping it would shed some light on it.
Right, so you're not even getting to present your credentials to the VPN server.
Install telnet client on one of the Win7 boxes from Add/Remove Programs > Turn Windows Features On or Off and then run telnet address.of.vpn.svr 1723
you should get a blank screen
On the Win 7 client, right-click the VPN you have configured and go to Properties > Security and set type to PPTP , also confirm that CHAP and CHAP v2 are checked under allowed authentication types on the same screen.
Install telnet client on one of the Win7 boxes from Add/Remove Programs > Turn Windows Features On or Off and then run telnet address.of.vpn.svr 1723
you should get a blank screen
On the Win 7 client, right-click the VPN you have configured and go to Properties > Security and set type to PPTP , also confirm that CHAP and CHAP v2 are checked under allowed authentication types on the same screen.
ASKER
I have replicated the properties of the working one and it has all of the above checked. I have tried off my win 8 laptop and a random windows 7 box and its as if it knows its new and not authorised?
"I have replicated the properties of the working one and it has all of the above checked"
OK, so what happens when you telnet on 1723? Does it connect OK?
Do you have any 'audit failure' events in the security log?
Does the user have Remote Access (Dial-In) permission if you check the user account in AD?
OK, so what happens when you telnet on 1723? Does it connect OK?
Do you have any 'audit failure' events in the security log?
Does the user have Remote Access (Dial-In) permission if you check the user account in AD?
ASKER
The reason this showed its head is the fact that the user has had a new laptop. On the old laptop Windows 7 the vpn works a treat using the same user credentials as the new one.
I am trying the telnet now but VPN on the server works I just don't seem to be able to setup new and replicated VPN's
I am trying the telnet now but VPN on the server works I just don't seem to be able to setup new and replicated VPN's
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all your help
Glad you got it fixed Grovenetsupport, but if the port wasn't opened correctly on the firewall then none of the VPNs would have worked, no? Colour me confused.
ASKER
Fault was found onsite. Thanks for all your help guys.
Can the problematic clients connect to a different VPN server without issue?