Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
04-02-2003, 02:04 PM
|
#1
|
Member
Registered: Mar 2003
Location: UK Darlington
Distribution: Fedora Freebsd Centos
Posts: 296
Rep:
|
Samba and swat
ok so I'm a newbie ,but I can't use SWAT on RedHat 8. I use the url http://127.0.0.1:901/ and get connection refused. I know Samba is running because Samba Server (localhost) is in Mygroup workgroup on my XP PC .Its probably simple but.....
Thanks in advance for any help
|
|
|
04-02-2003, 02:43 PM
|
#2
|
Moderator
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047
Rep:
|
Is swat enabled to run?
Run "ntsysv" from a prompt and make sure swat has a * beside it. The restart xinetd with "/etc/init.d/xinetd restart"
|
|
|
04-02-2003, 04:25 PM
|
#3
|
Member
Registered: Mar 2003
Location: UK Darlington
Distribution: Fedora Freebsd Centos
Posts: 296
Original Poster
Rep:
|
yeah done that swat is enabled to run!! still no luck..... thanks tho i'll keep trying
|
|
|
04-03-2003, 04:48 PM
|
#4
|
Member
Registered: Feb 2003
Location: The Attic. Nowhere near Texas.
Distribution: Gentoo, Kubuntu, formerly LFS, SuSE, and RedHat
Posts: 133
Rep:
|
SWAT should be enabled by default on xinetd, but you may have to add it to the services file: add a tcp line for swat on port 901. That might fix it...
|
|
|
04-03-2003, 04:51 PM
|
#5
|
Member
Registered: Feb 2003
Location: The Attic. Nowhere near Texas.
Distribution: Gentoo, Kubuntu, formerly LFS, SuSE, and RedHat
Posts: 133
Rep:
|
aha: the actual line is:
swat(tab)(tab)901/tcp(tab)#Samba Web Admin Tool
just replace the (tab) with a tab character and insert the line between the two services 901 is between.
|
|
|
04-03-2003, 11:05 PM
|
#6
|
LQ Newbie
Registered: Apr 2003
Location: Toronto, Ontario, Canada
Distribution: Red Hat
Posts: 29
Rep:
|
The firewall is always a good one to check in instances like this. if you are using ipchains type ipchains -L to see if you have any rules configured and ipchains -F to completely clear them out until your next reboot or until you reset them manually. If you're using iptables you can use the same commands. Don't worry about resetting them until you've tested to see if Swat connects.
Joe
|
|
|
04-04-2003, 03:28 AM
|
#7
|
Member
Registered: Mar 2003
Location: UK Darlington
Distribution: Fedora Freebsd Centos
Posts: 296
Original Poster
Rep:
|
Thanks I'll check my xinetd file and clear my firewall ,which I have noticed is set to high!? Might also need help to configure that as well!! Not good..... Thanks for the advice
|
|
|
04-04-2003, 12:27 PM
|
#8
|
Moderator
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047
Rep:
|
The current version of lokkit defaults back to high when it is run. I don't think it is a firewall problem because you are accessing the loopback. is the looback interface (lo) running?
Run "ifconfig" as root to see.
|
|
|
All times are GMT -5. The time now is 04:11 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|