Article ID: 189749
Article Last Modified on 6/9/2006
APPLIES TO
- Microsoft Internet Authentication Services for Remote Access Service 1.0
- Microsoft Commercial Internet System 2.0
- Microsoft Internet Information Server 4.0
This article was previously published under Q189749
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
SYMPTOMS
When using a U.S. Robotics(USR)/3Com Total Control Chassis with Microsoft Internet Authentication Service (Radius), administrators may notice that the Radius log files do not show up properly.
CAUSE
There are several reasons why this may occur. Assuming authentication is working properly and users are able to log on, the most likely causes are as follows:
- A known bug exists in the Total Control firmware. Please ensure you are running version 3.6.28 or later. For more information, please contact USR/3Com.
- By default, Radius requires that the Shared Secret that is used for authentication also be used for accounting. If no Shared Secret is set up in the USR box, Radius Logs are not created.
STATUS
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
For information about how to contact 3Com Corp., query in the Knowledge Base for one of the following articles:
MORE INFORMATION
In general, here are the commands used on the USR Total Control to set up a Shared Secret for Radius accounting. If you have specific questions, please contact USR/3Com support.
Commands to use if you are running USR Netserver software:
- Set authentic <IP address of radius server>;
- Set secret <secret key>;
- Set accounting <IP address of accounting server> <secret key>;
- Set acct_authchk on;
- Save all.
For customers with Netserver 8/16, Netserver 8plus or other USR/3Com equipment that uses the newer Netserver plus code 4.1.x, a known bug exists in the 3Com code that does not allow a user to set up a Shared Secret for Radius accounting as required by RFC2139. USR/3Com has released a hotfix to this problem. Customers affected should contact 3Com and request "Emergency release 4.1.86.[ASCII 148]
The above steps are given as a guideline only on how to set up the USR Total Control. For specifics, please contact USR/3Com support.
Additional query words: vpn radius CIAS USR prodmcis2
Keywords: kbprb KB189749
