Endpoint Protection

Failed to start Radius Server. "The radius port may be used by another process" is reported in my server as a critical error under "SECARS" 4097.

Advice sought.

Hi,

Please see the thread: https://www-secure.symantec.com/connect/forums/failed-start-radius-serverthe-radius-port-may-be-used-another-process - last commend may give you a hint.

Cheers,

Pawel Lakomski

Well yes, I did check. There are two folders 13 and 25 which have paths shown to the Symantec program. But the article you refer to just says check them. What has to be done with them? I would need an idea that these are relevant if they need changing or deleting!

Try this to change the Radius Port for SEPM

http://www.symantec.com/business/support/index?page=content&id=TECH102909&locale=en_US

Basically, the error relates to port conflict. You may need to change port used by your radius server.

Thanks. That's all very well but how do I go about deciding which port to use? A choice could clash with something else on the system. Why does Symantec choose a port which causes errors?

Use netstat command to see if for example port 1813 and change to this one.

Only ports 0-1023 are well-known ports and cannot be used for other services.

How do I know a Radius server is running? I have not added one.

Is there any other application that uses port 1812? You can cyheck it with netstat command.

Normally we change it to 1813

You can leave your application using 1812 as it is whether it is Remote Authentication Dial-In User Service (RADIUS) or any thing else

TO check if the port is free on the command prompt run command netstat -ab >a.txt  [export it to a text file ]

Then check if the port is free or in use.