Radius Server Not Logging Authentication and Accounting When Users Connect from RRAS

• Microsoft Windows NT Server version 4.0
• Microsoft Routing & Remote Access Service Update for Windows NT Server version 4.0

SYMPTOMS

Your Radius server fails to log accounting or authentication information when users are authenticated by a Routing and Remote Access Server (RRAS).

CAUSE

RRAS is using different ports for Radius accounting and authentication than your Radius server.

RESOLUTION

To resolve this problem, change the ports on your RRAS server to match the ports that are being used by your Radius server using the following steps:

1. Click Start, point to Settings, and then click Control Panel.



2. Double-click Network, click the Services tab, click Routing and Remote Access, and then click Properties.



3. Click Network and then click Configure under the Authentication Provider section.



4. Click the Radius server on which you want to edit the port number and then click Edit.



5. Change the port number to the same port number that your Radius server is using.



6. Click OK in the Radius Server dialog box.



7. Click OK in the Radius Configuration dialog box.



8. Click OK in the Network Configuration dialog box, click Continue, click Close, and restart your computer when prompted.

MORE INFORMATION

For more information, see RFC 2138 and RFC 2139.

For information about obtaining a RFC document, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q185262
TITLE : How to Obtain Request for Comments Documents

Keywords          : kb3rdparty kbnetwork ntnetserv ntrouter NTSrv 
Version           : WinNT:4.0
Platform          : winnt 
Issue type        : kbprb 

Last Reviewed: February 2, 1999