Day two of this issue.
Definaly sure it's something up with port 903.
Trying to narrow it down to our networks firewall (which I doubt) or something with ESX server.
I had a similar problem.
I shutdown the VI client and deleted this registry key, then it worked...
HKEY_CURRENT_USER\Software\VMware\Virtual Infrastructure Client\Preferences
Thanks for response!
Shut down the VI client and deleted the key from the system. Still same results though =(.
Very weird indeed.
Went as far as using esxcfg-firewall and opening an inbound tcp connection for port 903, as well as udp and tcp for outbound with 903 as well. But yeah didn't work either heh.
Pretty much ruled out everything in between the ESX server and this box remoting from the outside. Seems to be something with ESX, that just doesn't want to respond on 903 back to the remoting system.
I'm having the exact same problem. Is the computer you are connecting from and the server on a different subnet by any chance? My problem is more extended then that but started off that way, and just trying to narrow down to if it's a bug or something. I have a thread opened on my issue.
They are on different subnets.
When we try to use the client from the same subnet there is no problem.
It may be a bug, we have escalated it back to our VMWare engineer POC and he says they are having the same problem.
When we get a fix will post it here too in case they are the same thing and you are still having the problem too.
I am having this exact issue as well. I am going across subnets to our remote datacenter. All documented tcp and udp ports are open through the firewall. I have ESX servers in both locations, but I am trying to use the same VC Server to manage all of them.
Having the same issue here, anyone have any ideas/solutions? its extremely frustrating
Has anyone gotten any response back on an SR or any support whatsoever?
Here's one thing you could try:
- ssh to your ESX box
- add the following to /etc/vmware/config:
- try reconnecting
Hopefully that should allow you to work around the problem.
>- add the following to /etc/vmware/config:
This solved the problem for me. We connect over different subnets and the problem surfaced 3-4 days after the ESX 3 upgrade.
I tried this and it works. Nice suggestion. Where did u find that at? I didn't see it anywhere in the docs.
Yeah, I don't believe it's documented anywhere.
And I know about it because I'm an engineer at VMware familiar with this area of the code.
Thanks again. If Virtual Center is designed to work across subnets, in an enterprise, there should probably be a portion of the documentation devoted to that type of setup. Who would I submit that suggestion to, and reference this thread?