Hi I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet. As far as I understan the man pages I have edited /etc/services to contain the line swat 901/tcp and /etc/inetd.conf to swat stream tcp nowait.400 root /usr/local/bin/swat swat However when I start up the browser and enter the location http://localhost:901/ I get the error message that the requested URL/901/ was not found on this server. The command: grep swat /etc/services however gives me the answer swat 901/tcp If anyone can point me in the right direction I would be very grateful. The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is? I realise that these are very basic questions, but I dont know where else to look. thanks Paul -- 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/
On Fri, 10 Mar 2000, Paul Evans wrote:
Hi
I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet.
As far as I understan the man pages I have edited /etc/services to contain the line swat 901/tcp and /etc/inetd.conf to swat stream tcp nowait.400 root /usr/local/bin/swat swat
However when I start up the browser and enter the location http://localhost:901/ I get the error message that the requested URL/901/ was not found on this server. The command: grep swat /etc/services however gives me the answer swat 901/tcp
If anyone can point me in the right direction I would be very grateful.
The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
To find the pid type "ps ax" and look for the /usr/sbin/inetd entry. The # in the first col. is the pid. Doing a "kill -HUP pid" will re-start the process with the changes you made. Hope this helps. -- Bob F EMail FBob@wt.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- 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
I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet.
As far as I understan the man pages I have edited /etc/services to contain the line swat 901/tcp and /etc/inetd.conf to swat stream tcp nowait.400 root /usr/local/bin/swat swat
However when I start up the browser and enter the location http://localhost:901/ I get the error message that the requested URL/901/ was not found on this server. The command: grep swat /etc/services however gives me the answer swat 901/tcp
If anyone can point me in the right direction I would be very grateful.
The problem, or part of it, could be that I just do not understand what
Actually I think the problem may be that I hav'nt set up the INET services correctly. When I give the command /etc/rc.d/init.d/inetd restart I get the response: Shutting down INET services (inetd) done Starting INET services (inetd) failed In yast I answered yes to starting inetd, so I don't really know where the problem is. Paul -----Original Message----- From: BobF [mailto:FBob@wt.net] Sent: 11 March 2000 00:45 To: Paul Evans; Suse linux Subject: Re: [SLE] samba help On Fri, 10 Mar 2000, Paul Evans wrote: the
man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
To find the pid type "ps ax" and look for the /usr/sbin/inetd entry. The # in the first col. is the pid. Doing a "kill -HUP pid" will re-start the process with the changes you made. Hope this helps. -- Bob F EMail FBob@wt.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- 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/ -- 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/
Sometimes I ran into that problem also. So I would end up giving the command /etc/rc.d/inetd stop /etc/rc.d/inted start. Cheers, Wayne Paul Evans wrote:
Actually I think the problem may be that I hav'nt set up the INET services correctly. When I give the command /etc/rc.d/init.d/inetd restart I get the response: Shutting down INET services (inetd) done Starting INET services (inetd) failed
In yast I answered yes to starting inetd, so I don't really know where the problem is.
Paul
-----Original Message----- From: BobF [mailto:FBob@wt.net] Sent: 11 March 2000 00:45 To: Paul Evans; Suse linux Subject: Re: [SLE] samba help
Hi
I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet.
As far as I understan the man pages I have edited /etc/services to contain the line swat 901/tcp and /etc/inetd.conf to swat stream tcp nowait.400 root /usr/local/bin/swat swat
However when I start up the browser and enter the location http://localhost:901/ I get the error message that the requested URL/901/ was not found on this server. The command: grep swat /etc/services however gives me the answer swat 901/tcp
If anyone can point me in the right direction I would be very grateful.
The problem, or part of it, could be that I just do not understand what
On Fri, 10 Mar 2000, Paul Evans wrote: the
man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
To find the pid type "ps ax" and look for the /usr/sbin/inetd entry. The # in the first col. is the pid.
Doing a "kill -HUP pid" will re-start the process with the changes you made.
Hope this helps.
-- Bob F
EMail FBob@wt.net
A Truly Wise Man Never Plays Leapfrog With A Unicorn...
-- 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/
-- 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/
-- 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/
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu -- 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/
have you added any users to smbpasswd ? Initially try "smbpasswd -a root" then at least root will get into swat. On Sat, 11 Mar 2000, phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
-- 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/
Assuming you are trying to log onto SWAT with a Window Machine. If you did not edit the registry to enable clear text password then you have to do some work on the samba server to accept encrypted password. I think that is why you cannot log on to the samba. wulfie wrote:
have you added any users to smbpasswd ? Initially try "smbpasswd -a root" then at least root will get into swat. pt On Sat, 11 Mar 2000, phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
-- 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/
I am trying to log onto swat on the linux server. Using Netscape, the login box appears, but all I can get out of it is 'autherization required'. Then Netscape has its own complaint '401 Autherization required'. Wulfies suggestion 'smbpasswd -a root' accepted the new passwd ok but didnt help. Thanks for the attention. phillipp@w3eax.umd.edu -- 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/
I assumed you used root & the smbpasswd you assigned to root to login to swat ? On Sun, 12 Mar 2000, phillipp wrote:
I am trying to log onto swat on the linux server. Using Netscape, the login box appears, but all I can get out of it is 'autherization required'. Then Netscape has its own complaint '401 Autherization required'. Wulfies suggestion 'smbpasswd -a root' accepted the new passwd ok but didnt help. Thanks for the attention. phillipp@w3eax.umd.edu
-- 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/
Try using LYNX browser to confirm whether that the error comes from your samba config. PS. lynx localhost:901 (NO proxy settings) phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
-- 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/
-- 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/
On Mon, 13 Mar 2000, Wayne Chan wrote:
Try using LYNX browser to confirm whether that the error comes from your samba config.
PS. lynx localhost:901 (NO proxy settings)
Same deal here-'Username for "SWAT" at server 'Localhost:901'----After accepting root and passwd I get '401 Autherization required'.
phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
-- 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/
Okay, shall we have a look at your smb.conf file?
----- Original Message -----
From: phillipp
On Mon, 13 Mar 2000, Wayne Chan wrote:
Try using LYNX browser to confirm whether that the error comes from your samba config.
PS. lynx localhost:901 (NO proxy settings)
Same deal here-'Username for "SWAT" at server 'Localhost:901'----After accepting root and passwd I get '401 Autherization required'.
phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and
there
are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
-- 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/
On Sun, 12 Mar 2000, Wayne Chan wrote:
Okay, shall we have a look at your smb.conf file?
okay - But no snickering---I just plugs em in to see what works :-). [global] workgroup = WORKGROUP netbios name = WINDOW interfaces = 172.16.1.2/255.255.255.0 encrypt passwords = yes server string = My first server guest account = pcguest security = user password level = 6 null passwords = yes message command = sh -c '(echoWinPopup\ message\ from\ %f | cat %s) \ > /dev/console' & #message command = /bin/bash -c '/usr/X11R6/bin/xterm -T "WinPopup Message" \ # -e /usr/bin/vim %s; rm %s' & ; share name [inwood] ; text to list when browsing the share from a client comment = shared directory for group inwood ; absolute path to the disk directory path = /export/smb/inwood ; should the share be writeable? writeable = yes ; user allowed to connect to the share ; the '@' is used to designate a unix group valid users = @inwood ; enforce file locking? locking = yes ; default file creation permission mask create mode = 0660 ; default directory creation permission mask directory mode = 0770 ; share name [homes] comment = Unix home directory space path = %H writeable = yes valid users = %S create mode = 0600 directory mode = 0700 locking = no [tmp] comment = Temporary Read-only share path = /tmp writeable = no -- 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, have been trying to regenerate your error with no luck. Your smb.conf definitely looks okay. I was using samba-2.0.5a-26 but I've upgrade it to samba-2.0.6-16 to check whether I could get your error. No luck. Everything works here. SO.. let me suggest the following steps. 1. Stop all samba services. 2. Get samba-2.0.6-16.i38.rpm from suse ftp site. 3. Do a rpm -Uvh 4. Rename /etc/smb.conf to /etc/smb.conf.bak (NO smb.conf!) 5. Without starting any samba servcies, try logon to SWAT if it works, you can carry on and create the smb.conf thru SWAT and start the smb services. (PS. ensure you have pam.rpm from the a1 series installed) Good luck! phillipp wrote:
On Sun, 12 Mar 2000, Wayne Chan wrote:
Okay, shall we have a look at your smb.conf file?
okay - But no snickering---I just plugs em in to see what works :-). [global] workgroup = WORKGROUP netbios name = WINDOW interfaces = 172.16.1.2/255.255.255.0 encrypt passwords = yes server string = My first server guest account = pcguest security = user password level = 6 null passwords = yes message command = sh -c '(echoWinPopup\ message\ from\ %f | cat %s) \ > /dev/console' &
#message command = /bin/bash -c '/usr/X11R6/bin/xterm -T "WinPopup Message" \ # -e /usr/bin/vim %s; rm %s' & ; share name [inwood] ; text to list when browsing the share from a client comment = shared directory for group inwood ; absolute path to the disk directory path = /export/smb/inwood ; should the share be writeable? writeable = yes ; user allowed to connect to the share ; the '@' is used to designate a unix group valid users = @inwood ; enforce file locking? locking = yes ; default file creation permission mask create mode = 0660 ; default directory creation permission mask directory mode = 0770
; share name [homes] comment = Unix home directory space path = %H writeable = yes valid users = %S create mode = 0600 directory mode = 0700 locking = no
[tmp] comment = Temporary Read-only share path = /tmp writeable = no
-- 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/
On Mon, 13 Mar 2000, phillipp wrote:
On Mon, 13 Mar 2000, Wayne Chan wrote:
Try using LYNX browser to confirm whether that the error comes from your samba config.
PS. lynx localhost:901 (NO proxy settings)
Same deal here-'Username for "SWAT" at server 'Localhost:901'----After accepting root and passwd I get '401 Autherization required'.
phillipp wrote:
I dont have the problem currently under discussion, but when I try to log into swat with the log-in box----nada. DSoesnt accept roots or anyones passwd. smbpasswd file exists and there are no 'D's' in it. Thanks anyone for a suggestion. phillipp@w3eax.umd.edu
Did you try: http://root:password@localhost:901 Where root and password are your's? -- Bob F EMail FBob@wt.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- 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 try: http://root:password@localhost:901 Where root and password are your's?
yup- same result--401 autherization required. phillipp@w3eax.umd.edu> -- 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/
On Sat, 11 Mar 2000, Paul Evans wrote:
Actually I think the problem may be that I hav'nt set up the INET services correctly. When I give the command /etc/rc.d/init.d/inetd restart I get the response: Shutting down INET services (inetd) done Starting INET services (inetd) failed
In yast I answered yes to starting inetd, so I don't really know where the problem is.
OK- doing ps ax after the above- do you see inetd running with a pid? If is is not running there will be no pid or notataion of it in the list you get with ps ax. In my inetd .conf the only line uncommented is the swat line (so I am paranoid;-) Is there a pid for /usr/sbin/smbd in the output? This is the Samba daemon running.
The problem, or part of it, could be that I just do not understand what
snip the
man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
To find the pid type "ps ax" and look for the /usr/sbin/inetd entry. The # in the first col. is the pid.
Doing a "kill -HUP pid" will re-start the process with the changes you made.
Hope this helps.
Bob F EMail FBob@wt.net A Truly Wise Man Never Plays Leapfrog With A Unicorn... -- 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/
On 11 Mar, Paul Evans wrote:
Hi
I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet.
--snip--
The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
Try the command ps aux | grep inetd You will get one or two lines of which one looks something like this: root 172 0.0 0.4 1440 516 ? S 23:22 0:00 /usr/sbin/inetd ^^^ PID I have marked the Process ID that is 172 in this case. So if I wanted my inetd to reread the /etc/inetd.conf then I would give the command: kill -1 172 Good luck! TJo -- 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/
Tryggve Johannesson wrote:
On 11 Mar, Paul Evans wrote:
Hi
I have been trying to get the samba tool swat to run, but have run into a problem that I have no idea how to resolve. I have a linux and a windows machine connected via ethernet.
--snip--
The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
Try the command
ps aux | grep inetd
You will get one or two lines of which one looks something like this:
root 172 0.0 0.4 1440 516 ? S 23:22 0:00 /usr/sbin/inetd ^^^ PID
I have marked the Process ID that is 172 in this case. So if I wanted my inetd to reread the /etc/inetd.conf then I would give the command:
kill -1 172
Good luck!
TJo
I always do the simple thingy: killall -HUP inetd Why bother looking up the PID? Rogier -- 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/
On 11 Mar, Rogier Maas wrote:
I always do the simple thingy:
killall -HUP inetd
Why bother looking up the PID?
Rogier
Well, killall is a nice command, but run as root it is a little to much of a "smart missile" for my taste. I have no problem running , for example "killall netscape", as an ordinary user, but when I am root I want to be certain that the process I am about to signal is the one intended. I do not trust killall that much as root. Look at option -e for killall. This kind of uncertain behaviour does not really suit me. Not in a production environment at least. Another thing is that I want to use only one method for tasks that are similar, as much as possible. (Always use "kill" as root, etc). My work tend to be less errorprone that way. Makes my boss happy as well. ;-) But then again it is a matter of the situation. I can agree that there should not be more than one match for the above killall command. TJo <HR> <UL> <LI>APPLICATION/pgp-signature attachment: stored </UL> -- 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/
Paul Evans wrote:
<snip>
The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
# rcinetd reload would do the trick. Nadeem -- 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/
ps -ax|grep inetd will return the pid, as will "cat /var/run/inetd.pid".
If you want to kill a specific process & processes it has spawned, try
"killall
Paul Evans wrote:
<snip>
The problem, or part of it, could be that I just do not understand what the man means by kill -1 PID where PID is the process ID of the inetd deamon. How do I find out what the process ID is?
# rcinetd reload
would do the trick.
Nadeem
-- 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/
participants (8)
-
FBob＠wt.net -
icarus＠guldennet.nl -
nhasan＠usa.net -
pevans＠bigfoot.de -
phillipp＠w3eax.umd.edu -
tjo＠telia.com -
wayne＠aeonxe.com -
wulfie＠wulfric7.co.uk