Re: NT4 in VMWare VM can't see Samba over network - Yes, PlainTextPassword set :)
Pending further investigation, we now allege that Robin Collins wrote:
> Not really a Debian issue but maybe someone can help me out here.
> There are two computers here, for the sake of discussion called A and B. B
> runs Samba 2.0.7a on Potato. A is multi-boot.
> When booted to native NT4 SP6a with PlainTextPassword set A can see B and
> access B's shares perfectly.
> When booted to Linux, SMBCLIENT can see B's shares, use them and can also
> NFS mount them.
> BUT, when I run NT4 SP6a in a VMWare VM the VM can see the host, can see a
> Win98 system also on the network but can't see B nor map a share using NET
> VIEW: attempts fail with an error 53, name not found. Network Neighbourhood
> is also missing B, but the stange thing is that after a while (where "while"
> seems indeterminate!) B appears in Network Neighbourhood but it's shares
> cannot be seen.
> There are no errors logged by smbd or nmbd on B but the problem "feels" like
> some sort of name resolution problem; though clearly not DNS since the VM
> can ping B by name. PlainTextPassword is set since the VM can map drives
> from the host's Samba. SMBCLIENT on B can get to the VM's shares so B in
> able to "see" A's VM by name.
> I've installed many NT4/Samba systems in my time but I've never seen this,
> anyone any ideas?
Is the VM a host-only or bridged network?
Do you have WINS server support on B? If so, is the VM using it?
My first thought on hearing this is that your VM is a B-node running
on VMWare's virtual network, so it can't resolve NetBIOS names for
machines on the real network. If this is what's happening, you'll
either need to set up a WINS server somewhere (B would be ideal), or
you'll have to create a lmhosts on the VM. Also, if the VM has a
host-only network, you'll want to make sure its workgroup is different
btw, do you have any shares on A, and if so can the VM see them?