unable to connect win98 to w2k RRAS server
I have a W2k RRAS server with SP3 installed. When I try to get a win9x client to connect via dialup, the client PC always gets an error. The event logs on the W2k RRAS server show 'The authentication server did not respond to authentication requests in a timely fashion.
I have a W2k RRAS server with SP3 installed. When I try to get a win9x client to connect via dialup, the client PC always gets an error. The event logs on the W2k RRAS server show 'The authentication server did not respond to authentication requests in a timely fashion.' errors. The RRAS server is properly registered with AD and is in the RAS and IAS servers group. This only happens with Win9x clients. W2k and XP dialin clients connect correctly. I've tried using different forms of the username incase its being screwed up (ie used DOMAIN\username, username@domain etc) to no avail. Even more confusing is that this only happens using a modem connection, forming a PPTP VPN with win9x connects!
Any ideas on why this is so?
Any ideas on why this is so?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
http://support.microsoft.com/?kbid=299684
http://support.microsoft.com/?kbid=227747
http://www.windows-expert.net/faq/Networking/rras-does-not-authenticate-user.asp
http://www.cottagesoft.com/Win2000FAQ.htm
I believe for Windows 98 the latest version for DUN is 1.4, is this installed? I have also encountered this when a v92 modem is trying to connect to a v90 modem pool on our RAS servers. Changing the AT string on the clients to force v90 comptability solved our issue. This was the string .... +MS=v90.0
Hopefully these ideas and links will solve your problem.
http://support.microsoft.com/?kbid=227747
http://www.windows-expert.net/faq/Networking/rras-does-not-authenticate-user.asp
http://www.cottagesoft.com/Win2000FAQ.htm
I believe for Windows 98 the latest version for DUN is 1.4, is this installed? I have also encountered this when a v92 modem is trying to connect to a v90 modem pool on our RAS servers. Changing the AT string on the clients to force v90 comptability solved our issue. This was the string .... +MS=v90.0
Hopefully these ideas and links will solve your problem.
Win98se has dun 1.4 installed. I'm not using IAS, RRAS is using Windows auth, not RADIUS.
Really beats me as to what is going on here. If it was a general auth problem, then the Win9x clients (and for that matter XP / W2k ) should fail all the time. Win9x can sucessfully bring up a PPTP connection, XP and W2k can get any type of connection. Only modem dialups fail with 9x.
Really beats me as to what is going on here. If it was a general auth problem, then the Win9x clients (and for that matter XP / W2k ) should fail all the time. Win9x can sucessfully bring up a PPTP connection, XP and W2k can get any type of connection. Only modem dialups fail with 9x.
Well if it isnt hardware based, I would double check;
1. Remote access policies.
2. Enable PPP logging on the RAS box, and check those logs.
3. Try to see if a local account on the RAS box has the ability to authenticate, unlike a domain account.
4. Is the Client for Microsoft Networks installed on the 98 laptops?
5. Types of authentication security, such as MS-CHAP, and what levels of encryption.
I'm sure clutch, APK, and others will chime in here as well.
1. Remote access policies.
2. Enable PPP logging on the RAS box, and check those logs.
3. Try to see if a local account on the RAS box has the ability to authenticate, unlike a domain account.
4. Is the Client for Microsoft Networks installed on the 98 laptops?
5. Types of authentication security, such as MS-CHAP, and what levels of encryption.
I'm sure clutch, APK, and others will chime in here as well.
I had already installed a blanket allow everybody at all times etc RAS policy to try to resolve the problem.
PPP logging generates lots n lots of output (already done that too!). Does anyone have a tool to make the file human readable?
Will definitely try a local account and see what happens... Local accounts fail in the same way
MS file / print is not installed on the client computer and it not being there shouldn't stop the client from connecting.
I've had all the passwd encrypt methods enabled, but now back to defaults of MSCHAP 1 and 2.
Data encryption set to optional, but tried forcing it on one / both of the client / server to no avail.
Looking at the event logs, it always says user is \username for, maybe that \ is a clue.
PPP logging generates lots n lots of output (already done that too!). Does anyone have a tool to make the file human readable?
Will definitely try a local account and see what happens... Local accounts fail in the same way
MS file / print is not installed on the client computer and it not being there shouldn't stop the client from connecting.
I've had all the passwd encrypt methods enabled, but now back to defaults of MSCHAP 1 and 2.
Data encryption set to optional, but tried forcing it on one / both of the client / server to no avail.
Looking at the event logs, it always says user is \username for, maybe that \ is a clue.
