After Installing the RMA's on machines and connecting them to my HostMonitor program they will work fine and I receive the correct response back. But on some machines when they restart they will not respond back, using netstat I can see the port is being used. The only work around I see is to either stop and restart the agent or change the port. Is there a fix for this problem?
Thanks
Jason
RMA's Not working after Reboot
On some of the machines that have the agent (v1.07) installed there will be a problem with the agent on the computer that has just been reset. The port that the agent used before the computer was reset will still be in use and the agent will not be able to be contacted until you restart the agent manually on the server.
I have discovered this - primary - on Windows NT 4.x servers. RMA does not allways start correctly when installed as "service". On not updated W2K servers I have seen this issue as well... but I cant say if it persistent for all servers... it vary from "hardware-vendor". On our NT 4.x servers I have made a "service-program" who actually starts RMA manually (as application). I made an approach to Alex regarding this problem for long time ago.. but I have'nt been able to tell exactly what happens- and when.. so I is - in fact - tough for Alex to do anything about it. Anyway, I'we learned to live with this on NT 4.x servers... since they are sitting with one leg in the ground.Flagship wrote:On some of the machines that have the agent (v1.07) installed there will be a problem with the agent on the computer that has just been reset. The port that the agent used before the computer was reset will still be in use and the agent will not be able to be contacted until you restart the agent manually on the server.
Cheers,
Hans Mosegaard
Continuing problems after reboot
We are still having issues after rebooting servers which are running the RMA 1.07. After the reboot with no apparent pattern we will lose connection to the RMA. The log2.txt reports that the port is probably in use. No configuration changes were made before the reboot. Typically we will have to user ram_cfg.exe to change the port that the agent uses, reconfigure the firewall as the servers are accessed over the internet and update the RMA manager with the new port.
Is there an overall solution for this. I becomes tedious checking host monitor to see if we have lost the connection after each reboot.
Is there an overall solution for this. I becomes tedious checking host monitor to see if we have lost the connection after each reboot.