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 setup Samba and my smb.conf file on my linux machine (linux1). I have the service started and I can connect to the shares on my linux machine. When I try to connect from my Winodws machine, though, I get the following message:
No service is operating at the destination endpoint on the remote system.
I have tried to connect via windows mapping and the cmd prompt. I have entered the following at the cmd prompt:
here it is. It appears as though the port smb is running on is closed. How do you open?
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1595 ports scanned but not shown below are in state: closed)
Port State Service
22/tcp open ssh
25/tcp open smtp
111/tcp open sunrpc
139/tcp open netbios-ssn
901/tcp open samba-swat
6000/tcp open X11
I have actually found something. The firewall that RH configured automatiically at install was causing the problem. I turned that off and I do not get the error. Unfortunately, though, I not get the following message when I try to connect to any of my shares:
I have it working now. I had a bad smb.conf file in place that I had swapped in during troubleshooting. For anyone who is having the same problem, RH configures a firewall during install automatically. To disable it or reconfigure it run /usr/sbin/lokkit while logged in as root. I just disbaled mine b/c I already had a firewall on my router. I am now running smooth on SAMBA. Thanks mychi for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.