Hello out there!
I've set up a Linux Network (SuSE Ent 8 Ed.) environment with several Win XP Pro Clients. After configuring Samba and The windows client I haven't been able to connect via Samba. I went through the 'Fault Tree' described in the O'Reilly 'Using Samba' book and can report the following results: I can successfully ping both from and to the client as well as the server. Telnet works on both sides. The smbd and nmbd daemons seem up and running....
However, with the command

# smbclient -L SERVER -U%

I get the error message

session request to SERVER failed (not listening to calling name)
SESSION REQUEST TO smbserver FAILED (not listening for calling name)

If I look at the smb log, I see:

# tail -f /var/log/samba/log.smbd

[2004/3/21 17:54,1 ¨smbd /process, c: process_smb (871)
connection denied from 192.168.5.21

The System log reveals the following:

# tail -f /var/log/messages

....server ippl:ICMP message type echo request form 192.168.5.21
microsoft connection request from 192.168.5.21
netbios-ssn connection request from 192.168.5.21

Frankly, I don't know what this means or whether this indicate a clue to the problem.

Last, but not least, when I try to connect from the client, I get the message that the server can not be accessed; the network path can not be found.

Does anybody have an idea of where the problem lies. Because, I can successfully ping and telnet I assume that the problem is with the Samba config. or maybe with the Windows client config. But, where should I look?
Thanks for any help whatsoever!
Ron

Your going to have to post your smb.conf file... I just got mine going last night FINALLY.. had a friend come over and lend a hand.. that and DNS server...

Anyways..
Jesse

Make sure you set the appropriate user and host to allow a SMB connection.
Did you modify your smbhosts, smbuser files? Add the UID via smbpasswd -a command?

And yes, configuring your DNS is a must too.


J