Re: [Samba] no route to host
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 pgpHFvxY4Crfi.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] no route to host
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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 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. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] no route to host between Mac samba and Linux samba
[EMAIL PROTECTED] writes: >I have a mac running Mac OS X ans samba 2.2.5 which is provided by >Apple. The Linux server have samba 2.2.8 (the last one). Sometimes, in >the server logs, you have: >[2003/03/26 14:26:30, 0] lib/util_sock.c:read_data(436) > read_data: read failure for 4. Error = No route to host >in this case, the Macclient lost the samba connection and has to reboot >because a silly error (Mac error: -47, % macerror -47 >Mac OS error -47 (fBsyErr): File is busy (delete) ) >I don't understand the no route to host message because the error occurs >only once (or 2 times) per day >the problem occurs even if netatalk (appletalk) is not running >some suggestions ? > >-- >Jean-Max Reymond >derniËre Èruption de l'Etna: http://jmreymond.free.fr/Etna2002 Apple machines work way better on a half duplex connection, it must be forced on the switch and then the machine will accept it, or you can get a util from versiontracker called "cocktail" it will let you set the mode of the en* controller. do you have the lastest software updates on? I think this is a more mac side error than a samba prob. perhaps we should look into getting a apple-samba list going. god knows it could have helped me a while ago. Mac's are getting better, open source may save them. they have to find a way to update better though. good luck, I hope that kinda helps. Kyle Loree Rendek Communications [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] no route to host between Mac samba and Linux samba
I have a mac running Mac OS X ans samba 2.2.5 which is provided by Apple. The Linux server have samba 2.2.8 (the last one). Sometimes, in the server logs, you have: [2003/03/26 14:26:30, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = No route to host in this case, the Macclient lost the samba connection and has to reboot because a silly error (Mac error: -47, % macerror -47 Mac OS error -47 (fBsyErr): File is busy (delete) ) I don't understand the no route to host message because the error occurs only once (or 2 times) per day the problem occurs even if netatalk (appletalk) is not running some suggestions ? -- Jean-Max Reymond dernière éruption de l'Etna: http://jmreymond.free.fr/Etna2002 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
