|
Question : Windows 98 Gets Error 649: No Dial in Permission when using RAS into Windows 2003 Server running RRAS using IAS for Radius Authentication
|
|
We have recently upgraded our RAS server from Windows 2000 to Windows 2003. Since then, Windows 98 clients trying to dial in get Error:649 You do not have dial in permission. Windows XP computers(the same user) can get in just fine.
We have an NT4 domain server and in User Manger for Domains - the user has dial in permission. We use IAS for our Radius server - this was recently setup by another member of IT.
On the Windows 2003 RAS server - I see the error: Event ID: 20078 The account connected on com port 3 does not have Remote Access Priviledge. The line has been disconnected.
|
Answer : Windows 98 Gets Error 649: No Dial in Permission when using RAS into Windows 2003 Server running RRAS using IAS for Radius Authentication
|
|
Well, MS is doing the double-dance on this one. It is one of the greatest problems with 2003 server -- the dropping of 98 and NT support, and you can believe, by Gates, it was intentionally deliberate. They simply don't want to support NT4 and 98 any more, costs them too much "money", and just think how much more "money" they can make, if they force you to upgrade those NT4 servers and 98 clients to 2003 and XP. It is calculated marketing ploy, in fact, I know that for a fact, MS has even admitted it.
So, how to fix it? The classic MS solution? Everything that was going through the NT4 server for logins now needs to be done through the 2003 server -- that is the root of the problem. OK, that dispenses with the NT4 server, another 2003 license sold, more "money". Now the 98 WSs need fixing too, because as members of the NT4 domain, they have typical 98-NT protocols installed. This one is a little easier to solve. You can set the 98 systems to get a RAS privilege login directly to the 2003 server, as long as they are running MS Client, TCP/IP, and are listed in the AD registry, or have valid login accounts. So they can be fixed, but the 98 login through the NT4, then going to 2003 cannot. You have to break that chain.
|
|
|
|