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'm logged in as root and i'm on KDE. I'm trying to use a web administration configuration thingy for Samba. In a book i'm reading, it tells me to point my browser to:
By any chance are you in a network with router that has a firewall enabled? if so.. forward the port 901 with NAT. (Network Address Translation). If not, then perhaps you are using you're distro's firewall that is activated, forward the port there.
In NAT just give you're internal ip. for example 192.168.2.14 or whatever ip you're internal has. And then just give the port.. When you look at the NAT page.. everything will probably become clear by itself
I'm not sure why you'd need to forward any ports to access something on your local host. It sounds like Samba didn't start properly.
Since you're using Slackware, is /etc/rc.d/rc.samba executable? If it is, can you try running /etc/rc.d/rc.samba start and see if that works? If you still can't access localhost:901 check the following files; /var/log/messages, /var/log/syslog and /var/log/samba/* for error messages.
When i downloaded PaW ( Portable web app ) smb and stuff worked perfectly, and when i forwarded the ports, only then it worked. But perhaps i should've asked him that, if his samba was working yes / no.
You can make the startup script executable with something like chmod 0750 /etc/rc.d/rc.samba and then start it with /etc/rc.d/rc.samba start - you'll also need to use /etc/rc.d/rc.samba restart after each saved change to the configuration file (/etc/samba/smb.conf?).
Port 901 is Samba/Swat. The service is started by (x)inetd when you attempt to connect to port 901.
Look in your xinetd.d directory for the swat file. Open it and change the line that probably says
disable = yes to disable = no. Restart inetd (or xinetd) and voila, you can connect.
Distribution: CentOS, Ubuntu, Mac OSX, Amazon AMI Linux
Posts: 43
Rep:
Quote:
Originally Posted by BSchindler
Port 901 is Samba/Swat. The service is started by (x)inetd when you attempt to connect to port 901.
Look in your xinetd.d directory for the swat file. Open it and change the line that probably says
disable = yes to disable = no. Restart inetd (or xinetd) and voila, you can connect.
I looked in my xinetd.d directory, but I didn't see the swat file?
Is there another location or possibly another name?
What is a swat file?
Sorry tuntsfah, it has been a while since I used Slackware -- soulestream is probably correct. Either way, the objective is to have inet (or xinetd) start the service when you attempt to connect to port 901.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.