win98 clients can't connect to 2k3 RAS/VPN server

[Larry Belan]

Hopefully the good folks here can point me in the right direction:

In august, I setup a 2k3 server to run RAS as mainly a VPN server, and I
did test using win92se clients. The 2k3 server is just a member of a 2k
AD domain...no upgrades to the domain for 2k3 support yet.

All was working just fine in august, but it appears that some of MS's
security updates have cause the Win98 clients to NOT create a VPN
connection. Win2k, XP, and Mac OS X clients are working just fine, but
NO win98 box can connect.

I've looked at the IAS logs, and it appears that the win98 login was
sucessful, but it immediately disconnects and gives a 645 error.

another twist to this issue is that I have RAS/VPN wunning on a 2k
server, and the win98 clients connect without ANY problems at all.

I've swept through the MS KB, but don't see anythin directly related to
this issue.

has anyone else been the victim of this problem? have you been able to
recover?

Pointers would be appreciated.

TIA!

Larry

 

[Janani V[MSFT]]

Can you enable logging on both the server and client and let us know if
there is anything interesting in the logs?
You can enable logging using the command:
netsh ras set tracing * ena
After making the connection disable tracing using 'netsh ras set tra * dis'
and look at the logs.
The logs will be in %windir%\tracing directory

 

[Larry Belan]

Can you enable logging on both the server and client and let us know if
there is anything interesting in the logs?
You can enable logging using the command:
netsh ras set tracing * ena
After making the connection disable tracing using 'netsh ras set tra * dis'
and look at the logs.
The logs will be in %windir%\tracing directory

Janani,

I've finally been able to get back to this issue, but I can't trace on
the Win98 system. 'netsh' is not a valid command. are there some debug
tools that i could download/install?

On the W2k3 server...there's a LOT tracing files there. Could you point
me to the one(s) in particular that have some relavant info?

thanks

 

[Larry Belan]

Can you enable logging on both the server and client and let us know if
there is anything interesting in the logs?
You can enable logging using the command:
netsh ras set tracing * ena
After making the connection disable tracing using 'netsh ras set tra * dis'
and look at the logs.
The logs will be in %windir%\tracing directory

Janani,

I've finally been able to get back to this issue, but I can't trace on
the Win98 system. 'netsh' is not a valid command. are there some debug
tools that i could download/install?

On the W2k3 server...there's a LOT tracing files there. Could you point
me to the one(s) in particular that have some relavant info?

thanks