Click to See Complete Forum and Search --> : Problems with Swat in Woody?


cage47
01-08-2003, 08:08 PM
This is strange. I was sure it worked in my last woody install a few months back. But my swat is not working. When I open a terminal and type swat it doesn't start. The terminal sits there, the hard drive flashes twice and then nothing. I can close the terminal but swat never starts and it doesn't return to a command prompt. I have samba working by copying my smb.conf file from my mandy install that had swat working. I also brought up konqueror and tried http://localhost:901 but that didn't work either. Anyone else have a problem with swat in Woody? Are there any other ways to edit samba? (aside from text editor which is what I used a while back)

janet loves bill
01-08-2003, 09:58 PM
that's easy, don't use debian, or gentoo for that matter. use Caldera 3.1.1 workstation, whole lot simpler and easier.

st0rmrd
01-08-2003, 10:23 PM
sorry for asking but is inetd or xinetd working as it should to enable swat, do you have other services like swat (cups have a similar web-like interface)

try telnet-ing like this:

telnet localhost 901

and tell us what the result is...
it seems a little weird.

maybe your smb.conf is screwed up... can you find a "clean" copy and replace it, then modify from scratch? any errors when samba starts?

sharth
01-08-2003, 10:29 PM
nope nope nope.

man swat

Swat is not enabled by default. in man swat it will tell you to uncomment a line, and then all you have to do is point your browser to http://localhost:901

fretbrner
01-08-2003, 11:10 PM
I am having the same trouble with my redhat 8 box. I can't get swat to work. I looked at all the config files. created a swat file under /etc/xinetd.d/swat(like I read somewhere) and still nothing. I can see my samba server in the network neighborhood, so I am assuming smb is working fine. My suse 6.2 I can run swat with no problems.

i tried the telnet thing into the localhost and i get connection refused. I know telnet works cause I do most of the config from telnet.

So maybe someone can help two people out. I do not need to use samba, but am frustrated in getting it to work.

cage47
01-08-2003, 11:10 PM
OHOHOH. Sharth you might have it. That's for debian right?
Wierd. In Mandy swat was enabled right out of the box. I'll have to check that man file. Graci!

P.S. it said port 901 unavailable (or something similar, I'm at work so can't remember right now)

No the smb.conf file isn't screwed. First swat doesn't even work to fix it. Second it was stuck right from install without samba being set up. Third it is the working smb.conf file from my mandrake side (they are dual booted) and samba itself works and I have linneighborhood working. And I don't have telenet setup.

No another distro is not a solution. I already have mandy installed on another partition and samba IS working, i just want to have the option to change the conf file if needed, especially for when I get my printer re-inked it'll need to be configured. CUPS is already loaded and working and localhost:631 works. Already used it to setup my bjc-240. I just got my Debian 99% configured and don't wish to learn a new distro, since I am now settled on my preferences so lets not go there.

cage47
01-08-2003, 11:14 PM
to be honest fretbrnr, the first time I configured samba I just took the stock smb.conf file they give you and opened it in a text editor and hacked it to my liking until it worked. I didn't even touch swat until I installed Mandrake 8.2. So I spoiled myself. See if you can find the original smb.conf file and read down through it. It's long but worth the look over at the options. But check that swat man file idea. I'm gonna when I get home in a couple hours.

cage47
01-09-2003, 01:33 AM
Oh Boy, thank you sharth. Of course a Doh' on me for not ever checking the swat man file. Figured I had used it enough I wouldn't have needed to. Well did like it said and sure enough went to port 901 and bingo, there's swat. Only thing is in Mandy I could just open a terminal and type swat and it would come up in konqueror. Guess that's cause it needs to be configured. But it comes up when you type it in Konqueror now. So I'm back in business. Now my Debian install is 99% mirrored to my Mandrake install. Only diff is the kid misses xrally from Mandrake and my printer is setup just slightly different, but still works fine. Other than that everything is the same. Now to sort through this pile of old equipment I just got my hands on.