Login to participate
Endpoint Management & Virtualization BlogsRSS

ESX 3.0 Not Communicating with DS Server

phillipreid's picture
phillipreid
May 3rd, 2007
Filed under: , , , ,

If you're having issues with the Deployment Agent on a VMware ESX 3.0 server not being able to communicate with the Deployment Server, here's a fix.

In addtion to the lack of communication, look for log errors that look like the following:

Debug: Error:Connection refused, connecting socket 3 to host at <DS IPAddress> 402 ...
Warning: Error unable to connect to server

The problem is that you need to open port 402 so your server can communicate with the DS.

From a command prompt on the ESX server run the following commands.

esxcfg-firewall --openport 402,tcp,in,adlagent
esxcfg-firewall --openport 402,tcp,out,adlagent
esxcfg-firewall --openport 402,udp,out,adlagent
esxcfg-firewall --openport 402,udp,in,adlagent

Afterwards restart the adlagent (./adlagent restart) (found in the /etc/rc.d/init.d directory)

0 votes
riva11's picture
riva11
2 years 29 weeks ago

If can help, I have also a

If can help, I have also a suggestion from VMware also to open port 4300, see below :

esxcfg-firewall --openPort 4300,tcp,out,adlagentFileTransfer

Regards
PM

0 votes
gbromage's picture
gbromage
1 year 40 weeks ago

May not be 4300

For clarification, port 4300 is the default transfer port, but you should use whatever is set in your Deployment Console under Tools -> Options -> Global -> Client/Server file transfer port

0 votes