- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VMWare Player Can't Connect to VMWare Update Server
I just installed VMWare Player 4.0.2 onto a Windows 7 Pro 32bit Workstation. Next, I virtualized a Physical Machine running XP Media Center 32bit and copied the VM to the Windows 7 machine and opened the VM in the VMWare Player. It started up and is running. The only problem is that VMWare Tools could not be found for the XP Media Center guest VM, so it attempted to connect to VMWare to download the Tools. The problem is that it fails to connect to the server to check for updates. I have disabled the firewall, rebooted, verified that I am connected to the internet on the Windows 7 host machine, I can even get out to the internet from the XP VM guest. I am not connecting out through a proxy and I changed the Player preferences to 'No Proxy'. In network connections I see 3 adapters, the physical, and two virtual. Although both virtual show as unidentified it doesn't seem to affect the XP VM from gaining internet access. Which I'm a little confused about. Also, does the player get its network connection from the host's physical adapter or through the virtual adapters? I know the VMs get their network connections from the virtual adapters. Any Ideas on how I can get the player connecting to vmware's update servers?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the exact same problem with Windows 7 Ultimate guest OS. I think it is OS agnostic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue. I noticed that the VMware Player is apparently contacting this server: https://softwareupdate.vmware.com/cds and then only two links that appear, give "file not found" errors.
Does anyone know of a way to download the tools separately?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's seemed like each time they release a new version of the 4.x line, this happens for a couple of days. Try again in a day or so, and keep trying - the Tools will eventually be there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a result of this problem, I rolled back to the previous version. I'd be grateful if someone would post when this is (finally) addressed, so that I can upgrade again.
Thanks
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've the same behaviour after my further successfull update. I hope that that meaningless error gets away!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VMware certainly scrwed up something with this release.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VMware get so much write but incredibly this problem persist. It's so massively annoying. More then enough to make me look for other options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iss42 wrote:
VMware get so much write but incredibly this problem persist. It's so massively annoying. More then enough to make me look for other options.
I'm guessing this is an old cached post or something, as this issue was resolved months ago.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately not, 4.0.1 was exhibiting this behavior still.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iss42 wrote:
Unfortunately not, 4.0.1 was exhibiting this behavior still.
Well, I just installed Player 4.0.1 on a brand new Ubuntu 11.10 system, and it seems to connect to the update server fine. You're going to have to tell us more about what's going wrong.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could be a Windows problem, I have switched to 4.0.2 now and it connects ok.
I have experienced this problem though in many versions of VMWare Player before, all under Windows.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you browse to https://softwareupdate.vmware.com/cds/ with the trailing slash then the links will be resolved correctly, so perhaps the updater is using the incorrect URL. The reason this sometimes starts to work after a couple of days is probably that someone at VMware hacks the web server to handle the incorrect URLs. The update is not working for me at the moment (using a 4.0.4 build-744019 player on Windows 7 with Ubuntu 12.04 vm), so perhaps whoever usually fixes this is on vacation this week. ![]()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I browse to the link https://softwareupdate.vmware.com/cds/ I get:
Directories
- ../
- vmw-desktop
Files
- index.xml
Clicking on vmw-desktop I can work my way to:
https://softwareupdate.vmware.com/cds/vmw-desktop/player/5.0.1/894247/windows/packages/
- ../
Files
- metadata.xml.gz
- tools-freebsd-9.2.2.exe.tar
- tools-linux-9.2.2.exe.tar
- tools-netware-9.2.2.exe.tar
- tools-solaris-9.2.2.exe.tar
- tools-winPre2k-9.2.2.exe.tar
- tools-windows-9.2.2.exe.tar
are these the correct tools for running VMwarePlayer on Windows7
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For VMware Player 5.0.1 have a look at: Re: VMware Player 5 - Tools - "Cannot find component on update server..."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not the solution to the issue. There is a problem with the VMWare update server. If you open a web browser and put in the URL, it looks like works fine. Click vmw-desktop for example, it takes you to https://softwareupdate.vmware.com/vmw-desktop Which does not exist. I noticed if you manually put in the link for the next folder (https://softwareupdate.vmware.com/cds/vmw-desktop), you get there fine. It happens in each lower folder, not just from https://softwareupdate.vmware.com/cds. It is as if the links take you to ../vmw-desktop instead of ./vmw-desktop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DTGreen wrote:
This is not the solution to the issue. There is a problem with the VMWare update server. If you open a web browser and put in the URL, it looks like works fine. Click vmw-desktop for example, it takes you to https://softwareupdate.vmware.com/vmw-desktop Which does not exist. I noticed if you manually put in the link for the next folder (https://softwareupdate.vmware.com/cds/vmw-desktop), you get there fine. It happens in each lower folder, not just from https://softwareupdate.vmware.com/cds. It is as if the links take you to ../vmw-desktop instead of ./vmw-desktop.
You are replying directly to the reply I made:
Re: VMWare Player Can't Connect to VMWare Update Server
Your reply to me really has nothing whatsoever to do with my reply as my reply to DavidMays is meant only as a workaround until VMware gets things squared away with the current VMware Player 5.0.1 release!
Also the URL behavior you described is by design as VMware really doesn't what users walking through the update server in this manner and why I only provided version specific links for the VMware Tools ISO Images in the linked reply! ![]()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like someone saw my post. There is still one other issue. Player 5.0.1 info is missing from the player-windows.xml file. Get that in there and it might fix it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DTGreen wrote: There is still one other issue. Player 5.0.1 info is missing from the player-windows.xml file. Get that in there and it might fix it.
It appears to be there so it's probably something else. We'll just have to wait for VMware to fix whatever still needs it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, those are the same files so it seems I have the current stuff. I am trying to solve a directx9 error and I thought updating would fix it. I guess I will wait a little longer, longer, longer, longer ...... hummmmm.