Greeting all,

I am currently running CentOS 4.2 and I know about enough to be fairly dangerous.

One of my main issues right now seems to be with my samba install.

Where I am we have a handfull of Linux and windows machines in a workgroup, and it work fine. The other day we connected a CentOS machine onto the network and tried adding it into the smbtree. When I am on this new server, ill call it RAIN, and I run smbtree I get no results, which tells me that it is not on the samba system. When I run smbclient -L rain i get a list of avaliable shares in the server. If I go to a server that works that is on the network, I'll call this one SNOW, and run the same commands, the listing in the smbtree for RAIN says:

\\RAIN Rain Samba Server
Error connecting to 192.168.1.21 (No route to host)
cli_full_connection: failed to connect to RAIN<20> (192.168.1.21)

My first thought was that there was an error on the network, but both servers can ping and ssh to each other fine.

I also observed that if I am sitting on RAIN and type smbclient -L snow I get the list of shares that SNOW has avaliable.

I also observed that when I am sitting at RAIN and run smbclient to a share that exists on SNOW, it asks for a password and then sends me to the smb : /> prompt, which I find odd because one way says theres no route to host and the other works fine.

I've check the iptables on both servers and there dosent seem to be anything that would be preventing there communication. I also ran testparm smb.conf on both servers to see if my configuration file had errors in it, but testparm didn't report any.

I checked the the fourms to see if anyone else had the same problem but couldnt find anything, but I could have missed a post somewhere. If anyone might happen to have a clue to why this is occuring or knows if a post with this similar problem is, I would muchly appericate it.

-Joseph

Hi,

And welcome to LQ.

I'd suggest having a good look at the smb.conf on the new machine. Check the
workgroup
hosts allow
interfaces
wins & dns settings

to begin with.


Cheers,
Tink

I looked over my smb.conf file a couple of times, made a few changes, restarted smb, and I am still having the same issue. I even tried copying a conf file from onr of the servers that works and make a few changes to reflect the new server, but that didnt work. Since I am uncertain about what else might need to be aded to the conf file, Ill just post it here.

[root@rain samba]# testparm smb.conf
Load smb config files from smb.conf
Processing section "[homes]"
Processing section "[printers]"
Processing section "[cmc ftp]"
Processing section "[samba_test]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

# Global parameters
[global]
workgroup = WORKGROUP
server string = Rain Samba Server
map to guest = Bad User
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
username map = /etc/samba/smbusers
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
preferred master = No
local master = No
domain master = No
dns proxy = No
hosts allow = 192.168.1., 127.
cups options = raw

[homes]
comment = Home Directories
read only = No
veto files = /.*/
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[cmc ftp]
comment = cmc ftp
path = /home/ftpusers/amis
guest ok = Yes
printable = Yes

[samba_test]
comment = samba test share
path = /samba_test
read only = No
guest ok = Yes

Hopefully this will be of some help.

-Joseph

I figured out my problem. Apparently the firewall was the problem was rejecting the requests....not sure why I didnt think of that sooner.

-Joseph