i.e. Stop running as a service and from a command prompt enter radius -x
(or radius -x15 for maximum debug level)
This will tell you if RadiusNT is even receiving a request and part of the
debug log will tell you what port(s) it is listening on.
Also what port (if any) is listed for radius (and radacct) in the
> -----Original Message-----
> From: Rune M. Jonassen [mailto:email@example.com]
> Sent: 30 September 2000 19:30
> To: firstname.lastname@example.org
> Subject: [RadiusNT] Radiusnt 3.0 won't listen on port 1645 or 1646
> We have had some trouble with our former radiusnt 2.5 forcing
> us to upgrade
> to ver. 3.0
> We authenticate to an MS SQL v.7.0 via ODBC and the access
> router requesting
> the RadiusNT 3.0 is a Cisco AS5360. We are running all on NT4.0 SP5.
> We know that our link to the SQL database is correct and have
> checked it
> with the radlogin.exe and radlogin3.exe. These both reports
> that user is
> verified when we send a request for a registered user. In the
> same way we
> are denied access when typing in a false user.
> We have also tried the NTRadPing from another client
> requesting RadiusNT to
> Using Sniffer, we see that the request is made to the correct
> IP and port.
> Still RadiusNT won't respond. A portscan on the RadiusNT
> server do not show
> any activity on port 1645 and 1646 (we have also tried to
> change to port
> 1812 and 1813 without any difference)
> Any help appreciated..
> Regards Rune M. Jonassen
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: