Port Conflicts between PRTG Network Monitor and VMware vCenter

By admin, December 28, 2010 14:07

I didn’t know this could happen until last night. I restarted VMware vCenter server after installing Microsoft patches for Windows Serve 2008 R2. Then used vSphere client to connect to vCenter, suddenly it started to pop up with error, also found vCenter Server Service has stopped or crashed to be precious and error logs showed Event 1000 ID, luckily I found this is to do with vCenter port conflicts. I was also able to confirm this by another user’s post in VMware community who’s having the same port conflicting problem with PRTG and ESX 4.

As usual, my memory needs to rewind and back to the point where I installed PRTG Network Monitor 4 days ago, by trial and error, I stopped the PRTG Server and Probe Services, then I was able to restart vCenter server again and login with vSphere client. Finally, I was also able to restart PRTG server without any problem, PRTG somehow was able to bind itself dynamically to another port which vCenter couldn’t.

In additional, I did try to change the port for PRTG and its Probe services, but after restarting the server, somehow PRTG is still conflicting with vCenter’s port (I don’t know which port, but PRTG is using a range of ports above 23560)

The solution is quite simple but a bit troublesome, as it’s a matter of precedence, I just need to start vCenter Server service before starting the PRTG services MANUALLY every time after restarting the server.

If you know how to change the service start dependence or any proper way to solve this, please do let me know, as somehow I still couldn’t figure out the permanent solution for this port conflict problem, thanks!