Re: [Samba] SWAT is working but shows smbd/nmbd: not running
Jörg Nissen wrote: Take a look at your /etc/services and make sure you have the following entries: netbios-ns137/tcp netbios-ns137/udp netbios-dbm138/tcp netbios-dbm138/udp netbios-ssn139/tcp netbios-ssn139/udp Yes, I have them enabled in my /etc/services In your smb.conf do you have 127.0.0.1 added to interfaces = hosts allow = ? I think this is not important if I am connecting from another machine, is it? Zoran MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] To: Jörg Nissen [EMAIL PROTECTED]; samba@lists.samba.org Sent: Monday, March 20, 2006 2:57 PM Subject: Re: [Samba] SWAT is working but shows smbd/nmbd: not running Jörg Nissen wrote: It is most probably not a mainboard issue. You should post your smb.conf here as SWAT communicates with smbd/nmbd over 127.0.0.1 and ports 137, 138, 445. So you should make sure that communication is allowed. I am not using firewall but looks like ports 137 and 138 are not opened: server:/var/log/samba # nmap localhost Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-03-20 14:55 CET Interesting ports on localhost (127.0.0.1): (The 1649 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 110/tcp open pop3 111/tcp open rpcbind 139/tcp open netbios-ssn 199/tcp open smux 445/tcp open microsoft-ds 631/tcp open ipp 901/tcp open samba-swat 953/tcp open rndc 5801/tcp open vnc-http-1 5901/tcp open vnc-1 5902/tcp open vnc-2 Nmap finished: 1 IP address (1 host up) scanned in 0.326 seconds server:/var/log/samba # What should I do to open this ports on Suse 9.3 prof? Zoran MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] Newsgroups: mailing.unix.samba Sent: Wednesday, March 08, 2006 4:02 PM Subject: [Samba] SWAT is working but shows smbd/nmbd: not running Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. From that point (but maybe it is not related all) when I connect to swat, log in, and click status, I get valid page with open connections and files, but smbd and nmbd are show as not running. In same time everything else works as expected. I am using 64-bit version of Suse 9.3 prof. (swat version:3.0.12-5-SUSE). What went wrong? Zoran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT is working but shows smbd/nmbd: not running
Jörg Nissen wrote: It is most probably not a mainboard issue. You should post your smb.conf here as SWAT communicates with smbd/nmbd over 127.0.0.1 and ports 137, 138, 445. So you should make sure that communication is allowed. I am not using firewall but looks like ports 137 and 138 are not opened: server:/var/log/samba # nmap localhost Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-03-20 14:55 CET Interesting ports on localhost (127.0.0.1): (The 1649 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 110/tcp open pop3 111/tcp open rpcbind 139/tcp open netbios-ssn 199/tcp open smux 445/tcp open microsoft-ds 631/tcp open ipp 901/tcp open samba-swat 953/tcp open rndc 5801/tcp open vnc-http-1 5901/tcp open vnc-1 5902/tcp open vnc-2 Nmap finished: 1 IP address (1 host up) scanned in 0.326 seconds server:/var/log/samba # What should I do to open this ports on Suse 9.3 prof? Zoran MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] Newsgroups: mailing.unix.samba Sent: Wednesday, March 08, 2006 4:02 PM Subject: [Samba] SWAT is working but shows smbd/nmbd: not running Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. From that point (but maybe it is not related all) when I connect to swat, log in, and click status, I get valid page with open connections and files, but smbd and nmbd are show as not running. In same time everything else works as expected. I am using 64-bit version of Suse 9.3 prof. (swat version:3.0.12-5-SUSE). What went wrong? Zoran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT is working but shows smbd/nmbd: not running
Take a look at your /etc/services and make sure you have the following entries: netbios-ns137/tcp netbios-ns137/udp netbios-dbm138/tcp netbios-dbm138/udp netbios-ssn139/tcp netbios-ssn139/udp In your smb.conf do you have 127.0.0.1 added to interfaces = hosts allow = ? MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] To: Jörg Nissen [EMAIL PROTECTED]; samba@lists.samba.org Sent: Monday, March 20, 2006 2:57 PM Subject: Re: [Samba] SWAT is working but shows smbd/nmbd: not running Jörg Nissen wrote: It is most probably not a mainboard issue. You should post your smb.conf here as SWAT communicates with smbd/nmbd over 127.0.0.1 and ports 137, 138, 445. So you should make sure that communication is allowed. I am not using firewall but looks like ports 137 and 138 are not opened: server:/var/log/samba # nmap localhost Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-03-20 14:55 CET Interesting ports on localhost (127.0.0.1): (The 1649 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 110/tcp open pop3 111/tcp open rpcbind 139/tcp open netbios-ssn 199/tcp open smux 445/tcp open microsoft-ds 631/tcp open ipp 901/tcp open samba-swat 953/tcp open rndc 5801/tcp open vnc-http-1 5901/tcp open vnc-1 5902/tcp open vnc-2 Nmap finished: 1 IP address (1 host up) scanned in 0.326 seconds server:/var/log/samba # What should I do to open this ports on Suse 9.3 prof? Zoran MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] Newsgroups: mailing.unix.samba Sent: Wednesday, March 08, 2006 4:02 PM Subject: [Samba] SWAT is working but shows smbd/nmbd: not running Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. From that point (but maybe it is not related all) when I connect to swat, log in, and click status, I get valid page with open connections and files, but smbd and nmbd are show as not running. In same time everything else works as expected. I am using 64-bit version of Suse 9.3 prof. (swat version:3.0.12-5-SUSE). What went wrong? Zoran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT is working but shows smbd/nmbd: not running
Hi Zoran, in the [global] section of your smb.conf change the line interfaces = eth0, eth1 to interfaces = eth0, eth1, 127.0.0.1 Then restart smbd and nmbd (might not work with SWAT, use rcsmb restart and rcnmb restart instead). If this does not help, add the following line to your [global] section: hosts allow = 192.168.1.0/255.255.255.0, 192.168.2.0/255.255.255.0, 127.0.0.1 Restart smbd and nmbd. If it still does not work, add the following line: socket address = eth0, eth1, 127.0.0.1 Another restart should finally result in a correct working status under SWAT. MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] To: Jörg Nissen [EMAIL PROTECTED] Sent: Friday, March 10, 2006 9:03 AM Subject: Re: [Samba] SWAT is working but shows smbd/nmbd: not running Jörg Nissen wrote: It is most probably not a mainboard issue. You should post your smb.conf here as SWAT communicates with smbd/nmbd over 127.0.0.1 and ports 137, 138, 445. So you should make sure that communication is allowed. In attachment is my smb.conf. SWAT work normally from any computer in my two subnets 192.168.1.0 and 192.168.2.0. Everything is fine except showing status of smbd and nmbd. I attached two pictures. First, swat1.jpg shows what happens when I click status. On status bar you can find transferring data from server. This message stays here for five seconds, than I get swat2.jpg screen. I can't figure out what happened. This same configuration worked well in past. What should I do Jorg? Zoran MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] Newsgroups: mailing.unix.samba Sent: Wednesday, March 08, 2006 4:02 PM Subject: [Samba] SWAT is working but shows smbd/nmbd: not running Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. From that point (but maybe it is not related all) when I connect to swat, log in, and click status, I get valid page with open connections and files, but smbd and nmbd are show as not running. In same time everything else works as expected. I am using 64-bit version of Suse 9.3 prof. (swat version:3.0.12-5-SUSE). What went wrong? Zoran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT is working but shows smbd/nmbd: not running
It is most probably not a mainboard issue. You should post your smb.conf here as SWAT communicates with smbd/nmbd over 127.0.0.1 and ports 137, 138, 445. So you should make sure that communication is allowed. MfG Jörg Nissen - Original Message - From: Zoran Ljubisic [EMAIL PROTECTED] Newsgroups: mailing.unix.samba Sent: Wednesday, March 08, 2006 4:02 PM Subject: [Samba] SWAT is working but shows smbd/nmbd: not running Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. From that point (but maybe it is not related all) when I connect to swat, log in, and click status, I get valid page with open connections and files, but smbd and nmbd are show as not running. In same time everything else works as expected. I am using 64-bit version of Suse 9.3 prof. (swat version:3.0.12-5-SUSE). What went wrong? Zoran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Swat not working
I have used the commands /usr/sbin/smbd -D and /usr/sbin/nmbd -D And killall -HUP smbd and killall -HUP nmbd and killall -HUP xinetd all of which have produced no results. From what I have been able to tell I am supposed to create a file in the xinetd.d directory with the swat information. Was I also supposed to edit the xinetd.conf file? Thanks for your time `Matt -Original Message- From: Jeff Saxton [mailto:[EMAIL PROTECTED] Sent: Monday, January 03, 2005 2:35 PM To: 'Matt'; samba@lists.samba.org Subject: RE: [Samba] Swat not working Did you hup xinetd? Jeff Saxton Sr. Support Engineer SenSage, Inc. ( Formerly Addamark Technologies, Inc. ) http://www.sensage.com mailto:[EMAIL PROTECTED] OFFICE: +1 415-281-1900x128 CELL: +1 415-640-6392 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, January 03, 2005 12:29 PM To: samba@lists.samba.org Subject: [Samba] Swat not working I recently decided to set up a Linux machine with the intent to run samba on it. I am running Mandrake 10 and I have installed the latest version of samba from the website. But I can't seem to get samba and swat to work. Because when I go to http://localhost:901 http://localhost:901/ I receive an error, informing me that it cannot be reached. This is what I have done so far. Edit the services file Edit the xinetd Created and edited the smb.conf From what I can tell I should be able to access swat now, but it just does not seem to be working. Any help would be appreciated. Thanks for your time. `Matt -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Swat not working
Did you hup xinetd? Jeff Saxton Sr. Support Engineer SenSage, Inc. ( Formerly Addamark Technologies, Inc. ) http://www.sensage.com mailto:[EMAIL PROTECTED] OFFICE: +1 415-281-1900x128 CELL: +1 415-640-6392 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, January 03, 2005 12:29 PM To: samba@lists.samba.org Subject: [Samba] Swat not working I recently decided to set up a Linux machine with the intent to run samba on it. I am running Mandrake 10 and I have installed the latest version of samba from the website. But I can't seem to get samba and swat to work. Because when I go to http://localhost:901 http://localhost:901/ I receive an error, informing me that it cannot be reached. This is what I have done so far. Edit the services file Edit the xinetd Created and edited the smb.conf From what I can tell I should be able to access swat now, but it just does not seem to be working. Any help would be appreciated. Thanks for your time. `Matt -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] swat not working this time
Is it listening? Does netstat -l |grep swat turn up anything?
If not, xinetd needs to listen for port 901, easiest was is a chkconfig
swat on or you could restart xinetd.
~ Daniel
-Original Message-
From: Mike Stewart
Sent: Thursday, December 05, 2002 11:32 AM
To: [EMAIL PROTECTED]
Subject: [Samba] swat not working this time
Hi again, I've just reinstalled RH 7.2 and Samba 2.2.7 for the
unpteenth
time this time swat is not working !!! I have checked the
etc/services
file and swat 901/tcp is in there and I have a text file named swat in
etc/xinetd.d directory containing the following...
service swat
{
port = 901
socket_type = stream
wait = no
user = root
server = /usr/local/samba/bin/swat
log_on_failure +=USERID
disable = no
}
I can't access is from either the browser on my PC or from KDE's
Konqueror
Have I missed some vital step ? It all worked last week when I
first/second/third installed everything but I've been busy installing M$
Windoze 2000 for a few days and my brain is addled.
TVM
Mike
---
This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Swat NOT Working Yet!
On Wed, 2002-11-06 at 03:51, Danny Bradley wrote: I am running RedHat 8.0 and Samba 2.2.6. I already provided a proper xinetd file and appointed port 901 in /etc/services. What am I still missing? For whatever reason, I wasn't able to get to SWAT until I installed Webmin...also, prior to running Webmin and rebooting, I ran /usr/sbin/swat just for giggles and grins - after the reboot, and after getting into Webmin, I was able to get into SWAT via the SERVERS\SAMBA SERVER icon in Webmin... ...same thing happened on my last 7.2 box, and this is a 7.3 box...like I said - for whatever reason...dunno... -- Wed Nov 6 08:50:00 EST 2002 |____ | | / \ /| |'-. | | .\__/ || | | | | _ / `._ \|_|_.-' | | | / \__.`=._) (_ |kuhn media australia | |/ ._/ || |http://kma.0catch.com | |'. `\ | | |stephen kuhn | ;/ / | | |email: [EMAIL PROTECTED] | smk ) /_/| |.---.| |mobile: 0410-728-389 | ' `-`' | If you are not for yourself, who will be for you? If you are for yourself, then what are you? If not now, when? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SWAT not working
I don't understand passwords in samba or swat. But, I get around the problem by starting swat with the -a option. This is what I have in my inetd.conf file: swatstream tcp nowait.400 root/usr/local/samba/bin/swat swat -a Expect cries of outrage over this suggestion, but it works fine on a home network without particular security concerns. Joel I've installed samba 2.2.5 a while ago and I didn't need swat at that time but now I do. I followed the manpage and modified my inetd.conf etc, the swat files are in place but SWAT still gives me errors my password is wrong. I've checked my password etc and still it doesn't work. Any idea's Greetz Maxor -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
