session request to SERVER failed

[Ronald Cogen]

Hello out there,
I've installed a Linux/Windows network using an HP ML370 as the Linunx Server running SuSE Enterprise 8. File sharing and printing use Samba. I've installed Samba and checked most everything that can be checked according to the book 'Using Samba' (O'Reilly). However, I get the following message when troubleshooting SMBconnections:

# smbclient -L SERVER -U%
added interface ip .......
session request to SERVER failed (not listening for calling name)
SESSION REQUEST TO smbserver FAILED (not listening for calling name.

Also, on the client side I get the message that the path to the server can't be found. I've looked in all the places I could think of: ping, telnet, checking the deamons, etc., but I con't find the source of the problem. Can someone help me?

[Alexander Chuzhoy]

what happends if you try to connect to IP address instead of HOSTNAME?
Can you send us smb.conf file?

[Mobeen_1]

Ronald,
I think the best would be to eliminate name resolution issues before proceeding any further.

Can you please confirm if you can reach client-server or server-client using the IP address instead of the hostnames?

If the test above turns to be negative, then we can look at other areas. If you are able to reach using IP and cannot reach using hostnames, then i would suggest that you add entries for the hostnames in /etc/hosts

Let us know how it goes

rgds
Mobeen

rgds
Mobeen

[Ronald Cogen]

Well, I can communicate between the client and server using ping and telnet with the IP Address and the server and client name. What I cannot do is map to the share on the server. I agree, that the problem must be connected to the name resolution or something like that. But, I still don't know where to look. Unfortunately, I can't send a copy of the smb.conf file, as I am not at the site at the moment. However, it is a typical smb.conf put together with swat. Another thing is that I see in the smb.log file that the client is trying to access the server but is being denied access. I don't see anything special about the smbpasswd file that would adversly affect this.