smbclient works for localhost but not domain name

[Bill Bob]

Hi all,
Please take pity on a poor NT admin trying to free himself from having to
install Win2k/Exchange2k servers to replace our NT4 servers. I am trialing
Linux/Samba on behalf of the college that I support. Running RedHat 7.1 with
Samba 2.0.7 (that's what came on the cd). Hard coded IP's 192.168.0 private
subnet sharing a switch with 1 XPpro machine setup for workgroup. Questions
are as follows:

1. When I run smbclient -L localhost I get a nice list of sharenames, server
name and workgroup indicating that samba is indeed running and working.
Howerver if I run smbclient -L servername (linux1 in this case) I get the
following message:

session request to LINUX1 failed (not listening to calling name)
session request to *SMBSERVER failed (not listening to calling name)

Note: I can ping linux1 and it resolves and responds

2. I can use smbclient to conect to the shares on the XP machine no problems

Any thoughts

Regs

Julian Roath
Network Admin
Tabor College Victoria, Australia

[Robert]

Try smbclient '\\linux1\share name'
if you get a response : Server Time ..........
(all is working ok)
quit

Robert
*****************
"Bill Bob" <billb...@hotmail.com> wrote in message
news:3c7b41f7$0$6218$afc3...@news.optusnet.com.au...

[Bill Bob]

Same error message unfortunately. I have tried adding ' ' around the path as
well as specifying username and password a la smbclient -L '\\linux1\public'
and also used the -U username%password -W workgroup switches. I think there
may be something wrong in the basic setup of the network bindings. This is
my first attempt at linux networking. What questions should I be asking on a
network level, bearing in mind that a ping to linux1 resolves to the correct
IP 192.168.0.150

Many thanks

regs

Julian Roath
Network Admin
Tabor College Victoria, Australia

"Robert" <star.he...@virgin.net> wrote in message
news:ZxIe8.2895$Hg1.5...@news6-win.server.ntlworld.com...

[S C Rigler]

Do you have a line for "netbios name = LINUX1" in your
smb.conf? Also, what does "hostname" return on your
Linux machine?

-S

[Robert]

The fact that you can resolve localhost and get a response
shows that samba is working.
For samba not to be able to resolve linux1 shows that
it does not recognise the netbios name of linux1.
I assume that when you ping linux1 it is resolving to
192.168.0.150 and that it is a fixed ip not dhcp.
I also assume that linux1 is in your host file.
I also assume that linux1 is the samba workgroup
that appears in the network neighbourhood and that
you have tested with testparm to ensure that no sillies
are resident in your config file.
I also assume that public is a samba share that you have
rights to, and that it is declared in you config file.

I can send you a full test schedule if you do not see anything obvious
in the above.

Regards

Robert
**********************

"Bill Bob" <billb...@hotmail.com> wrote in message

news:3c7b7afa$0$6214$afc3...@news.optusnet.com.au...

[Bill Bob]

Thanks for the suggestions. From what I understood from the smb.conf man
page I thought that it would use the first part of my private domain name,
in this case linux1.roath.local, and the results of smbclient -L localhost
reported
SERVER Comment
-------------- -----------------
LINUX1 Samba Server

But I added netbios name = linux1 in the [Global] section anyway. Stopped
and started samba with no improvement. hostname returns linux1.roath.local
on my machine.

Thanks again for your thoughts

Regs

Jules

"S C Rigler" <st...@sluggo.win95sux2.com> wrote in message
news:slrna7n2lk...@sluggo.win95sux2.com...

[Robert]

As you have not published your smb.conf file I assume
the following.
You have a line in your global section which reads
allow hosts = ***.***.***.*** localhost
If the localhost is missing, SAMBA cannot connect to itself
and that is a requirement.

Robert

***************
"Bill Bob" <billb...@hotmail.com> wrote in message
news:3c7b41f7$0$6218$afc3...@news.optusnet.com.au...