samba - May 2006 - no route to host

Hello,

First of all sorry for my English.

I am experiencing with Samba and I have a problem.
I have an old server (OLD) with Red Hat 9 and Samba 2.2.7a that is working well.
Now I try to start up a new server (NEW) with Red Hat Enterprise 4 and
Samba 3.0.22.
If I try to connect from NEW to itself by using smbclient I got the
shared resources list correctly. If I try to connect to NEW from OLD,
always using smbclient, I receive the message:

added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.X.255 nmask=255.255.255.0
error connecting to YYY.YYY.YYY.YYY:139 (No route to host)
Error connecting to YYY.YYY.YYY.YYY (No route to host)
Connection to YYY.YYY.YYY.YYY failed

Supposing that XXX.XXX.XXX.XXX is the OLD server address and
YYY.YYY.YYY.YYY is the NEW server address.

I try to find in documentation and in other resources but I found nothing.
Could you help me.

Thank you.

Alessio Bandini wrote:
> Hello,
> 
> First of all sorry for my English.
> 
> I am experiencing with Samba and I have a problem.
> I have an old server (OLD) with Red Hat 9 and Samba 2.2.7a that is 
> working well.
> Now I try to start up a new server (NEW) with Red Hat Enterprise 4 and
> Samba 3.0.22.
> If I try to connect from NEW to itself by using smbclient I got the
> shared resources list correctly. If I try to connect to NEW from OLD,
> always using smbclient, I receive the message:
> 
> added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.X.255 nmask=255.255.255.0
> error connecting to YYY.YYY.YYY.YYY:139 (No route to host)
If you have a firewall on the new server that rejects access to
port 139, one would expect this behavior.

There should be a firewall setup program.  Make sure to allow access
to smb ports 137-138 and 445.

I've not used RH Enterprise 4, but Fedora, an offshoot, the rpm
is system-config-securitylevel and so is the command name to run
the program.
> Error connecting to YYY.YYY.YYY.YYY (No route to host)
> Connection to YYY.YYY.YYY.YYY failed
> 
> Supposing that XXX.XXX.XXX.XXX is the OLD server address and
> YYY.YYY.YYY.YYY is the NEW server address.
> 
> I try to find in documentation and in other resources but I found nothing.
> Could you help me.
> 
> Thank you.
Regards, Doug

You have a routing problem.
Have a look at /sbin/route and add the subnet NEW is in to the table.

Am Mittwoch, 17. Mai 2006 14:34 schrieb Alessio Bandini:
> error connecting to YYY.YYY.YYY.YYY:139 (No route to host)
> Error connecting to YYY.YYY.YYY.YYY (No route to host)
-- 
Dipl.-Ing. Sebastian Held
Universit?t Duisburg-Essen
Campus Duisburg
Fachbereich Ingenieurwissenschaften
Abteilung Elektrotechnik und Informationstechnik
Hochfrequenztechnik

Bismarckstra?e 81, Geb?ude BB 1117
Eingang Oststra?e 99
D - 47057  Duisburg
Tel.: +49 (203) 379-3285
Fax.: +49 (203) 379-5135
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20060517/80e71fda/attachment.bin