Hi all,
I'm running VMWare Server 2.0.2 under Windows 2008 Server R2. The host server is presenting some file shares via CIFS (fallback to SMB).
I am attempting to create a guest which can access file shares on the host machine.
I have done this successfully with a Windows XP guest with the following configuration:-
Ethernet Interface 1 - VMNet Bridged - 192.168.10.xx/24 - gw 192.168.10.1 (NAT Router)
Ethernet Interface 2 - VMNet Host-Only - 192.168.81.xx/24 (Host is .1)
This XP guest can access the 10-space network fine and get out to the internet. It also has mapped drives to the Host IP on the 81-space. Performance is fine, almost running at gigabit line speed (or so taskmgr pretends) when copying files via cifs from the host to the guest.
Now, i'm trying to create an equivalent guest using *BSD. So far I have tried OpenBSD 4.8 with Sharity 3 (for CIFS client support) and FreeBSD 8.1-Release (using mount_smbfs). Guests are configured as per the XP VM with two network interfaces, one being vm-bridged, one vm-hostonly.
All networks are accessible from the guests and the relevant smb/cifs client is able to mount the shares on the host. The issue comes when a file copy is initiated. Speed, or lack of, seems to be around 25KB/sec. Upon checking network adapter usage on the host, the vmnet1 (host-only) adapter is barely used but I do see a very slight trickle of traffic on the main 10-space network adapter (on the host, to confirm).
I'm wondering if something is going wrong on these unix guests and SMB traffic is ending up going via the wrong interface. I've not done a packet trace yet to find out exactly what's going on but I will do as a last resort. Perhaps something like the initial handshake happens over the correct target IP but then something changes and the remainder goes via the wrong interface on the guest.
Is this is a common issue? Can I provide you folks with some outputs to help with resolving this issue?
Much appreciative of your help in advance 
Regards