Hello, everyone. I have been following the recent thread concerning a few peoples SAMBA/SWAT woes. I believe I have followed all the good advice so far, but all to no avail. So I am looking for further suggestions. My problem is that when I try to connect to SWAT using localhost:901, servername:901, 127.0.0.1:901, root:password@servername:901 etc I get an error as follows: Netscape 4.7 - URL http://127.0.0.1:901 Error - Netscape's network connection was refused by the server 127.0.0.1. The server may not be accepting connections or may be busy. Try connecting again later. URL http://servername:901 Error - Netscape redirects to Google URL http://localhost:901 Error - Netscape redirects to Google KFM - URL http://127.0.0.1:901 Error - Could not connect to http://127.0.0.1:901 URL http://servername:901 Error - Could not connect to http://servername:901 URL http://localhost:901 Error - Could not connect to http://localhost:901 IE5 on NTW4 (Puts on fireproof undies...) URL http://127.0.0.1:901 Error - N/A URL http://servername:901 Error - The page cannot be displayed URL http://localhost:901 Error - N/A Sorry if this is getting long, I am trying to be thorough. Here is the setup: SuSE6.3 Stock SMP Kernel (I'm not yet brave enough to roll my own) SAMBA 2.0.6-16 (just updated tonight from 2.0.6-7, but the problem existed before, too) Static IP Address in the 192.168.x.y range What I've tried so far: SETDUMMYDEV=no in rc.config (tried it with and without quotes) Did the whole smbpasswd -a root Tried to put the root:password@localhost:901 into the URL Checked /etc/services, that's right Checked /etc/inetd.conf, that's right The workgroup name shows up from Network Neighbourhood in NT, so SAMBA itself appears to be working Stopped and started smb and inetd services to effect changes Rebooted machine to effect changes The freaky thing is that I set SWAT up on two other machines today, and they worked right off the bat, so I know this is supposed to work. The only difference I've found is that the two that work are on SAMBA 2.0.5. Having been testing it out all day, I know that if it is working, I should be presented with a login prompt. This does not come up. When I am trying it locally on the SuSE box, I am logged in as root to make sure I have all the rights to everything. If necessary, I can downgrade to Samba 2.0.5, but it strikes me that this should work. Hope you can help. Thanks, Stuart. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Did you actually enable swat by deleting the '#' in the startup line in inetd.conf ? Wihout it's running you'll not get far :) On Mon, 13 Mar 2000, Stuart Powell wrote:
Hello, everyone.
I have been following the recent thread concerning a few peoples SAMBA/SWAT woes. I believe I have followed all the good advice so far, but all to no avail. So I am looking for further suggestions.
My problem is that when I try to connect to SWAT using localhost:901, servername:901, 127.0.0.1:901, root:password@servername:901 etc I get an error as follows:
Netscape 4.7 - URL http://127.0.0.1:901 Error - Netscape's network connection was refused by the server 127.0.0.1. The server may not be accepting connections or may be busy. Try connecting again later. URL http://servername:901 Error - Netscape redirects to Google URL http://localhost:901 Error - Netscape redirects to Google
KFM - URL http://127.0.0.1:901 Error - Could not connect to http://127.0.0.1:901 URL http://servername:901 Error - Could not connect to http://servername:901 URL http://localhost:901 Error - Could not connect to http://localhost:901
IE5 on NTW4 (Puts on fireproof undies...) URL http://127.0.0.1:901 Error - N/A URL http://servername:901 Error - The page cannot be displayed URL http://localhost:901 Error - N/A
Sorry if this is getting long, I am trying to be thorough.
Here is the setup: SuSE6.3 Stock SMP Kernel (I'm not yet brave enough to roll my own) SAMBA 2.0.6-16 (just updated tonight from 2.0.6-7, but the problem existed before, too) Static IP Address in the 192.168.x.y range
What I've tried so far: SETDUMMYDEV=no in rc.config (tried it with and without quotes) Did the whole smbpasswd -a root Tried to put the root:password@localhost:901 into the URL Checked /etc/services, that's right Checked /etc/inetd.conf, that's right The workgroup name shows up from Network Neighbourhood in NT, so SAMBA itself appears to be working Stopped and started smb and inetd services to effect changes Rebooted machine to effect changes
The freaky thing is that I set SWAT up on two other machines today, and they worked right off the bat, so I know this is supposed to work. The only difference I've found is that the two that work are on SAMBA 2.0.5. Having been testing it out all day, I know that if it is working, I should be presented with a login prompt. This does not come up. When I am trying it locally on the SuSE box, I am logged in as root to make sure I have all the rights to everything.
If necessary, I can downgrade to Samba 2.0.5, but it strikes me that this should work.
Hope you can help. Thanks, Stuart.
-- This sig brought to you by SuSE 6.3 and sendmail. Linux - you know it makes sense. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Thanks, wulfie. At first, I was a bit upset at your suggestion, 'cos I'm not that new to this stuff that I would miss this, but you did get me thinking. inetd.conf was set up just fine, as per the docs, but it took me all day to realise that I had installed xinetd, and had disabled inetd. So it didn't matter how much I messed with inetd.conf, it was never going to work. So, I removed xinetd, and switched on inetd just to stick with the standard. And it all works great now. I knew it would turn out to be my own stupid fault. Well, you live and learn. Thanks to everyone who sent suggestions. Bye for now, Stuart. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi.
At 21:38 on 13 Mar 00, Stuart Powell begun to yabber about "[SLE] SAMBA and SWAT"
Send reply to:
I have been following the recent thread concerning a few peoples SAMBA/SWAT woes. I believe I have followed all the good advice so far, but all to no avail. So I am looking for further suggestions.
In SuSE Linux (as far as i know) SWAT does not run by default.. You will have to enable it (inetd or daemon, not sure, i don't use it).. Also make sure that your firewall or hosts.deny files allow the port to be used. Cya Matthew Matthew King: Network Engineer, Cable & Wireless Optus. My ICQ#: 2342475 Message me! Cellular Phone: +61 404 898544 040 489 8544 (Inside .au) Home e-mail: nerd@zip.com.au Work e-mail: Matthew.King@cwo.net.au Homepage: http://www.zip.com.au/~nerd/ -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s: a--- C++++ UL++++ P+ L+++ E---- W++ N++ o++ K w O- M- V- PS+ PE Y+ PGP- t+ 5++++ X++ R+ tv++ b+++ DI+++++ D++ G+++ e* h* r++ y+ ------END GEEK CODE BLOCK------ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
nerd＠zip.com.au -
stuart＠yorkshirepudding.com -
wulfie＠wulfric7.co.uk