Reset Search
 

 

Article

KB23524 - [SBR] Getting an error message "Unable to bind UDP socket for Radius requests" on debug logs and SBR is unresponsive.

« Go Back

Information

 
Last Modified Date8/1/2015 7:53 AM
Synopsis
SBR installed on Windows 2008 server and user authentication fails . In SBR debug logs and getting the following error during the service startup .

04/12/2012 17:33:57 F:\build\tmp.3\SBR\xradius\radauthd.c radAuthMain() 142 Entering
04/12/2012 17:33:57 Unable to bind UDP socket for Radius requests
04/12/2012 17:33:57 Failed in attempt to bind to 10.141.232.50 and well-known port 1646
04/12/2012 17:33:57 Unable to bind UDP socket for Radius requests
04/12/2012 17:33:57 Failed in attempt to bind to 10.141.232.50 and well-known port 1813
04/12/2012 17:33:57 Initializing Radius Authentication socket communications
04/12/2012 17:33:57 Unable to bind UDP socket for Radius requests
04/12/2012 17:33:57 Failed in attempt to bind to 10.141.232.50 and well-known port 1645
04/12/2012 17:33:57 Unable to bind UDP socket for Radius requests
04/12/2012 17:33:57 Failed in attempt to bind to 10.141.232.50 and well-known port 1812

SBR debug logs doesn't contain any information  regarding the user authentication failure. On the Supplicant end the session is timed out.
In a packet capture able to see the radius Access request coming in but SBR is not responding back with a Radius Access accept / Access reject.
Problem or Goal
Cause
This problem is due to an other program is already using the radius ports 1812,1813,1645,1646 on the server.


Solution
Microsoft Network policy server ( Radius implemention of Microsoft  Windows 2008 ) was also running on the same SBR server as a result SBR application couldn't make use of the radius ports .


1. Open Services Console
2. Stop  'Network policy Server" and set the startup type to "Disabled"
3. Restart SBR service.

Now you will be able to see the following messages on the debug logs & the issue will be resolved.

04/12/2012 17:41:46 Initialized Radius socket address 10.141.232.50 port 1646 (receive buffer size 8192 bytes)
04/12/2012 17:41:46 Initialized Radius socket address 10.141.232.50 port 1813 (receive buffer size 8192 bytes)
04/12/2012 17:41:46 Initializing accounting thread pool
04/12/2012 17:41:46 Initializing Radius Authentication socket communications
04/12/2012 17:41:46 Initialized Radius socket address 10.141.232.50 port 1645 (receive buffer size 8192 bytes)
04/12/2012 17:41:46 Initialized Radius socket address 10.141.232.50 port 1812 (receive buffer size 8192 bytes)
Related Links
Attachment 1 
Created ByData Deployment

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255