Session request failed (Called name not present) error

[Robert Dahlem]

Jason,

On Mon, 11 Dec 2000 16:37:31 -0800, Jason Hill wrote:

I'm coming back on this: I get no peace without solving this. :-)

>I'm running Solaris 2.7 with Samba 2.0.7 and I receive the following 
>message when I try to use ./smbclient -L lonepeak.
>
>session request to LONEPEAK failed (Called name not present)
>session request to *SMBSERVER failed (Called name not present)

I had a little stroll through the sources looking out for the code 
returning "called name not present". To my surprise it did not find 
_anything_ looking like this!

I have a private network here with 3 PCs

192.168.1.1		radio		Linux	+ Samba 2.0.7
192.168.1.2		station	NT4/SP6
192.168.1.3		zocker	Linux + Samba 2.0.7 (master browser)

Now lets hack some commands into "radio"

Checking against NT:
  smbclient -L STATION -I 192.168.1.2 -U%
    ERROR: complains about "access denied"
  smbclient -L STATION -U 192.168.1.2 -Uuser%password
    OK: returns share list
  smbclient -L '*SMBSERVER' -U 192.168.1.2 -Uuser%password
    OK: returns share list
  smbclient -L XXXXXXX -U 192.168.1.2 -Uuser%password
    PARTLY IN ERROR: complains about "Called name not present"
                     then returns share list
                     while answering as '*SMBSERVER'
                     ( I have evidence for this from
                       tcpdump analysis )

Checking against Samba:
  smbclient -L ZOCKER -I 192.168.1.3 -U%
    OK: returns share and browse list
  smbclient -L ZOCKER -I 192.168.1.3 -Uuser%password
    OK: returns share and browse list
  smbclient -L '*SMBSERVER' -I 192.168.1.3 -Uuser%password  
    OK: returns share and browse list
  smbclient -L XXXXXX -I 192.168.1.3 -Uuser%password
    OK: returns share and browse list

What we learn from this is:

   Samba (2.0.7) never answers with "Called name not present" !!!

So if you do anything like 'smbclient -L HOST' while thinking HOST 
should be a Samba server and something answers you with "Called name 
not present", it is definitely not a Samba server. Your name 
resolution must be totally hosed. :-)

The (my?) problem with tcpdump is it does not sniff on loopback 
interfaces. Do you have a non-switched environment and a third 
machine? You could try:

   tcpdump -i <interface> -w <filename> -s 2000 \
      host <first_IP> or host <second_IP>

the redo the smbclient test and send me the file off-list?

Please first do a check with

  tcpdump -r <filename>

if the trace makes _any_ sense.

Regards,
        Robert


-- 
---------------------------------------------------------------
Robert.Dahlem at gmx.net           Fax +49-69-432647
---------------------------------------------------------------

Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email
software; far better than Outlook. Try it sometime.