Has anyone run into this problem with Samba?

ME dugan at passwall.com
Sat May 26 22:29:13 PDT 2001


If it is a problem with not being able to connect to your linux box
running samba, and you have 2 copies of samba installed, you *may* (read
likely) have 2 different "smb.conf" files on your system. If you can't or
don't want to uninstall the one that does not work, or just want to leave
them both on, you should verify which one is actually being run as your
wish, and then make sure the conf file you edit is for that copy. (Some
prepackaged samba distros come with samba hard-coded with a non-default
(samba-wise) location for smb.conf.

Make sure the authentication system required by your client (windows
bx) can authenticate with the same authentication configured on your linux
samba server.

(For example, if your windows NT workstation is part of a domain at work
with a PPTP or other "secure" connection, then it may not find your samba
server on linux, and even if it does find it may fail to authenticate -
depending upon the use of NT policies and enforcement of rules from the
DC.

If your NT box is not part of any windows NT domain, and you have never
install profiles or mods to profiles on your NT box, you should be able to
find your box in the network neighborhood or with the nnet use command.

On another tangent, it is possible to connect to a samba box by IP address
with windows 2000 and NT (Not 95, or 98 and probably not ME, but I can try
some other time.)

example net use for connecting a user authenticated share to a local
mapped drive from a windows NT / 2000 box:
(Use only if you can't find the server in the network neighborhood)

C:> net use z: \\10.10.10.10.\share /user:username

where 10.10.10.10 is the IP address, but do not forget to add the last
"." or else NT thinks it is a FQDN and tries a lookup via DNS and find
that the IP address does not have an IP address. (Thanks to Andru for
finding this one.)

You can also try setting things up with WINS, and/or lmhosts with the
#PRELOAD directive...

the /user allows you to connect to the samba server with a username other
than the one you are using on the NT box.

(Other readers please note the /user: directive and the IP address are
"features" of NT and 2000 not 95/98 and probably ME.)

Just some guesses as to the problem you were encountering with your
windows NT box and the samba server.

-ME

On Sat, 26 May 2001, Lincoln Peters wrote:
> I think I just figured it out.
> I tried running `netstat -an` (Thanks to ME for suggesting that I do that) 
> and piping its output to a file, then found that there was a program 
> listening on the SMB ports on my vmnet1 network.  Turns out that it was the 
> version of Samba that shipped with VMWare.  I shut it down, and now the 
> regular Samba works fine.
> 
> At this point, the only problems I'm having seem to be originating from my 
> Windows NT worsktation (that figures).  If I find evidence to the contrary, 
> and I can't figure out how to fix it, I'll be back.



More information about the talk mailing list