check ur fwall ruleset and make sure the xinetd is running. restart it to be sure:

/sbin/service xinetd restart

Try becoming root and starting a browser from that terminal. This worked for me. Thereafter, I can use samba as a normal user or at least the one linked to the "guest" account.

Should be "can use swat as a normal"

Well, I've tried everything suggested and I'm still stuck. Convinced I'm missing something simple, but who knows?

I've checked with netstat -antp and it appears that swat is not listening on port 901, but I'm not sure what to do about it. All of the necessary files are configured properly according to your suggestions.

swat should present a login prompt.

if it's not I would say it's not running or it's not listening on the interface at port 901

it should be on the lo interface by default, so 127.0.0.1:901 should work. localhost:901 is supposed to work as well.

check your log files for errors as you try to connect.

I finally fixed the problem.

When I installed swat, I carefully followed the instructions to insert the following line into the inetd.conf file:

swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat

I incorrectly assumed that the same would be necessary in the xinetd.conf file. Once I removed this line, everything worked fine.

Thanks for your help...your suggestions helped point me in the right direction.

Yes, that is the old way of doing it.

Interestingly, there is still documentation out there that is incorrect. That's what led me astray.

It's one of the problems. Actually the information is still useful to some people, as they have a different system. A lot of things are relative to the newer versions of an app, but you just need to be careful with redhat and mandrake like distros. They have different ways of doing the initd and xinetd scripts than other distros like slackware's scripts.


I guess I should have said, that's the old redhat way.

It may be a little long after the last post, but what I found today may help 'those that come behind us'.

My problem was that http://localhost:901 was resolved into http://www.localhost.com and sent out to the web, rather than staying on my one and only left over RedHat box. A helpless and unsuccessful browser (Mozilla) was the result. As it turned out, during installion, RedHat 8.0 had put the following line in /etc/hosts:

Getting the localhost.localdomain out of there and putting localhost in its place solved this problem for me. Immediately after restarting Mozilla and entering http://localhost:901 I got prompted for a password. I guess that Mozilla just doesn't do multiple hostnames for one IP-address.

that's kind of strange, the .localdomain part of the name is the domainname. It should not normally cause a problem with mozilla. Maybe something in /etc/resolv.conf is causing a problem

I agree, it doesn't seem right, because this defeats the purpose of aliases entirely. Still, that single modification to /etc/hosts/ made all the difference. And it was just a normal /etc/hosts, 127.0.0.1 was the only line in there. That's why I suspect Mozilla to be the culprit here, because it didn't pick up the 'localhost' on that same line after 'localhost.localdomain'. Otherwise I wouldn't have a clue as to why Mozilla immediately resolved that to www.localhost.com rather than stay on my box. I haven't tried with other browsers (yet), but maybe that will give more insight. Or maybe there are people who did get this to work with Mozilla?

I have seen this before

127.0.0.1 localhost localhost.localdomain localhost

How about some "# service httpd start" ?
You thought of that one already? I overlooked it too... how's SWAT gonna show up in your browser if you forget about Apache and it ain't running?