On Wed, 2005-10-12 at 11:43 -0700, Ken Plumley wrote: > I recently installed centos 4.1 and I'm trying to get samba working on > it to serve windows boxes on a lan. I configured samba on the centos > server using the graphical samba server configuration tool, which is > similar to the samba setup on redhat 9 that I have successfully setup > in the past. I setup samba user names and passwords with the same user > names and passwords used on the win boxes. > > I'm not able to access any shared samba folders from win boxes on the > lan. I disabled the firewall on the centos server using the graphical > security level configuration tool but I still can't access the samba > shares. When I use a win box to connect to samba it will not complete > the connection. It acts like the firewall is still running. > > I disabled iptables on the centos server using the graphical services > configuration tool but I still can't access the samba shares. > > I can ping the centos server from linux and windows boxes on the lan. > The centos server can ping other machines on the lan and can access > the internet. > > When I try to telnet into the centos server from win and linux boxes > on the lan I get these messages: > > On linux boxes: > "Unable to connect to remote host: Connection refused" > > On win boxes: > “Connecting To 192.168.1.2...Could not open connection to the host, on > port 23. > No connection could be made because the target machine actively > refused it.” > > Can anyone tell me what I’m doing wrong or what I need to do to get > samba > working on centos? ---- netbios / smb doesn't use port 23, that's the port for telnet. Telnet server is by default (by design, by good practice not installed). If you want to telnet into netbios port, you would want to telnet to port 139 but recognize that windows/samba etc. expect things to be encrypted which is gonna add to the difficulty. telnet 192.168.1.2 139 SO the better thing to do is to try to connect... on the server, smbclient -L localhost -U USERNAME it will ask for the password (samba passwd) of the USERNAME then from another Linux box (I am gathering you have more than 1)... smbclient -L 192.168.1.2 -U USERNAME and from Windows machine you can then connect I would think... Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.