Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have three Redhat Linux machines on a 192.168.1.X network with the following names:
A - 6.2
B - 7.3
C - 7.3
All have static IP addresses and all have the same HOSTS file. The smb.conf files are also the same. There is nothing unusual about the hardware. Can ping by name from any machine to any other machine.
A & B can connect to each other and do everything you might expect. However, machine C is the one refusing connections from A & B. If I use the smbclient -L name command if works as expected between A & B in either direction. However A & B cannot connect to C. C however can connect to A & B OK. Am running as root on all machines and all have the same password.
Question - when A & B ask for a Password they will accept anything including blank. What is that about? Other random note - Security is set to share.
Try as I might I cannot find anything wrong with the configuration of machine C. B & C have 2.7.7 and A has 2.06. This is driving me nuts!!!
added interface ip=192.168.1.150 bcast=192.168.1.255 nmask=255.255.255.0
error connecting to 192.168.1.200:139 (Connection refused)
Error connecting to 192.168.1.200 (Connection refused)
Connection to flac failed
(flac is the name of machine C above)
I found a reference to IPTABLES and firewall rules somewhere and got all excited but knowing nothing about them was not surprised when the command
services iptables stop
did not do anything. Since machine C can connect to the outside world but nobody can get to it I thought the firewall thing might fix it , but alas it did not.
Did you do a testparm to see if the smb.conf file has no errors? Also set make sure that your local directory permmissions are set right. If your the directory permissions are not set to allow you to enter the directory you will get that error.
Thanks for the help and comments. Turns out that lokkit was running and not allowing samba connections. Once the firewall was turned off everything was fine.
I should have asked you if a firewall was running. I read where you stopped iptables and thought that you had already done it. Sorry and glad to hear that you got it working.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.