As part of my ongoing endeavour to get samba up and running in 9.3 I've now tried to get swat going..... hmmm, it doesn't work but I don't know why. Here's what I have tried already: opened up /etc/xinetd.d/swat and changed disabled = yes to disabled =no then I did the same with /etc/xinetd.d/services I tried this because the manual states that I should carry out these configurations on /etc/xinetd./samba and /etc/services However those last two particular files do not exist???? So, has the manual been printed incorrectly? Because I have followed the instructions to the letter. So, my next step after making those changes was to try logging into swat though Firefox with: http://localhost:901 Uh, uh...all I get with this is connection refused. Any ideas where I go from here? -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
----- Original Message -----
From: "Kevanf1"
So, my next step after making those changes was to try logging into swat though Firefox with:
Uh, uh...all I get with this is connection refused.
Any ideas where I go from here?
Yes, just insert a little 's' after the first 'p' in the url and all should be fine ; - ) https://localhost:901 YMMV with SWAT. I prefer to simple edit the /etc/samba/smb.conf file. And as always, just follow http://us2.samba.org/samba/docs/man/Samba3-ByExample/ -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
On Tuesday, October 18, 2005 @ 12:39 PM, Kevan Farmer wrote:
As part of my ongoing endeavour to get samba up and running in 9.3 I've now tried to get swat going..... hmmm, it doesn't work but I don't know why. Here's what I have tried already:
opened up /etc/xinetd.d/swat and changed disabled = yes to disabled =no
then I did the same with /etc/xinetd.d/services
I tried this because the manual states that I should carry out these configurations on /etc/xinetd./samba and /etc/services However those last two particular files do not exist???? So, has the manual been printed incorrectly? Because I have followed the instructions to the letter.
So, my next step after making those changes was to try logging into swat though Firefox with:
Uh, uh...all I get with this is connection refused.
Any ideas where I go from here?
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
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
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
participants (4)
-
david rankin -
Greg Wallace -
Kevanf1 -
Stan Glasoe