Problems in networking between 7.04 host and win2k guest OS in vmware

Bug #96445 reported by reagle
6
Affects Status Importance Assigned to Milestone
vmware-player (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Problems in networking between 7.04 host and win2k guest OS in vmware

On a Dell Dimension e520 Core2 Duo e6400 2.2GHz with 2GB of RAM. When I am running Ubuntu Edgy I have no problems using networking in VMware. However, I did a clean install by disk of the Feisty Beta everything looked great except for this puzzling issue: The Win2K VMware guest was not able to connect with network services offered by the host (Ubuntu feisty). The Win2K virtual machine is configured to use bridge networking and can browse the Internet, and even ping the host but both Samba and SSH fail to connect. I can connect to my Ubuntu feisty host with those services from other Windows machines on the network. I tried this using the VMware player and kernel modules that come with feisty, as well as the tar ball of VMware server, neither worked.

Revision history for this message
reagle (joseph.reagle) wrote :

In Ubuntu forums, I see another example of this bug perhaps:
  http://www.ubuntuforums.org/showthread.php?p=2396111

Revision history for this message
reagle (joseph.reagle) wrote :

I'm going to close this. After doing an edgy upgrade, rather than fresh install, using the any-108 patch, making sure I don't enable post-only networking, and removing msdfs proxy from the Samba share configurations, I am able to map my network drives.

Revision history for this message
Marco Gaiarin (marcogaio) wrote :

Just upgraded fron edgy to feisty and the same things happen to me.

I confirm that i can ping from host to guest and back, but i cannot use from the guest, eg, putty to the ssh server of the host, nor browse the host samba shares from the guest.

I've tried to fiddle with netwprk parameters (forwarding, proxy_arp, ...) but nothing happen.

Please, help me.

Revision history for this message
Marco Gaiarin (marcogaio) wrote :

When i've installed dapper in this box the integrated NIC (realtec gigabit) was not supported.
So i've installed a second PCI NIC (again, a 100Mbit Realtec) and forgot all.

Today i've tried to remove the PCI NIC, re-enable in bios the integrated one, configure correctly it and... WORKS!

Reading around i've found another post that claim problem with the NIC (but if i remember well was a intel e1000), so i don't know if this is a driver or NIC problem, or something other.

Boh, i hope that someone can track down and fix this.

Thanks to all.

Revision history for this message
jhansonxi (jhansonxi) wrote :

I had similar issues with host-guest smb access. I was also having USB problems with a Lexmark X3350 that would only function on the initial driver install in Win98SE and WinXP but not after the guest was rebooted. Both issues were resolved by installing the 1.0.4 version of the player from the tarball on the VMware site. Due to a kernel compatibility problem in feisty, vmmon needs a fix in order to get it to build:
http://ubuntuforums.org/showpost.php?p=2127036
The down side is that this will need rebuilding after any kernel update.

Revision history for this message
oolon (magnus-zone) wrote :

It worked for me like this and maybe ya all know this by now :) My system is latest feisty with the classic problem of host <-> guest unable to do any sensible networking.

1) Uninstall vmplayer and delete /etc/vmware and /var/run/vmware

1) Download the latest vmplayer (version 2 when this was done) tar ball from vmware.com

2) Unpack in a suitable place

3) sudo apt-get install build-essential linux-headers-`uname -r` This will download the current header files

4) sudo ./vmware-install.pl I basically said yes to everything (autodetect worked nicely in the script)

5) Tried vmplayer in terminal as my user and pointed it to my gentoo image. It booted up nicely

6) ssh -l username ip-on-guest

Thats it

Looks like vmware have done a couple of fixes on vmmon, no haxing on header files were needed.

I used automatix for the vmplayer but dig this, I checked the version and it said vmplayer 1.02 which is way old. Any 2 cents on that?

Revision history for this message
Adam Niedling (krychek) wrote :

Feisty is not supported anymore.

Changed in vmware-player:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.