Select the product you need help with

RADIUS Cannot Re-Establish a Connection to ODBC Data Source

Article ID: 221196 - View products that this article applies to.

This article was previously published under Q221196

SYMPTOMS

When Remote Authentication Dial-In User Service (RADIUS) uses an ODBC data source for validation data, it cannot re-establish a connection to the ODBC data source if the connection is broken (database crash, database maintenance, network storm, hardware problems, electrical outages).

Back to the top | Give Feedback

CAUSE

No retry logic was implemented for ODBC, so the service fails to start if the database is unavailable, and fails to reconnect if the server is unreachable for any reason.

Back to the top | Give Feedback

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

Windows Service Pack Center
(http://windows.microsoft.com/en-US/windows/downloads/service-packs)
-or-
152734
(http://support.microsoft.com/kb/152734/EN-US/ )
how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

(http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS)

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734

(http://support.microsoft.com/kb/152734/EN-US/ )

How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top | Give Feedback