Loading ...« /n Software NetCmdlets | Main | Scotty McLeod »
VMware VIC 2.5 and Server 2.0 Beta 1
By Adam Bell | January 18, 2008
I’ve been using Server 2.0 B1 for a few weeks now, and it would appear that like everyone else I really don’t like the new VI Web Access.
I just find the interface very slow and hard work to use. As mentionend by Chrissy there is a VMware Infrastructure Client (2.5) that can be used instead of the Web UI.
Now ignoring the rather bizarre way required to acquire the 53mb client – which is included in the linux tarball and err, apparently not in the Windows package, I just can’t seem to get it to work – I am working in a test lab so I’m not using any AV, and I have the firewalls disabled on both of my Windows 2003 servers.
I’m able to connect via the Web UI, and all the other connectivity tests work fine:
- I can ping both servers from each other
- I can telnet from Server1 to the Host on port 8333
However, I always get the error message: “..could not establish the initial connection with server Server2. Details: The server took too long to respond”.
If anyone has any constructive ideas please feel free (really) to post a comment, or on my thread over on VMTN. ;)
- None Found
Topics: Virtualisation | 8 Comments »
January 19th, 2008 at 1:15 am
Hey Adam,
I believe that the port is on 902, at least it is on the Linux version. I hope it would be the same on Windows! Not sure how that will help, though..since the firewall is disabled on both. I’ve not run VMware Server 2 on Windows but the Web interface seems just as horrible as it is in Linux, eh?
Good luck!
January 19th, 2008 at 1:28 am
Just as an FYI, I just did a netstat and I’m connected to the VMWare server from my workstation on port 443 a few times and 902 once. When I loaded up https://myserver, it redirected me to /ui/ then said service unavailable. So perhaps VIC does use port 443 still.
April 14th, 2008 at 10:46 am
Hey,
it’s definitely the SSL port (e.g. 443) to connect to. Thanks to Chrissy!
September 6th, 2008 at 12:25 am
Is there any way to change and forward this port? Used to be able to in 1.0…….
September 15th, 2008 at 3:56 am
Hi R,
Tbh after the hassles that I had with Server 2.0 I switched to the 6.5 Workstation beta.
I’ve always preferred the Snapshot Manager available in workstation too, but Server is free, so it’s always handy to play with ….
Hope you found a solution to your problem!
Cheers,
Adam
October 6th, 2008 at 10:05 am
Hi Adam,
I found THE SOLUTION! :D
To connect with vic to vmware server 2.0 you need to add the :8333 to the hostname, so the magic is, for example, 192.168.1.10:8333 and the connection works.
Best regards,
Davide
October 22nd, 2008 at 10:55 pm
Alternatively, you can reconfigure VMware to use port 902 for remote administration with http on 80, https on 443.
Then you can use the VI Client without having to add a specific port.
March 25th, 2009 at 9:35 am
VMware Infrastructure Client could not establish initial connection with server “VC server” Details: The server could not interpret the communication from the client