I am replying to my own initial post just as an update rather than
because I have found a solution. I got an email from someone last week
who had found this thread on our archives (nice!) who had the same issue
that was at the time unresolved. Subsequently his resolution was found
to be running
sudo ethtool -K eth0 sg off rx off tx off tso off
on the linux client and this has worked for a number of people. Some
have found it necessary to use without "tso off" where the full line
gave errors.
The following is a good description of the issue and of typical resolutions:
https://bugs.launchpad.net/ubuntu/+source/vmware-player/+bug/105697
In my case this was not a solution and neither has any other among the
solutions mentioned in the ubuntu and other forums. It appears to be a
common problem with k/ubuntu 7.04. I have reproduced the problem on a
work machine using the amd64 alternate disk. In both my cases I have
onboard gigabit ethernet adaptors, u
<https://bugs.launchpad.net/ubuntu/+source/vmware-player/+bug/105697>nfortunately
this is a show-stopper for me both at home and work. My next move at
work will be to disable the onboard ethernet adaptor and put in a card
as this has been a solution for some. I'd started that box with suse
10.2 (which I have found to be fine with vmware server) but it couldn't
find the ethernet adaptor so I went to kubuntu! Oh well, life's like
that sometimes . . . If that is unsuccessful will go back to suse -
despite it's very slow booting time - that machine is going to stay up
once running.
At home I'm now trying Mepis 6.5 which is defying my initial attempts to
run vmware server - but it is still day one for me and this distro. I
will persevere! My initial thoughts on Mepis are that it is nice, easy
to install, aside from amarok and vmware-server everything "just works"
although a number of the packages are quite dated. Suddenly I am
realising that I have become somewhat "bleeding edge" in my approach and
looking forward to seeing what works (and doesn't) in Gutsy Gibbon and
10.3, but that this has it's down side too...
Cheers,
Roger
Roger Searle wrote:
Hi, I can't figure this one out. I have a feisty box running vmware
server, and windows guest. Feisty has some samba shares set up via
webmin, and another (windows) box on the network can do all the
expected things with those shares.
Network is 192.168.1.0/24, each machine is using DHCP, addresses
coming from a linksys wag54g router that is also the default gateway
for each machine.
All machines can ping google, and other machines by ip address. The
windows machines can ping each other by host name, so a degree of
local name resolution is working. The thing that is NOT working is
that the windows vm guest can't resolve the host machine - it can't
ping it by hostname, returning "could not find host" (it CAN ping it
by ip address), so no surprise that it can't acces the samba shares
(where the "real" windows machine can). Strangely, the vm guest does
see the host machine name listed in the workgroup in "my network
places" yet clicking it returns "\\gemini is not accessible. you might
not have permission to use this network resource".
DNS server setting in the vm guest are always including the router's
ip address, and it is using a bridged network card in vmware.
Usernames and passwords are consistent across machines.
Can anyone suggest what I can look for?
Cheers,
Roger
