Zoran Ljubisic
2006-Mar-08 15:02 UTC
[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
Jörg Nissen
2006-Mar-10 07:23 UTC
[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"" <powersoft@bj.t-com.hr> 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
Jörg Nissen
2006-Mar-10 09:17 UTC
[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" <powersoft@bj.t-com.hr>
To: "J?rg Nissen" <joenis@arcor.de>
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""
<powersoft@bj.t-com.hr>
>> 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
>
Zoran Ljubisic
2006-Mar-20 13:57 UTC
[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"" <powersoft@bj.t-com.hr> > 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
Jörg Nissen
2006-Mar-20 14:09 UTC
[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-ns 137/tcp
netbios-ns 137/udp
netbios-dbm 138/tcp
netbios-dbm 138/udp
netbios-ssn 139/tcp
netbios-ssn 139/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" <powersoft@bj.t-com.hr>
To: "J?rg Nissen" <joenis@arcor.de>;
<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""
<powersoft@bj.t-com.hr>
>> 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
>
>
Zoran Ljubisic
2006-Mar-22 08:03 UTC
[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-ns 137/tcp > netbios-ns 137/udp > netbios-dbm 138/tcp > netbios-dbm 138/udp > netbios-ssn 139/tcp > netbios-ssn 139/udpYes, 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" <powersoft@bj.t-com.hr> > To: "J?rg Nissen" <joenis@arcor.de>; <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"" <powersoft@bj.t-com.hr> >>> 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