A
Alexander A. Manaeff
I have a Windows 2000 Enterprise Server SP4 with RRAS Server with one modem
(not Domain Controller). First RAS client connects, succeeds makes use of
the network and then disconnects. After this clients [including the first
client] can connect to the server but cannot ping or access the network.
After reboot RRAS server the same happens (first client work, and other
can't ping or acces the network).
I try to use Windows authentification in RRAS properties and then RADIUS
authentification (with IAS on DC) - the same happens.
This is event from system log - when client can work and when client can't
work (events are equal)
User DOMAIN\User was granted access.
Fully-Qualified-User-Name = domain.com/Users/User
NAS-IP-Address = 81.24.152.15
NAS-Identifier = <not present>
Client-Friendly-Name = 192.168.20.2
Client-IP-Address = 192.168.20.2
Calling-Station-Identifier = <not present>
NAS-Port-Type = Async
NAS-Port = 11
Proxy-Policy-Name = Use Windows authentication for all users
Authentication-Provider = Windows
Authentication-Server = <undetermined>
Policy-Name = Connections to Microsoft Routing and Remote Access server
Authentication-Type = MS-CHAPv2
EAP-Type = <undetermined>
Also, two my friends from different organizations have similar problem with
Windows 2000 Advanced Server SP4. More of than, i try to create RRAS on
Windows 2003 Enterprise Edition (not DC) - similar problem.
Also I try to create incomming connection in Windows 2003 Ent. edition (not
DC) - similar problem!
But, when i create incoming connections in Windows XP or enable RRAS on DC
(Windows 2003 Ent. Edition) - everything works correctly.
Why? I'd like to work with RRAS on Windows 2000 or Windows 2003 not DC!
Alexander A. Manaeff
(not Domain Controller). First RAS client connects, succeeds makes use of
the network and then disconnects. After this clients [including the first
client] can connect to the server but cannot ping or access the network.
After reboot RRAS server the same happens (first client work, and other
can't ping or acces the network).
I try to use Windows authentification in RRAS properties and then RADIUS
authentification (with IAS on DC) - the same happens.
This is event from system log - when client can work and when client can't
work (events are equal)
User DOMAIN\User was granted access.
Fully-Qualified-User-Name = domain.com/Users/User
NAS-IP-Address = 81.24.152.15
NAS-Identifier = <not present>
Client-Friendly-Name = 192.168.20.2
Client-IP-Address = 192.168.20.2
Calling-Station-Identifier = <not present>
NAS-Port-Type = Async
NAS-Port = 11
Proxy-Policy-Name = Use Windows authentication for all users
Authentication-Provider = Windows
Authentication-Server = <undetermined>
Policy-Name = Connections to Microsoft Routing and Remote Access server
Authentication-Type = MS-CHAPv2
EAP-Type = <undetermined>
Also, two my friends from different organizations have similar problem with
Windows 2000 Advanced Server SP4. More of than, i try to create RRAS on
Windows 2003 Enterprise Edition (not DC) - similar problem.
Also I try to create incomming connection in Windows 2003 Ent. edition (not
DC) - similar problem!
But, when i create incoming connections in Windows XP or enable RRAS on DC
(Windows 2003 Ent. Edition) - everything works correctly.
Why? I'd like to work with RRAS on Windows 2000 or Windows 2003 not DC!
Alexander A. Manaeff