Click to See Complete Forum and Search --> : smbclient error


eejit
02-03-2001, 03:07 AM
running "smbclient -L localhost"
generates this message:

doing parameter security = share
doing parameter printing = bsd
doing parameter printcap name = /etc/printcap
doing parameter load printers = yes
doing parameter wins support = yes
doing parameter encrypt passwords = yes
doing parameter hosts allow = 192.168.0. 127.
doing parameter hosts deny = all
pm_process() returned Yes
added interface ip=24.114.197.221 bcast=24.114.197.255 nmask=255.255.255.192
added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
Client started (version 2.0.6).
resolve_lmhosts: Attempting lmhosts lookup for name localhost<0x20>
Connecting to 127.0.0.1 at port 139
session request to LOCALHOST failed (Not listening for calling name)
resolve_lmhosts: Attempting lmhosts lookup for name localhost<0x20>
Connecting to 127.0.0.1 at port 139
session request to *SMBSERVER failed (Not listening for calling name)

this is on a Mandrake 7.1 workstation/router on a w2k network.

everything else so far is working, the machines are mutually visible and share with no problems.

haven't figured out IPMASQ yet to get the LAN on the Internet; is the above going to interfere with that?

shaggy112
02-03-2001, 07:10 PM
try running 'smbclient -L 127.0.0.1'
if that works, it means that localahost is not defined in /etc/hosts.
if it doesn't work...post back.

Ryeker
02-03-2001, 07:11 PM
Is Samba running (smbd and nmbd)?

eejit
02-04-2001, 02:14 PM
"smbclient -L 127.0.0.1"

produces the same result. And yes, smbd and nmbd are running fine.

so is IP Forwarding now. This doesn't have any effect that I can see,, but error messages like this are diquieting, so I'd like to figure it out.

hndpaul
02-04-2001, 04:49 PM
Hi there!

Try and have a look for an /etc/resolv.conf file. If there is one, you're using DNS. Also check for NIS services being switched on etc. Basically, Windows hosts use WINS and LMHOSTS first to resolve names/IP addresses, then broadcast and finally DNS and hosts files. NT looks at WINS, then broadcast, LMHOSTS (I think) and hosts then DNS. Windows programs using WINSOCK use hosts files, DNS and WINS.

SAMBA deamons will use LMHOSTS, WINS, the Unix host's preference then broadcast. generally I configure client machines to use WINS and DNS, the SAMBA daemons to use WINS and DNS and the server to use DNS.

I think you need to look at the above areas to find out why you are having a resolution problem. Try:

smbclient -L <server> -R wins

If you want to troubleshoot WINS. Also, run:

nslookup <machine's name without brackets>

Then:

nmblookup -S <machine's name> using this to look whether broadcasts are being dealt with adequately.

Look at the Windows machines and see if their c:\windows\hosts files exists and contains an IP number and one or more names for each machine. Look at you c:\windows\lmhosts file.

In conclusion, I think looking at combinations of the above if this bugs you that much and thinking along those lines should help narrow down the problem. Since its your localhost that's the apparent fiend, work on that. Ask questions like: have I got the right names; are the NETBIOS names the same; can I list shares on the localhost etc etc.

Hope that helps a little :confused: :confused:

Paul, UK