Ubuntu
app-install-data-commercial package

vmware-server : guest can't access server and vis-versa

Bug #112702 reported by Simon Schmidig on 2007-05-05

This bug report is a duplicate of: Bug #105697: VMWare Player guest OS and Host Kubuntu cannot SSH into each other. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	app-install-data-commercial (Ubuntu)	New	Undecided	Unassigned

Bug Description

I had install the vmware-server (amd64/feisty) from the commercial source.
When I create guests with a brighten network interface, I can ping from the guest to the server or to a other host in the local network. I can also ping from the server to the guest ip.
But I can't access http://192.168.100.4 (server ip) form the guest. Windows XP guest can "see" the other hosts of the local network but not the samba share of the server. When I try on the server the samba command:
# simon@mail:~$ smbclient -L terminal
# protocol negotiation failed
But when I try the same command line from a other host in the local network get a access to the guest.
The server is also a Samba PDC server.

Revision history for this message

Wolfgang Glas (wglas) wrote on 2007-05-14:

A sniff from an unsuccessful connect to the server's webapp. Edit (6.5 KiB, application/octet-stream)

We are experiencing the same problem using an ubuntu 7.04 amd64 vmware-server (commercial source package) and a WinXP SP2 vmware guest. We're using bridged networking.

The vmware guest is able to establish TCP connection to any host in the world, except to the own vmware host.

The vmware host is running a tomcat5.5 with a deployed webapp, which may be correctly reached from all the clients in our subnet except fro m the vmware client .

Trying to access the web app from within the WinXP client results in TCP/IP retransmits and checksum errors according to the attched sniff from wireshark.

192.168.17.101 ... unbuntu server.
192.169.17.201 ... WinXP vmware client.

Nevertheless, the client may reach the server using 'ping 192.168.17.101' and vice versa, so the problem suspectedly is related to TCP connections and not to packet-based protocols like ICMP or UDP.

The same problem ocurrs for connects to samba running on the vmware host, thus making it impossible to share server directories from within the vmware client.

Revision history for this message

Christoph Lechleitner (lech) wrote on 2007-05-15:

I failed to reproduce the problem in a 32-bit environment (early Athlon 1.33 GHz).
I suppose the problem is restricted to 64-bit installations.

Revision history for this message

Wolfgang Glas (wglas) wrote on 2007-06-15:

Hi, is there any progress on this issue? Does anybody now, whether VMWare is aware of the Problem ?

Revision history for this message

d12fk (ninja++) wrote on 2007-07-05:

I had the same problem on a 32bit P4 HT architecture. Nothing I tried solved the problem for me. Disabling TSO as suggested in http://www.vmware.com/community/thread.jspa?threadID=78606&tstart=0 didn't do the job for me either as my Realtek NIC doesn't support it and disables it by default.

I got bridged networking to work when I followed the instruction here: http://www.howtoforge.com/ubuntu_feisty_fawn_vmware_server_howto
Maybe that's help for some of you.

Is there any estimation when/if the .deb will be updated?

Revision history for this message

lefty.crupps (eljefedelito) wrote on 2007-08-13:

I have this issue with either Linux or Windows guests on Linux host, Intel 32bit P4, running Feisty with VMWare Player 1.0.2; my bug was marked as a duplicate of this, but myne is certainly NOT with 64bit hardware.

There is a wish to upgrade the package to VMWare Player 2.x.x for Dapper LTS and for Gutsy, but latest search is that the old version is packaged for Gutsy (and I don't think we'll ever get new software for Dapper) :(