[Samba] Can't Connect to Swat

[Anthony Abby]

On Tue, 2002-08-13 at 21:14, Joel Hammer wrote:
> Well, that pretty much proves that xinetd is listening on the appropriate
> port.
> What precisely is the error your are getting? Just saying you can't connect
> isn't very much information to work with.
> 
> When I telnet localserver 901, I get the escape message and then a total
> hang, and have to kill the xterm window. What do you get when you try it?
> 
> Do you have nmap? Just run nmap localhost.
> 
> BTW, does local host resolve to your computer? Have you tried its ip number
> instead? Can you ping localhost? That should be in your /etc/hosts file.
> 
> Joel

I get the following error whether I attempt to access swat via
http://localhost:901, http://127.0.0.1:901 or http://192.168.1.100:901


An error occured while loading http://127.0.0.1:901:
Connection to host 127.0.0.1 is broken

This is all on Redhat 7.3, running KDE 3.0.2 and using Konquerer not
that I think that matters much.  I've looked over my configs and they
appear to be correct which is why I wrote in to the list. My last email
with the syslog messages pertaining to swat also apply here.... just
very weird but obviously I'm missing something and no idea what it might
be.  This SHOULD work.

Anyway if I nmap localhost I get the following:

Starting nmap V. 2.99RC1 ( www.insecure.org/nmap/ )
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1594 ports scanned but not shown below are in state: closed)
Port       State       Service
67/tcp     filtered    dhcpserver
111/tcp    filtered    sunrpc
137/tcp    filtered    netbios-ns
138/tcp    filtered    netbios-dgm
139/tcp    filtered    netbios-ssn
901/tcp    open        samba-swat
6000/tcp   filtered    X11

Nmap run completed -- 1 IP address (1 host up) scanned in 7 seconds


so yes swat appears to be listening.... or xinetd appears to be letting
swat listen, but I still can not connect!!!

Anthony