RE: [SLE] SWAT

From: Greg Wallace (jgregw_at_acsalaska.net)
Date: 10/20/05

  • Next message: Kai Ponte: "Re: [SLE] 'New' KDE file navigation Dialog"
    To: <suse-linux-e@suse.com>
    Date: Wed, 19 Oct 2005 19:48:03 -0800
    
    

    On Wednesday, October 19, 2005 @ 8:59 AM, Stan Glasoe wrote:

    >On Wednesday 19 October 2005 1:58 am, Greg Wallace wrote:
    >> I had this working in an earlier version (8.1) of SuSE, so I thought I'd
    >> look at mine and see if I could see anything. Turns out upgrading to
    >> 10.0 has apparently trashed it. Now, when I enter http://linux:901/ or
    >> https://linux:901 I get the old Cannot find server message. Looks like
    >> the upgrade trashed it. If I go to xinetd, it shows it running! Oh
    >> well, another problem to try to solve (it never ends!). Good luck on
    >> getting yours going. Sounds like your closer than I am.
    >>
    >> Greg Wallace

    >Couple of things to check. Instead of http://localhost:901 try both the
    name
    >of the system and/or its IP address; http://my-pc:901 or
    >http://192.168.0.2:901. If either of those work then we have something to
    >go on. At one time I thought you also had to go into YaST, System, System
    >Services (Runlevel ) to activate swat as well as activating it in xinetd.
    >But my SUSE 9.3 doesn't have that anymore. Hmmm, hope that's not
    >oldenheimer's disease...

    >I've also had this challenge when fresh installing newer SUSE releases.
    I've
    >also managed to disable the http://localhost:901 capability numerous times
    >via numerous methods when learning DNS, DHCP, etc. But then that's just me.

    >Stan

    Thanks for the suggestion, but that wasn't the problem. I did get it
    working, however. The trick was to edit /etc/xinetd.d/swat and comment
    out the following line --

    only_from = 127.0.0.1

    I got to this point after discovering a bunch of error messages pertaining
    to swat in /var/log/xinetd.log. In looking back, when I set it up in 8.1, I
    was running inetd, not xinetd. When I chose to switch to xinetd somewhere
    along the line, I suspect that's when this happened (?). After making this
    change, I just went into yast under xinetd and bounced swat to pick up the
    new settings. When I try connect now, I get the pop up asking for userid
    and password, where I enter root and the root password. Then, viola!, the
    familiar SWAT application is sitting there in front of me.

    Greg Wallace

    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Kai Ponte: "Re: [SLE] 'New' KDE file navigation Dialog"

    Relevant Pages

    • Re: vsftpd "500 Opps"
      ... I've been using lsof | fgrep ... ... Xinetd owns the port as I ... provided by SuSE and the man page doesnt list any options. ...
      (alt.os.linux.suse)
    • Re: vsftpd "500 Opps"
      ... |There are currently no options being provided to vsftpd in the xinetd file ... But SuSE has it set to run through ... YAST2 often doesnt allow ...
      (alt.os.linux.suse)
    • Re: Access to Samba SWAT service
      ... >> It seems like Samba SWAT service is not running. ... > That should get it working through xinetd. ... I would recommend getting used to the chkconfig/service tools, ...
      (Fedora)
    • Re: AW: [SLE] SWAT installation with Yast2 (SuSe 8.2) ?
      ... > not enough to just mess with the xinetd files if its not actually running. ... No swat still does not work. ... Impossible to connect to localhost (port 901). ... As far as I know the Suse firewall is not in place, ...
      (SuSE)
    • Re: AW: [SLE] SWAT installation with Yast2 (SuSe 8.2) ?
      ... /etc/xinetd.d/ as described in Google findings, ... By the way, in SuSe 8.2 this file is called samba instead of swat, but it ... There is a line smpnameres 901/tcp, ...
      (SuSE)