I've looked through the archives trying to find a solution to this problem. I found a handful of messages that reported this error, however, only one of them had a resolution. 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) According to the documentation and my "hornbill" book this is probably due to a NetBIOS problem, either nmbd isn't running (which it is) or it's not responding to requests. I built 2.0.7 from scratch with no problems, but for kicks I tried the binary as well as older versions of Samba, all of them report the same error. I can pass the first two tests from DIAGNOSIS.txt and the following tests pass in the fault tree: Troubleshooting Low-level IP Troubleshooting TCP Troubleshooting SMB connections through Testing locally with smbclient. I've installed and configured Samba many times in the past, and I've been using it steady for the past 2-3 years. I've never seen this error before and it's causing me major headaches. ;) Any help would be appreciated. BTW, here's my smb.conf [global] workgroup = tennorth security = share hosts allow = localhost, 127., lonepeak, 127.16.5 hosts deny = all [share] path = /tmp guest ok = yes read only = no
Robert Dahlem
2000-Dec-12 08:31 UTC
Session request failed (Called name not present) error
Jason, On Mon, 11 Dec 2000 16:37:31 -0800, Jason Hill wrote:>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)[...]>BTW, here's my smb.conf > >[global] > workgroup = tennorth > security = share > hosts allow = localhost, 127., lonepeak, 127.16.5 > hosts deny = all >You did not configure a netbios name for that machine. What is its hostname? Try "netbios name = LONEPEAK". What happens if you try "./smbclient -L lonepeak -I IP_address"? Regards, Robert -- --------------------------------------------------------------- Robert.Dahlem@gmx.net Fax +49-69-432647 --------------------------------------------------------------- Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email software; far better than Outlook. Try it sometime.
Robert, Thanks for the reply. I added netbios name = LONEPEAK and tried ./smbclient -L lonepeak -I 172.16.5.6 and I still get the session request failed message. Maybe a certain system patch breaks Samba? If I throw Samba on my Linux machine and configure w/a virtually identical smb.conf it works fine. I've never had this problem before... this one has me puzzled. Any other suggestions you might have would be greatly appreciated.>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)[...]>BTW, here's my smb.conf > >[global] > workgroup = tennorth > security = share > hosts allow = localhost, 127., lonepeak, 127.16.5 > hosts deny = all >
David McMullen
2000-Dec-12 16:13 UTC
Session request failed (Called name not present) error
I have this exact same problem with Solaris 2.7, and seemingly all versions of samba - I've tried 1.9.18p4, 2.0.7 and even 2.2.0alpha1 and get the exact same error. I had 2.0.7 running with the exact same smb.conf under Solaris 2.6 on another server with absolutely no problems. uname -a gives: SunOS chef 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-4 I think this is a Solaris 2.7 thing, as again I can install samba 2.0.7 with no issues on any of our Redhat 7 linux boxes. Dave -- David McMullen Enigma - "Facing the Future" T +44 (0) 116 238 8113 | F + 44 (0) 116 238 8112 M +44 (0) 7801 743 068 | www.TheEnigma.co.uk mailto:david.mcmullen@TheEnigma.co.uk> -----Original Message----- > From: Jason Hill [mailto:jhill@north.com] > Sent: 12 December 2000 16:05 > To: 'Robert Dahlem'; 'samba@lists.samba.org' > Subject: RE: Session request failed (Called name not present) error > > > Robert, > > Thanks for the reply. > > I added netbios name = LONEPEAK and tried ./smbclient -L lonepeak -I > 172.16.5.6 > and I still get the session request failed message. > > Maybe a certain system patch breaks Samba? If I throw Samba > on my Linux > machine and configure w/a virtually identical smb.conf it > works fine. I've > never had this problem before... this one has me puzzled. > > Any other suggestions you might have would be greatly appreciated. > > > >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) > > [...] > > >BTW, here's my smb.conf > > > >[global] > > workgroup = tennorth > > security = share > > hosts allow = localhost, 127., lonepeak, 127.16.5 > > hosts deny = all > > >
David McMullen
2000-Dec-12 16:36 UTC
Session request failed (Called name not present) error
> Must be a patch thing... I can't imaging EVERY 2.7 box out there is > incapable of running Samba. :) > > Not sure if this will help, but here's my list of installed patches. >how did you generate the patch list? Solaris is all rather new to me, so I only know the very basics - I come more from a WinNT / Linux background.> Maybe we can compare notes and figure out what's going on. >That would be good as I've been banging my head against this for about 2 months on and off now!> --- > SunOS lonepeak 5.7 Generic_106541-12 sun4u sparc SUNW,Ultra-250 >Well we are already on different releases then... you are 2 ahead of me. Regards, Dave
David, Must be a patch thing... I can't imaging EVERY 2.7 box out there is incapable of running Samba. :) Not sure if this will help, but here's my list of installed patches. Maybe we can compare notes and figure out what's going on. --- SunOS lonepeak 5.7 Generic_106541-12 sun4u sparc SUNW,Ultra-250 106147-04,106148-05,106327-05,106541-08,106541-12,106621-05,106627-03,106760 -01, 106793-03,106857-10,106879-01,106887-02,106917-01,106924-02,106925-02,106934 -03, 106936-01,106938-02,106940-01,106942-05,106944-02,106946-01,106948-01,106949 -01, 106950-07,106952-01,106960-01,106963-01,106978-09,106980-07,106980-13,106982 -01, 106985-01,106987-02,106999-01,107001-01,107003-03,107011-01,107014-01,107018 -01, 107022-04,107038-01,107044-01,107049-01,107058-01,107059-01,107063-01,107072 -01, 107074-01,107076-01,107078-18,107081-08,107094-04,107115-03,107127-02,107147 -05, 107148-04,107171-04,107178-01,107180-12,107185-01,107187-01,107200-08,107219 -02, 107226-07,107233-01,107248-01,107250-02,107259-01,107285-02,107293-01,107306 -01, 107316-01,107330-01,107332-02,107337-01,107351-01,107359-01,107401-01,107403 -01, 107430-01,107432-03,107437-03,107438-02,107441-01,107443-09,107448-01,107451 -02, 107453-01,107454-03,107456-01,107458-04,107459-01,107460-03,107462-01,107465 -02, 107469-03,107472-02,107473-02,107474-01,107475-01,107477-02,107499-02,107544 -03, 107546-02,107551-01,107555-01,107557-02,107584-01,107587-01,107589-03,107624 -01, 107648-09,107650-05,107652-05,107654-05,107656-05,107658-04,107680-01,107684 -01, 107688-01,107702-01,107709-03,107711-01,107716-04,107738-01,107744-01,107746 -03, 107792-01,107794-01,107796-01,107799-01,107807-01,107809-03,107813-01,107834 -02, 107836-01,107838-01,107841-01,107843-02,107853-01,107865-01,107881-10,107883 -04, 107885-05,107887-07,107893-02,107917-02,107919-01,107962-01,107972-01,108029 -02, 108068-03,108089-02,108127-01,108147-01,108148-01,108151-01,108158-01,108162 -01, 108168-01,108170-01,108175-01,108197-01,108203-01,108219-01,108221-01,108224 -01, 108244-01,108263-01,108285-01,108343-01,109104-04
Jerry, Thanks for the tip on using FQDN... no go. Same error message.
Sorry, that's a typo on my part when I typed it in the message. It's not in the smb.conf. I was changing that line on the Solaris machine as I was composing the message so I manually changed it in the message. It should read: hosts allow = localhost 127. lonepeak 172.16.5. I've since created a generic smb.conf that works on my Linux machine. When I copy it over to the Solaris box, I get the session request failed, so I know it's not a smb.conf problem. -----Original Message----- From: Gerald Carter [mailto:gcarter@valinux.com] Sent: Tuesday, December 12, 2000 9:43 AM To: Jason Hill Subject: Re: Session request failed (Called name not present) error Jason Hill wrote:> > >[global] > > workgroup = tennorth > > security = share > > hosts allow = localhost, 127., lonepeak, 127.16.5^^^^^^^^^ you a missing a trailing '.' here> > hosts deny = all > >-- ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
David McMullen
2000-Dec-13 09:01 UTC
Session request failed (Called name not present) error
I just tried that here on my problem server and I get:
root@chef:/usr/local/samba/bin:./nmblookup -U 192.168.1.200 -S '*'
querying * on 192.168.1.200
192.168.1.200 *<00>
Looking up status of 192.168.1.200
received 5 names
CHEF <00> - B <ACTIVE>
CHEF <03> - B <ACTIVE>
CHEF <20> - B <ACTIVE>
ENIGMA-NT <00> - <GROUP> B <ACTIVE>
ENIGMA-NT <1e> - <GROUP> B <ACTIVE>
num_good_sends=0 num_good_receives=0
does this look about right?
I am now back running a compiled source 2.0.7 version with an smb.conf taken
straight from a working linux box that I set up last night, changing only
the NETBIOS NAME entry as follows:
# Samba config file created using SWAT
# from 192.168.1.62 (192.168.1.62)
# Date: 2000/12/12 17:40:55
# Global parameters
[global]
workgroup = ENIGMA-NT
netbios name = CHEF
security = SHARE
password level = 8
wins server = 192.168.1.5
[tmp]
path = /tmp
writeable = Yes
guest ok = Yes
still get the Called name not present error....
Dave
--
David McMullen
Enigma - "Facing the Future"
T +44 (0) 116 238 8113 | F + 44 (0) 116 238 8112
M +44 (0) 7801 743 068 | www.TheEnigma.co.uk
mailto:david.mcmullen@TheEnigma.co.uk
> -----Original Message-----
> From: Robert Dahlem [mailto:Robert.Dahlem@gmx.net]
> Sent: 13 December 2000 02:16
> To: Jason Hill; samba@lists.samba.org
> Subject: RE: Session request failed (Called name not present) error
>
>
> Jason,
>
> On Tue, 12 Dec 2000 08:05:17 -0800, Jason Hill wrote:
>
> >I added netbios name = LONEPEAK and tried ./smbclient -L lonepeak -I
> >172.16.5.6 and I still get the session request failed message.
> >
> >Maybe a certain system patch breaks Samba?
>
> Nothing read about this yet. Did you restart smbd/nmbd after changing
> smb.conf?
>
> Now lets go and ask this machine who it thinks it is:
>
> nmblookup -U 172.16.5.6 -S '*'
>
> This should tell us which name it thinks it has: you are
> looking for a
> line with <00> and without <GROUP>.
>
> Regards,
> Robert
>
>
> --
> ---------------------------------------------------------------
> Robert.Dahlem@gmx.net Fax +49-69-432647
> ---------------------------------------------------------------
>
> Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email
> software; far better than Outlook. Try it sometime.
>
>
>
Robert,
Yes, I restarted smbd/nmbd after making the change.
Here's the output from
nmblookup -U 172.16.5.6 -S '*'
querying * on 172.16.5.6
172.16.5.6 *<00>
Looking up status of 172.16.5.6
received 5 names
LONEPEAK <00> - B <ACTIVE>
LONEPEAK <03> - B <ACTIVE>
LONEPEAK <20> - B <ACTIVE>
TENNORTH <00> - <GROUP> B <ACTIVE>
TENNORTH <1e> - <GROUP> B <ACTIVE>
num_good_sends=0 num_good_receives=0
I appreciate the help. I've gone through this previously in my debugging
effort. Everything looks ok according to my Samba book and the
documentation.
Robert Dahlem
2000-Dec-16 11:12 UTC
Session request failed (Called name not present) error
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@gmx.net Fax +49-69-432647 --------------------------------------------------------------- Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email software; far better than Outlook. Try it sometime.
Robert/David, Success! The problem was lanman (Solaris PC Net Link), which someone before me installed on this machine. It wasn't running, but apparently the software install mucks with something. I was digging around on lonepeak and came across a directory that looked something like: DOS---- That prompted me to check the groups file and I noticed a few related entries and the password file had some SLSxxxx stuff in it. I checked through the /opt directory and found a directory called lanman with an uninstall in sbin, so I ran the uninstall (which complained that lanman server was not running) but proceeded successfully. After that, I kill -HUP'd smbd/nmbd and smbclient now recognizes it. I can't say enough about the tireless effort that Robert (Dahlem) put forth. The virtual beer is on the way, but he'll have to grab the nearest Hefe Weissbier himself. ;-) Robert, thanks so much for your help. Maybe I can return the favor someday. This might be worth putting in an FAQ someplace... Session request failed is not generated from Samba (more likely lanman). If you get the message, see if lanman is installed. Jason.