Cannot connect to VM with 3.1.1 agent

[bmikosh]

While running the 3.1.1 agent install program I am pinging the virtual machine. As soon as the install is complete I am unable to ping or RDP to the view machine. Is this a known issue, is there a fix?

[mjsvirt]

Sometimes the agent reenables the windows firewall during install. Check to see that your FW is disabled.

Hope this helps.

Jason Silva

http://silvaecs.com

[bmikosh]

Firewall service is not running, thanks.

[mjsvirt]

Interesting..

Can you ping by IP?

Also here is a known issue:

Jason Silva

[ragazzi]

I'm facing exactely the same problem. Ping to VM works until the View Agent installer start the RDP configuration and the stops. Firewall Service is disabled.

Wether direct RDP sessions nor connection with View Client oder Web access works....

- Tried also with View Client 3.0.1 and it did not work.

- Checked Agent GPO settings and did not find any setting which could be used to solve the problem..

[lbourque]

Have you checked the error logs? Anything interesting in there that might help? Event viewer say anything?

Want make a difference in the future of VMware Products? Feature request your ideas ( )!

[ragazzi]

I think I've found the solution.

Windows Firewall startup type was set to "automatic" but the service status was "stopped". I changed the the startup type from automatic to disabled. After rebooting the VM it worked again.

[lbourque]

By default now, in 3.1.1, the agent will start the firewall service when installing and removing the agent. This is being reviewed as something to address in future versions (mostly because I get annoyed when teaching it and the silly thing turns on the firewall after it was previously disabled). 😛

Want make a difference in the future of VMware Products? Feature request your ideas ( )!

[bmikosh]

We have found a solution that works for us. It appears that each time we make a new snapshot with this 3.1.1 agent we are unable to connect(via RDP) or ping the machine until we reboot it after its creation. We have verified through the console that the firewall service is not running and disabled.

[bmikosh]

The problem was that we had disabled the firewall service.  The agent install starts the firewall service to make changes.  We solved the problem by allowing the service the run, but disabling the firewall from within the itself.  This allows the agent to make its changes without affecting the accessiblity.