RM Ranger 8 Woes - Waiting for reply from Security Monitor

[DontCycloneMeBro]

Hi there.

 

Has anyone had the issue where RM Ranger 8 will stop a log in with the message "Ranger License Server did not respond"? It may happen if the user tries again but will eventually allow a log in if the user keeps trying. There doesn't really seem to be any correlation to the issue and it can happen on any PC. It's really causing some stress. Lets say we have 400 log on's at one time only 4/5 will have this happen to them and the rest will log in no problem.

 

First sign of the issue during log on:

http://i.imgur.com/yQO7tk5.png

 

Box which appears (user will be logged out):

http://i.imgur.com/7dKa3UY.png

 

Additional diagnostics:

http://i.imgur.com/WZd9iW1.png

 

I realise this is a complete stab in the dark but was just hoping to find others who have experienced the issue and what they did to resolve.

 

Thanks for your time!

[LeMarchand]

Used to get this. The best solution (though it may not be one you're allowed to use) is to remove Ranger.

 

Otherwise you could try the advice near the bottom of this page: Logon Problems since upgrade to v5.9 .

[JATSO]

Have this no end of time but with an much older version.

Check your windows firewall. Can you ping the server when logged in as administrator?

Check that the DNS server that ranger sits on is in the list of DNS servers given to the local machine, I only have 1 internal dns server you might have more.

Run Rangersetup and remove ranger from the pc and re-add the machine to the domain and then re-run rangersetup gets a bit annoying if you have lots of pc's displaying the message though.

Consider going vanilla and dump Ranger for GPOL

[fiza]

I got this a couple of times. Have you looked at the network cable? We found a couple of dodgy cables that had seen better days. Swapped these out and seems to have sorted it.

[SHimmer45]

iffy profile on the machine/ranger install.

we found that remote desktoping to the ranger server causes this exact issue, which is due to the server attempting to open LAN ranger twice and the lock files ect