I know this question has already been asked a zillion times, but I have done my homework (Teach yourself samba in x hours + newsgoup search + web search) and I have not been able to solve the problem. Setup: Suse 8.1 samba server smb - nmb running 4 win98 boxes network configured and working workgroup = workgroup on all 5 machines, no spelling mistakes EnablePlainTextPassword=1 No wins server Internet connection via dsl, successfully shared Network neighborhood shows all win98 boxes, but no samba server Start>Search>computer finds the samba server, and shares can be mounted my smb.conf hereafter. I seem to have read somewhere that it was caused by the local loopback device lo. If I shut down lo, my problem is not solved, and on top of it I cannot ping the server from the win boxes, so I guess lo is needed. I know network neighborhood is supposed to be unreliable, but why does it work for most people an not for me? Why me??? Any help would be appreciated. Thanks, and best samba wishes for 2003. fx
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server load printers = yes guest account = pcguest log file = /usr/local/samba/var/log.%m max log size = 50 security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 192.168.0.0/255.255.255.0 local master = yes os level = 33 domain master = no preferred master = yes wins support = no dns proxy = no message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s
[homes] comment = Home Directories browseable = yes writable = yes hide dot files = yes
[printers] comment = All Printers path = /usr/spool/samba browseable = yes guest ok = yes writable = no printable = yes public = yes
[tmp] comment = Temporary file space path = /tmp read only = no public = yes browseable = yes
[public] comment = Public Stuff path = /home/public public = yes writable = yes printable = yes write list = @staff browseable = yes
[Samba-share] comment = Samba share path = /home/Samba-share browsable = yes guest ok = yes
-- ______________________ Courtesy of SuSE Linux nibz.org
On Sat, 2003-01-04 at 06:54, FX Fraipont wrote:
I know this question has already been asked a zillion times, but I have done my homework (Teach yourself samba in x hours + newsgoup search + web search) and I have not been able to solve the problem.
Let's see if we can help
Setup: Suse 8.1 samba server smb - nmb running 4 win98 boxes network configured and working workgroup = workgroup on all 5 machines, no spelling mistakes EnablePlainTextPassword=1 No wins server Internet connection via dsl, successfully shared
Network neighborhood shows all win98 boxes, but no samba server
Start>Search>computer finds the samba server, and shares can be mounted
my smb.conf hereafter.
I seem to have read somewhere that it was caused by the local loopback device lo.
If I shut down lo, my problem is not solved, and on top of it I cannot ping the server from the win boxes, so I guess lo is needed.
I know network neighborhood is supposed to be unreliable, but why does it work for most people an not for me?
Why me???
Any help would be appreciated. Thanks, and best samba wishes for 2003.
fx
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server load printers = yes guest account = pcguest log file = /usr/local/samba/var/log.%m max log size = 50 security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 192.168.0.0/255.255.255.0 local master = yes os level = 33 domain master = no preferred master = yes wins support = no dns proxy = no message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s
[homes] comment = Home Directories browseable = yes writable = yes hide dot files = yes
[printers] comment = All Printers path = /usr/spool/samba browseable = yes guest ok = yes writable = no printable = yes public = yes
[tmp] comment = Temporary file space path = /tmp read only = no public = yes browseable = yes
[public] comment = Public Stuff path = /home/public public = yes writable = yes printable = yes write list = @staff browseable = yes
[Samba-share] comment = Samba share path = /home/Samba-share browsable = yes guest ok = yes
Try this to see if you get the results that you want. Set in the global settings your local master to no and set the os level to 2 and restart the server. I have these options set and it works for me in 98,2K and Xp. You will need to wait until the browser elections take place but your server should show up within a few min. -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
Marshall Heartley wrote:
Try this to see if you get the results that you want. Set in the global settings your local master to no and set the os level to 2 and restart the server. I have these options set and it works for me in 98,2K and Xp. You will need to wait until the browser elections take place but your server should show up within a few min.
Nope, it does not work for me. Thanks anyway fxf -- ______________________ Courtesy of SuSE Linux nibz.org
Try these commands by root: # smbd # nmbd
Hi, I have several machines running SuSE and I want to set one up to be a network time server and the others to coordinate their clocks with the server. Any ideas how to go about this? Thanks Abraham -- Abraham Bloom, CISSP | The New Testament offers the basis for modern abrahambloom@comcast.net | computer coding theory, in the form of an X/motif/c/shell/perl | affirmation of the binary number system. Sys V/BSD/Linux/Sco | | But let your communication be Yea, yea; nay, | nay: for whatsoever is more than these cometh | of evil. -- Matthew 5:37
Hi, Forgot one other point, I also have some M$ Win machines I would like to sync the clock to the SuSE time server. Thanks Abraham Abraham Bloom wrote:
Hi,
I have several machines running SuSE and I want to set one up to be a network time server and the others to coordinate their clocks with the server. Any ideas how to go about this?
Thanks Abraham
-- Abraham Bloom, CISSP | The New Testament offers the basis for modern abrahambloom@comcast.net | computer coding theory, in the form of an X/motif/c/shell/perl | affirmation of the binary number system. Sys V/BSD/Linux/Sco | | But let your communication be Yea, yea; nay, | nay: for whatsoever is more than these cometh | of evil. -- Matthew 5:37
On Saturday 04 January 2003 7:27 am, Abraham Bloom wrote:
Hi,
Forgot one other point, I also have some M$ Win machines I would like to sync the clock to the SuSE time server.
set your "time server" to also be a samba server [most likely PDC, which will involve other things, like setting actually-enforced passwords...] set up a "logon script" that contains the line "net time /set". When users fire up their windows system, give their passwords, etc., a window will come up labled something like "executing windows NT startup", which is a DOS-box that runs the "script" specified by the PDC. [the other useful command to include is "net use <drive letter> /home" -- this causes the user's "home" directory on linux to be visible, via a samba share, as a drive letter on the windows machine.]
On Sat, 4 Jan 2003, Abraham Bloom wrote:
I have several machines running SuSE and I want to set one up to be a network time server and the others to coordinate their clocks with the server. Any ideas how to go about this?
Abraham, Hopefully these directions will help Install these three RPM files: ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/libcap-1.92-225.i586.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/xntp-4.1.1-120.i586.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/xntp-doc-4.1.1-120.i586.rpm xntp says that libcap is a dependency, so install it first. what I did is set up a cron job that stops ntpd, synchs time with a public time server using ntpdate -s, and then restarts ntpd again. The other workstations sync time with the local ntp server every 2 hours. Your milage may vary. So far, this has worked well for me. I installed the xntp-doc rpm because it includes quite a lot of useful information about network time servers & the ntp protocol. -Jonathan
Hi Sure this has been asked before. I've got an ADSL connection with an Alcatel USB modem, which I set up according to the SDB instructions. It works fine, but uses KInternet to connect. What I really want is for the connection to start up automatically when I log on. Also, when I shut down, the TERM signal triggers a kernel panic. I've read that this is something to do with pppd and the usb hotplug service not shutting down properly. So, what I need is a script that starts pppd on startup, and stops it (and rchotplug) when I shut down. What would I need to put in these scripts, and where should they go? As you might be able to tell, I'm new to this. To save me asking more obvious questions, can someone point me in the direction of a searchable list archive? I'm sure Geocrawler used to have one, but there doesn't seem to be any way to search it anymore. Thanks for your help Olly
See below for a script I use on SuSE 7.1, kernel 2.4.19 that I cobbled together from the skeleton script and the Speedtouch documentation. On Monday 06 January 2003 05:27 am, Oliver Maunder wrote: [snip-snip]
So, what I need is a script that starts pppd on startup, and stops it (and rchotplug) when I shut down. What would I need to put in these scripts, and where should they go?
[snip-snip] *****************start script***************************** #!/bin/sh #script for loading benoit drivers ### BEGIN INIT INFO # Provides: pppd call adsl # Required-Start: inetd # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: ### END INIT INFO # Source SuSE config . /etc/rc.config # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} case "$1" in start) echo -n "Starting pppd_adsl" ## Start daemon with startproc(8). If this fails ## the echo return value is set appropriate. # startproc should return 0, even if service is # already running to match LSB spec. startproc /usr/sbin/pppd call adsl # Remember status and be verbose rc_status -v ;; stop) echo -n "Shutting down pppd_adsl" ## Stop daemon with killproc(8) and if this fails ## set echo the echo return value. killproc -TERM pppd # Remember status and be verbose rc_status -v ;; status) echo -n "Checking for pppd_adsl: " ## Check status with checkproc(8), if process is running ## checkproc will return with exit status 0. # Status has a slightly different for the status command: # 0 - service running # 1 - service dead, but /var/run/ pid file exists # 2 - service dead, but /var/lock/ lock file exists # 3 - service not running # If checkproc would return LSB compliant ret values, # things could be a little bit easier here. This will # probably soon be the case ... checkproc pppd; rc=$? if test $rc = 0; then echo "OK" else echo "No process" if test -e /var/run/pppd.pid; then exit 1 else exit 3 fi fi #rc_status ;; *) echo "Usage: $0 {start|stop|status}" exit 1 ;; esac rc_exit ************************end script********************** I do not profess to be a whiz bash scripter and others may surely provide more artfully coded work, but it works. This file is located in /etc/init.d on my system. I ran insserv to add it to the appropriate rc level (see above in script). You will most likely need to adjust this to your system, but I hope this gives you some ideas. No guarantee, use at your own risk! I actually start the modem and login during boot and then reverse the process on a shutdown. Shutting down pppd seems to be all I need to do to prevent a freeze. -- ThankYouKindly! Willard E. [Bill] Fullam III wfullam@bellsouth.net http://home.bellsouth.net/p/PWP-fullamgroup
Be sure you have on each win98 boxes correctly set-up TCP/IP protocol as default You can delete all protocols except tcpip. If you don't have dhcp daemon (server) you have to setup manualy win98 boxes - e.g.: linux has ip address 192.168.0.1 win98box1 - 192.168.0.10, netmask 255.255.255.0, gateway 192.168.0.1 ... win98box1 - 192.168.0.14, netmask 255.255.255.0, gateway 192.168.0.1 also check if you have correctly set-up firewall (if any present). Ivan Mojzis Slovakia -----Original Message----- From: FX Fraipont [mailto:fxf@skynet.be] Sent: Saturday, January 04, 2003 12:55 PM To: suse Subject: [SLE] no Samba server in network neighborhood I know this question has already been asked a zillion times, but I have done my homework (Teach yourself samba in x hours + newsgoup search + web search) and I have not been able to solve the problem. Setup: Suse 8.1 samba server smb - nmb running 4 win98 boxes network configured and working workgroup = workgroup on all 5 machines, no spelling mistakes EnablePlainTextPassword=1 No wins server Internet connection via dsl, successfully shared Network neighborhood shows all win98 boxes, but no samba server Start>Search>computer finds the samba server, and shares can be mounted my smb.conf hereafter. I seem to have read somewhere that it was caused by the local loopback device lo. If I shut down lo, my problem is not solved, and on top of it I cannot ping the server from the win boxes, so I guess lo is needed. I know network neighborhood is supposed to be unreliable, but why does it work for most people an not for me? Why me??? Any help would be appreciated. Thanks, and best samba wishes for 2003. fx
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server load printers = yes guest account = pcguest log file = /usr/local/samba/var/log.%m max log size = 50 security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 192.168.0.0/255.255.255.0 local master = yes os level = 33 domain master = no preferred master = yes wins support = no dns proxy = no message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s
[homes] comment = Home Directories browseable = yes writable = yes hide dot files = yes
[printers] comment = All Printers path = /usr/spool/samba browseable = yes guest ok = yes writable = no printable = yes public = yes
[tmp] comment = Temporary file space path = /tmp read only = no public = yes browseable = yes
[public] comment = Public Stuff path = /home/public public = yes writable = yes printable = yes write list = @staff browseable = yes
[Samba-share] comment = Samba share path = /home/Samba-share browsable = yes guest ok = yes
-- ______________________ Courtesy of SuSE Linux nibz.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com __________ Informacia od NOD32 1.339 (20021230) __________ Tato sprava bola preverena systemom NOD32 pre Exchange. http://www.eset.sk
Ivan Mojzis wrote:
Be sure you have on each win98 boxes correctly set-up TCP/IP protocol as default You can delete all protocols except tcpip. If you don't have dhcp daemon (server)
done already
you have to setup manualy win98 boxes - e.g.: linux has ip address 192.168.0.1 win98box1 - 192.168.0.10, netmask 255.255.255.0, gateway 192.168.0.1 ... win98box1 - 192.168.0.14, netmask 255.255.255.0, gateway 192.168.0.1
done already smb server 192.168.0.99 winboxes 192.168.0.98/7/6/5 I said that the network and samba were working properly, except for the samba server not appearing in network neighborhood.
also check if you have correctly set-up firewall (if any present).
Susefirewall 2. :FW_SERVICE_SAMBA="yes" So it must be something else.... Thanks anyway Fx -- ______________________ Courtesy of SuSE Linux nibz.org
Try to set gateway for windows machines to 192.168.0.99 also - i think setting FW_SERVICE_SAMBA="yes" in Suse firewall is not enough, you have to enable/add in section 9 of /etc/sysconfig/SuSEfirewall2 FW_SERVICES_INT_TCP="137 139" FW_SERVICES_INT_UDP="137 139" if your winboxes are connecting to "internal" interface (e.g. eth1) of linux Ivan -----Original Message----- From: FX Fraipont [mailto:fxf@skynet.be] Sent: Saturday, January 04, 2003 3:26 PM To: suse Subject: Re: [SLE] no Samba server in network neighborhood Ivan Mojzis wrote:
Be sure you have on each win98 boxes correctly set-up TCP/IP protocol as default You can delete all protocols except tcpip. If you don't have dhcp daemon (server)
done already
you have to setup manualy win98 boxes - e.g.: linux has ip address 192.168.0.1 win98box1 - 192.168.0.10, netmask 255.255.255.0, gateway 192.168.0.1 ... win98box1 - 192.168.0.14, netmask 255.255.255.0, gateway 192.168.0.1
done already smb server 192.168.0.99 winboxes 192.168.0.98/7/6/5 I said that the network and samba were working properly, except for the samba server not appearing in network neighborhood.
also check if you have correctly set-up firewall (if any present).
Susefirewall 2. :FW_SERVICE_SAMBA="yes" So it must be something else.... Thanks anyway Fx -- ______________________ Courtesy of SuSE Linux nibz.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com __________ Informacia od NOD32 1.339 (20021230) __________ Tato sprava bola preverena systemom NOD32 pre Exchange. http://www.eset.sk
Ivan Mojzis wrote:
Try to set gateway for windows machines to 192.168.0.99 also - i think setting FW_SERVICE_SAMBA="yes" in Suse firewall is not enough, you have to enable/add in section 9 of /etc/sysconfig/SuSEfirewall2 FW_SERVICES_INT_TCP="137 139" FW_SERVICES_INT_UDP="137 139" if your winboxes are connecting to "internal" interface (e.g. eth1) of linux Ivan
I should think that if the needed ports had not been open on the firewall, I would not have been able to mount the shares I have defined on the winboxes. But I can do that, so it's not a question of ports. I tried anyway to open ports 137 139, restarted the firewall, but it does not change anything to my network neighborhood elusive icon. fxf -- ______________________ Courtesy of SuSE Linux nibz.org
On Saturday 04 January 2003 3:54 am, FX Fraipont wrote:
I know this question has already been asked a zillion times, but I have done my homework (Teach yourself samba in x hours + newsgoup search + web search) and I have not been able to solve the problem.
Setup: Suse 8.1 samba server smb - nmb running
which version of samba? [just curious -- shouldn't matter, but later versions have "more features"...]
4 win98 boxes
any of them "NT" [and then, "workstation" vs. "server"?] [...]
No wins server
trivial question: why not? [as in, "why not make the linux box the wins server?"] without a "wins" server, systems that do not "broadcast" the fact that they exist must be included in the "lmhosts" file of /every client/ that expects to "see" them "in the neighborhood" [this might give you an inkling as to what the problem may be, but read on...] [...]
Any help would be appreciated. Thanks, and best samba wishes for 2003.
[snipping shares & most-likely-unrelated options]
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server security = user local master = yes os level = 33 domain master = no preferred master = yes wins support = no
From the "man smb.conf" pages: <take a deep breath>
domain master (G)
Tell nmbd(8)to enable WAN-wide browse list collation. Set
ting this option causes nmbd to claim a special domain spe
cific NetBIOS name that identifies it as a domain master
browser for its given workgroup. Local master browsers in
the same workgroup on broadcast-isolated subnets will give
this nmbd their local browse lists, and then ask smbd(8)
for a complete copy of the browse list for the whole wide
area network. Browser clients will then contact their local
master browser, and will receive the domain-wide browse
list, instead of just the list for their broadcast-isolated
subnet.
Note that Windows NT Primary Domain Controllers expect to
be able to claim this workgroup specific special NetBIOS
name that identifies them as domain master browsers for
that workgroup by default (i.e. there is no way to prevent
a Windows NT PDC from attempting to do this). This means
that if this parameter is set and nmbd claims the special
name for a workgroup before a Windows NT PDC is able to do
so then cross subnet browsing will behave strangely and may
fail.
If domain logons = yes , then the default behavior is to
enable the domain master parameter. If domain logons is not
enabled (the default setting), then neither will domain
master be enabled by default.
Default: domain master = auto
OK, what this is saying:
windows's "network neighborhood" works like this: every computer regularly
"broadcasts" a message to the effect, "hi, I'm a dos/windows machine on this
network, I'm offering the following 'services', please remember me; if not,
I'll tell you again in 15 seconds" [or maybe it is 5 seconds -- for fun and
giggles, hook up a dozen windows computers to a switch and leave them all
"idle" -- watch for "broadcast storms"] Every OTHER computer in the network
is supposed to grab that information and note it down somewhere. Linux does
this [via nmdb] and you'll see files under /var/lib/samba that reflect the
data gathered [browse.dat / wins.dat]
local master (G)
This option allows nmbd(8)to try and become a local master
browser on a subnet. If set to false then nmbd will not
attempt to become a local master browser on a subnet and
will also lose in all browsing elections. By default this
value is set to true. Setting this value to true doesn't
mean that Samba will become the local master browser on a
subnet, just that nmbd will participate in elections for
local master browser.
Setting this value to false will cause nmbd never to become
a local master browser.
Default: local master = yes
check the file /var/log/samba/
Tom Emerson wrote:
which version of samba? [just curious -- shouldn't matter, but later versions have "more features"...]
2.2.5-102
4 win98 boxes
any of them "NT" [and then, "workstation" vs. "server"?]
just four windows 98 boxes, sim, jules, mart, cecile
no wins server
trivial question: why not? [as in, "why not make the linux box the wins server?"] without a "wins" server, systems that do not "broadcast" the fact that they exist must be included in the "lmhosts" file of /every client/ that expects to "see" them "in the neighborhood" [this might give you an inkling as to what the problem may be, but read on...]
I used to have wins enabled, until I read in "teach yourself samba in 24 hours" that wins was only really necessary when samba was used with several networks: mine is a small home network, in the 192.168.0.x range, so Wins is not necessary. Removing it did not change anything, which kinda proves the point, I suppose.
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server security = user local master = yes os level = 33 domain master = no preferred master = yes wins support = no
From the "man smb.conf" pages: <take a deep breath>
domain master (G)
Default: domain master = auto
local master (G)
Default: local master = yes
Actually, I used to have domain master = no Teach yoursef samba p 389: "the default value for this parameter is no" local master = yes Until one suse-lister advised me to change it to "no". Anyway, I've followed your advice, but I still can't see samba in NNeighborhood.
check the file /var/log/samba/
This will have lines in it indicating when a "browse master election" occurs. Your computer will try to become "the master", yet will abstain from attempting to be the "domain" master [actually, re-reading these two items myself helps makes sense to me -- at first it didn't...] Does it "win" these elections?
This is my log.nmbd fil [2003/01/04 14:16:41, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating sos nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/04 14:16:40, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 1372 [2003/01/04 14:16:41, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/04 14:16:41, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Ca nnot assign requested address ubnet lists. Exiting. Bind failed on port 137? Something to do with SuSEfirewall2? I was advised yesterday to open ports 136 137 on my firewall, tried it, but that did not change a thing. How can I have all theses error messages and at the same time be able to mount shares from the win98 boxes? It does not make sense to me.
After the system has been running for a while, what information appears in the /var/lib/samba/browse.dat file?
"WORKGROUP" c0001000 "VERTIGO" "WORKGROUP" "VERTIGO" 40049a23 "Samba 2.2.5" "WORKGROUP" "JULES" 40412003 "" "WORKGROUP" "MART" 40412003 "" "WORKGROUP" Thanks for your help fx -- ______________________ Courtesy of SuSE Linux nibz.org
On Sunday 05 January 2003 1:53 am, FX Fraipont wrote:
Tom Emerson wrote:
check the file /var/log/samba/
This will have lines in it indicating when a "browse master election" occurs. Your computer will try to become "the master", yet will abstain from attempting to be the "domain" master [actually, re-reading these two items myself helps makes sense to me -- at first it didn't...] Does it "win" these elections? This is my log.nmbd fil
[2003/01/04 14:16:41, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating sos nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/04 14:16:40, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 1372 [2003/01/04 14:16:41, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/04 14:16:41, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address ubnet lists. Exiting.
Bind failed on port 137? Something to do with SuSEfirewall2? I was advised yesterday to open ports 136 137 on my firewall, tried it, but that did not change a thing.
There are two primary ways you can "fail to get an address" 1) it's already in use -- make sure nmbd is NOT running and try the "netstat -a --tcp" command -- if the system shows it is "listening" on port 137, then "something else" has the port [track that down!] **potentially** this could be inetd/xinetd [that's its job: listen on several ports on behalf of various background/daemon type programs; when activity occurs, inetd spawns the appropriate daemon handler and passes the connection] if your system shows the port to be "in use", and investigation shows the owner to be "inetd", check the configuration file for nmb [and probably smb] You'll have to decide if you really want to continue using inetd to watch for and spawn these processes or if you want them to run "standalone". 2) your "nmdb" process is not running "as root" -- ports below 1024 are considered "privileged", which simply means that any process that tries to open such a port MUST be a superuser process -- this can either occur by having "root" explicitly run such a program, or by setting the program to be "suid" and making the owner of the program "root" [suid means set uid -- when started, the process changes from running as the user who initiated it to the "owner" of the file.]
How can I have all theses error messages and at the same time be able to mount shares from the win98 boxes? It does not make sense to me.
because "nmb(d)" doesn't transfer files -- smbd does. nmbd only manages the "names" found on the network [browsing & broadcasts]
After the system has been running for a while, what information appears in the /var/lib/samba/browse.dat file?
"WORKGROUP" c0001000 "VERTIGO" "WORKGROUP" "VERTIGO" 40049a23 "Samba 2.2.5" "WORKGROUP" "JULES" 40412003 "" "WORKGROUP" "MART" 40412003 "" "WORKGROUP"
From the looks of it, your computer has "seen" broadcasts from JULES and MART, but not CECILE or SIM. On the windows computer(s), you can check for much the same thing by using the DOS command "nmbstat" [I think -- look for exectuables ending with "stat" in the windows or windows/command directory]
Tom Emerson wrote:
1) it's already in use -- make sure nmbd is NOT running and try the "netstat -a --tcp" command -- if the system shows it is "listening" on port 137, then "something else" has the port [track that down!] **potentially** this could be inetd/xinetd
vertigo:/home/fx # netstat -a --tcp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:swat *:* LISTEN tcp 0 0 *:smtp *:* LISTEN tcp 0 0 *:mysql *:* LISTEN tcp 0 0 *:netbios-ssn *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:www-http *:* LISTEN tcp 0 0 *:x11 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 *:http-rman *:* LISTEN tcp 0 0 *:telnet *:* LISTEN tcp 0 0 *:ipp *:* LISTEN tcp 0 0 *:ssh *:* LISTEN But this does not give me the ports that are being "listened to" here's my /etc/services file: profile 136/tcp # PROFILE Naming System profile 136/udp # PROFILE Naming System netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp # NETBIOS Name Service Can I simply disable these?
2) your "nmdb" process is not running "as root" -- ports below 1024 are considered "privileged", which simply means that any process that tries to open such a port MUST be a superuser process -- this can either occur by having "root" explicitly run such a program, or by setting the program to be "suid" and making the owner of the program "root" [suid means set uid -- when started, the process changes from running as the user who initiated it to the "owner" of the file.]
No it is running as root
"WORKGROUP" c0001000 "VERTIGO" "WORKGROUP" "VERTIGO" 40049a23 "Samba 2.2.5" "WORKGROUP" "JULES" 40412003 "" "WORKGROUP" "MART" 40412003 "" "WORKGROUP"
From the looks of it, your computer has "seen" broadcasts from JULES and MART, but not CECILE or SIM. On the windows computer(s), you can check for much the same thing by using the DOS command "nmbstat" [I think -- look for exectuables ending with "stat" in the windows or windows/command directory]
This is simply because all the computers are not switched on all the time. Sim and cecile were switched off at the time. Thanks for your help FX -- ______________________ Courtesy of SuSE Linux nibz.org
On Sunday 05 January 2003 11:21 am, FX Fraipont wrote:
Tom Emerson wrote:
1) it's already in use -- make sure nmbd is NOT running and try the "netstat -a --tcp" command -- if the system shows it is "listening" on port 137, then "something else" has the port [track that down!] **potentially** this could be inetd/xinetd
vertigo:/home/fx # netstat -a --tcp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:netbios-ssn *:* LISTEN
But this does not give me the ports that are being "listened to"
netbios-ssn is port 139 -- to see this, do the netstat command with the switch "-an" instead of just "-a" [the "n" means "no names" or "numbers only"] You can also use "--udp" or "--inet" to show udp-only or "all" socket types respectively -- "I forgot..." the port 137 stuff shows up under UDP [though note in the /etc/services file that port 137 is defined identically for TCP and UDP style sockets]
here's my /etc/services file:
profile 136/tcp # PROFILE Naming System profile 136/udp # PROFILE Naming System netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp # NETBIOS Name Service
Can I simply disable these?
the fact that they are listed in /etc/services doesn't mean they are "enabled" or disabled -- /etc/services simply maps numbers to "human readable names" To find out [definitavely] what "process" has the port opend, we turn to another command: lsof [list Open Files], with the "-i" switch [show IP related files only -- the command "man lsof" gives full details] [note also you should do this as root] franky:~ # lsof -i :137 -n COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME nmbd 657 root 9u IPv4 2641 UDP *:netbios-ns nmbd 657 root 11u IPv4 2644 UDP 192.168.40.6:netbios-ns franky:~ # lsof -i :139 -n COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME smbd 661 root 9u IPv4 3320 TCP *:netbios-ssn (LISTEN) Note the "-i" parameter can be repeated: franky:~ # lsof -n -i :139 -i :137 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME nmbd 657 root 9u IPv4 2641 UDP *:netbios-ns nmbd 657 root 11u IPv4 2644 UDP 192.168.40.6:netbios-ns smbd 661 root 9u IPv4 3320 TCP *:netbios-ssn (LISTEN) (-n again means "numbers only/no names" -- without it, it looks up the DNS name for the computer at 192.168.40.2, which is long enough to make this example "wrap")
Tom Emerson wrote:
netbios-ssn is port 139 -- to see this, do the netstat command with the switch "-an" instead of just "-a" [the "n" means "no names" or "numbers only"]
netstat -an does not reveal anything about port 139
You can also use "--udp" or "--inet" to show udp-only or "all" socket types respectively -- "I forgot..." the port 137 stuff shows up under UDP [though note in the /etc/services file that port 137 is defined identically for TCP and UDP style sockets]
vertigo:/home/fx # netstat -an --udp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State udp 0 0 0.0.0.0:111 0.0.0.0:* udp 0 0 0.0.0.0:631 0.0.0.0:* vertigo:/home/fx # netstat -an --inet Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9925 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN <<<<<<<<<<<<<<< tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6711 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:111 0.0.0.0:* udp 0 0 0.0.0.0:631 0.0.0.0:*
To find out [definitavely] what "process" has the port opend, we turn to another command: lsof [list Open Files], with the "-i" switch [show IP related files only -- the command "man lsof" gives full details] [note also you should do this as root]
vertigo:/home/fx # lsof -n -i :139 -i :137 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME smbd 5922 root 10u IPv4 42845 TCP *:netbios-ssn (LISTEN) Something else: if I stop smbd with rcsmb stop, it stops all right. But rcnmb stop, followed by rcnmb status shows it is still running. Why? Plus, I was advised to check my SuSEfirewall2.conf file, and saw that port 139 was not explicitly open, and that broadcasts were not allowed. I duly corrected that, but still no luck. This is turning into private tuition :-) Thanks a lot fx -- ______________________ Courtesy of SuSE Linux nibz.org
On Sunday 05 January 2003 12:24 pm, FX Fraipont wrote:
Tom Emerson wrote:
netbios-ssn is port 139 -- to see this, do the netstat command with the switch "-an" instead of just "-a"
netstat -an does not reveal anything about port 139
yes it does -- you even pointed it out:
vertigo:/home/fx # netstat -an --inet Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN <<<<<
the number following the colon IS the "port"
To find out [definitavely] what "process" has the port opend, we turn to another command: lsof [list Open Files], with the "-i" switch [show IP related files only -- the command "man lsof" gives full details] [note also you should do this as root]
vertigo:/home/fx # lsof -n -i :139 -i :137 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME smbd 5922 root 10u IPv4 42845 TCP *:netbios-ssn (LISTEN)
Something else: if I stop smbd with rcsmb stop, it stops all right. But rcnmb stop, followed by rcnmb status shows it is still running. Why?
read that carefully again -- your first line says rc-S-mb stop works, but your second line says rc-N-mbd stop followed by status shows it running, so which is it? <S>mb or <N>mb? Either way, are you sure it actually stopped? does the process still show up under the "ps" command? ["ps aux | grep <processname>" is a conventient way to check for just one process -- remember to ignore the "grep" command, since the "command" portion will match itself -- for samba stuff, you can even use "grep mbd" and that will match both <S>mbd and <N>mbd] Also, did you investigate whether this might be handled via inetd/xinetd? If so, these "processes" might get started automagically. [if you REALLY do use inetd, you don't need to stop that service (because doing so messes with "other things") instead, alter the inetd.conf file to exclude the smb/nmb services and issue the command "kill -HUP <pid-of-inetd>" -- this causes inetd to re-read the configuration file and take appropriate steps...]
Plus, I was advised to check my SuSEfirewall2.conf file, and saw that port 139 was not explicitly open, and that broadcasts were not allowed. I duly corrected that, but still no luck.
You did open these to the "internal" network only, correct? It wouldn't do to open this to the "outside" -- after all, that is explicitly what the firewall should be protecting you from... :) But, to stop a moment and take stock of the situation: 1) smbd seems to work -- explicit [manual] connections & file transfers work 2) nmbd reports the error "cannot open port" for port 137 [per nmbd.log] 3) nothing seem to be explicitly using port 137 [port 139, yes] 4) permissions/ownership/execution of the nmbd file appears to be correct [owned & run by root] 5) as best as can be determined, the firewall is not blocking port 137/139 either you've overlooked something or misreported it -- now that you (we) are absolutely sure "nothing is using port 137", does the nmbd.log file still show errors trying to open/allocate port 137 when you start the program? [purge or move the file so a new one gets built -- no point in misleading yourself with old/out-of-date errors]
This is turning into private tuition :-)
You may send a check, for any amount you feel is appropriate for the information you've received, to the following address: Tom Emerson 3541 Fairchild Street La Crescenta, CA 91214 USA
Something else: if I stop smbd with rcsmb stop, it stops all right. But rcnmb stop, followed by rcnmb status shows it is still running. Why?
read that carefully again -- your first line says rc-S-mb stop works, but your second line says rc-N-mbd stop followed by status shows it running, so which is it? <S>mb or <N>mb?
vertigo:/home/fx # rcsmb status Checking for Samba classic SMB daemon running vertigo:/home/fx # rcsmb stop Shutting down Samba classic SMB daemon done vertigo:/home/fx # rcsmb status Checking for Samba classic SMB daemon unused vertigo:/home/fx # rcnmb status Checking for Samba classic NMB daemon running vertigo:/home/fx # rcnmb stop Shutting down Samba classic NMB daemon done vertigo:/home/fx # rcnmb status Checking for Samba classic NMB daemon running This was what I meant: even when I try to stop nmbd, it is still running. But killing the pid kills it all right.
You did open these to the "internal" network only, correct? It wouldn't do to open this to the "outside" -- after all, that is explicitly what the firewall should be protecting you from... :)
# Common: ssh smtp domain FW_SERVICES_INT_TCP="ssh smtp 9925 80 139" # Common: domain syslog FW_SERVICES_INT_UDP="137 138" # For VPN/Routing which END at the firewall!! FW_SERVICES_INT_IP="" Something else My nmb log reads: Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/06 14:32:57, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating subnet lists. Exiting. ~ But the computers on the network go from 192.168.0.99 to 192.168.0.95 There is no 192.168.0.1 on my network ! fxf -- ______________________ Courtesy of SuSE Linux nibz.org
On Monday 06 January 2003 12:34 pm, FX Fraipont wrote:
My nmb log reads:
Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/06 14:32:57, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating subnet lists. Exiting. ~
But the computers on the network go from 192.168.0.99 to 192.168.0.95
There is no 192.168.0.1 on my network !
As Homer S. would, say, "Doh!" Re-reading your original message [wherein you had your smb.conf file] I see: On Saturday 04 January 2003 3:54 am, FX Fraipont wrote:
[global] interfaces = 192.168.0.0/255.255.255.0
and referring to "man smb.conf", "interfaces" section: interfaces (G) This option allows you to override the default net work interfaces list that Samba will use for brows ing, name registration and other NBT traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable. The option takes a list of interface strings. Each string can be in any of the following forms: · a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth" · an IP address. In this case the netmask is deter mined from the list of interfaces obtained from the kernel · an IP/mask pair. · a broadcast/mask pair. The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted dec imal form. The "IP" parameters above can either be a full dotted dec imal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms. For example, the following line: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0. See also bind interfaces only. Default: all active interfaces except 127.0.0.1 that are broadcast capable You're telling samba to use "interface 192.168.0.0" [which is flat out invalid, btw, since nobody is allowed to use ".0" as their computer's node address; likewise .255 is a no-no] "perhaps" nmbd is "correcting" that for you by trying to use .1 instead of .0 [it could be a "common enough mistake..."] [checking my own file I see I've set mine to use the actual interface -- per the above, this really isn't neccessary, but I think "at one time" this computer was also "the firewall", so it had more than one IP address -- limiting Samba/nmbd to "just one interface" helps cut down potential "intrusion" points...] [you may take a discount on that check you were going to send me :) ]
Tom Emerson wrote:
[checking my own file I see I've set mine to use the actual interface -- per the above, this really isn't neccessary, but I think "at one time" this computer was also "the firewall", so it had more than one IP address -- limiting Samba/nmbd to "just one interface" helps cut down potential "intrusion" points...]
AAARgh.... Just when I thought you had found THE cause of all this, I remove the interface line in smb.conf, rename the log.nmbd file, kill the nmbd pid, restart nmbd, restart smbd, cross my fingers and toes, spit twice, turn aniclockwise seven times, and type ls /var/log/samba/log.nmbd, this is what I get: [2003/01/07 17:30:12, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/07 17:30:12, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 5751 [2003/01/07 17:30:12, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/07 17:30:12, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/07 17:30:12, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating subnet lists. Exiting. [2003/01/07 17:30:45, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/07 17:30:45, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 5769 [2003/01/07 17:30:45, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/07 17:30:45, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/07 17:30:45, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating subnet lists. Exiting. So what the heck is at stake here? Shouldn't I call an exorcist? fxf -- ______________________ Courtesy of SuSE Linux nibz.org
On Tuesday 07 January 2003 8:45 am, FX Fraipont wrote:
Tom Emerson wrote:
[checking my own file I see I've set mine to use the actual interface -- per the above, this really isn't neccessary ...]
AAARgh....
Just when I thought you had found THE cause of all this, I remove the interface line in smb.conf, rename the log.nmbd file, kill the nmbd pid, restart nmbd, restart smbd, cross my fingers and toes, spit twice, turn aniclockwise seven times, and type ls /var/log/samba/log.nmbd, this is what I get:
[essentially the same problem -- trying to allocate port 137 on 192.168.0.1] OK, "one last test..." per the docs, the default is to assign this "on every broadcast capable network interface"; presumably your system does NOT have interface 192.168.0.1 "defined", so attempts to allocate on that network should not be happening "but they are..." What happens if you explicitly add in interfaces 192.168.0.99/255.255.255.0 [I believe .99 is the one you said was this host -- obviously, alter this if I'm wrong...] I'm beginning to think the error messages are a bit of a red herring -- you're getting this message for address 192.168.0.1, which presumably isn't defined [aside: try an "ifconfig" command at some point -- you might want to pipe this to "more/less" or increase the number of lines in your terminal in case this scrolls -- perhaps something "grabbed" this IP address, such as dhcp, so your system is trying both...] so the error messages may be entirely correct, but pointless -- the system may be successfully assigning/opening port 137 on IP address 192.168.0.99, just not reporting it... [though netstat would/should show listening on "0.0.0.0", which means "whereever it comes in"]
Tom Emerson wrote:
OK, "one last test..." per the docs, the default is to assign this "on every broadcast capable network interface"; presumably your system does NOT have interface 192.168.0.1 "defined", so attempts to allocate on that network should not be happening "but they are..." What happens if you explicitly add in
interfaces 192.168.0.99/255.255.255.0
[I believe .99 is the one you said was this host -- obviously, alter this if I'm wrong...]
You're right. This is what I get: [2003/01/07 19:47:24, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/07 19:47:24, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 6245 [2003/01/07 19:47:24, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/07 19:47:24, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/07 19:47:24, 0] nmbd/nmbd.c:main(872) No, no luck .... BUT ! I think I've found the culprit. After editing smb.conf, I ran testparm, and got "Loaded services file OK" and an invitation to see the dump of my services definition, I pressed enter, and guess what I saw? # Global parameters [global] coding system = client code page = 850 code page directory = /usr/share/samba/codepages workgroup = WORKGROUP netbios name = netbios aliases = netbios scope = server string = Samba Server interfaces = 192.168.0.1/24 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< bind interfaces only = No security = USER
I'm beginning to think the error messages are a bit of a red herring -- you're getting this message for address 192.168.0.1, which presumably isn't defined [aside: try an "ifconfig" command at some point --
vertigo:/var/log/samba # ifconfig eth0 Link encap:Ethernet HWaddr 00:04:61:42:99:79 inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::204:61ff:fe42:9979/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:581363 errors:0 dropped:0 overruns:0 frame:0 TX packets:342496 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:720226372 (686.8 Mb) TX bytes:34177310 (32.5 Mb) Interrupt:11 Base address:0xc800 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:209 errors:0 dropped:0 overruns:0 frame:0 TX packets:209 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:154236 (150.6 Kb) TX bytes:154236 (150.6 Kb) ppp0 Link encap:Point-to-Point Protocol inet addr:217.136.113.211 P-t-P:217.136.113.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:80821 errors:0 dropped:0 overruns:0 frame:0 TX packets:89501 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:50811052 (48.4 Mb) TX bytes:54352598 (51.8 Mb)
you might want to pipe this to "more/less" or increase the number of lines in your terminal in case this scrolls -- perhaps something "grabbed" this IP address, such as dhcp,
I don't have dhcp running. So where does samba get all these configuration options listed in the dump that are not explicitly specified in /etc/smb.conf? Or is any net in the 192.168.0.x range defined like this : 192.168.0.1/24? But then, typing the question suddenly rings a belle, and I check my SuSEfirewall2 configuration, and I find: FW_MASQ_NETS="192.168.0.0/24" and full of hope, I change that to 192.168.0.99/24, restart firewall, nmbd, smbd, and the log.nmbd looks like this :-( [2003/01/07 20:01:22, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/07 20:01:22, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 7379 [2003/01/07 20:01:22, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/07 20:01:22, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/07 20:01:22, 0] nmbd/nmbd.c:main(872) ????? FXF -- ______________________ Courtesy of SuSE Linux nibz.org
On Tuesday 07 January 2003 11:05 am, FX Fraipont wrote: [...]
BUT ! I think I've found the culprit.
After editing smb.conf, I ran testparm, and got "Loaded services file OK" and an invitation to see the dump of my services definition, I pressed enter, and guess what I saw?
I think you're on to something -- did you ALSO happen to notice...
# Global parameters [global] server string = Samba Server
Your "original posting" of your smb.conf file listed the global section as follows:
[global] server string = Vertigo Samba Server
your SERVER STRING is different than testparm reports! you have a bunch of "other things" that testparm didn't report [though most are probably defaults anyway (though when I ran testparm myself, I saw there was "a lot" of output beyond "security = USER" -- I suspect you chopped this in your post?)] I'm thinking [and I *might* be off my rocker here] that the file you've been editing is NOT the file samba is using for the actual configuration!!! I ran my copy here, and noticed the first line shows what file it is "checking": franky:~ # testparm Load smb config files from //etc/samba/smb.conf what does your system say [and what file are you editing?] Processing section "[netlogon]" Processing section "[homes]" Processing section "[zope]" Processing section "[web]" Processing section "[printers]" Loaded services file OK. your list of "shares" from your original posting looks a lot like the "default", did you actually enter a "custom" share [like "web" or "zope" in my example above] and did testparm report those "shares"? Press enter to see a dump of your service definitions # Global parameters [global] coding system = client code page = 850 code page directory = /usr/share/samba/codepages workgroup = HOME-NET netbios name = netbios aliases = netbios scope = server string = SuSE file server (running samba %v) interfaces = 192.168.40.6/255.255.255.0 bind interfaces only = No security = USER [and a bunch more lines chopped...] I see that some things I've changed are indeed being reported by "testparm" [workgroup, server string, etc.] Unfortunately, you chose "WORKGROUP" for your workgroup, which is a default, so you wouldn't know if you were getting a "custom" or "default" configuration loaded...
Tom Emerson wrote:
On Tuesday 07 January 2003 11:05 am, FX Fraipont wrote: [...]
BUT ! I think I've found the culprit.
After editing smb.conf, I ran testparm, and got "Loaded services file OK" and an invitation to see the dump of my services definition, I pressed enter, and guess what I saw?
I think you're on to something -- did you ALSO happen to notice...
# Global parameters [global] server string = Samba Server
I did not realize this directly, because yesterday I rewrote a minimal smb.conf file. but then, Yippie, /etc/samba/smb.conf is indeed the real one !!!! and this is the log I now get [2003/01/07 20:45:17, 0] nmbd/nmbd.c:main(794) Netbios nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/07 20:45:22, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 10942 received with no matching recor d. [2003/01/07 20:45:22, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 10943 received with no matching recor d. [2003/01/07 20:45:41, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) ***** Samba name server VERTIGO is now a local master browser for workgroup WORKGROU P on subnet 192.168.0.99 ***** log.nmbd lines 1-13/13 (END) I know you will appreciate the sheer beauty of it :-) and you can see the result on www.nibz.org/gif/samba.jpg So you are a remarkable sleuth indeed. Thank you a thousand times for bearing with me, teaching me the mysteries of ps aux |grep mbd, and the like. I promise I'll sing your praise on my blog tomorrow, but in the meantime, you can watch the result of days of experiments on www.nibz.org/gif/samba.jpg. Thanks again fx PS. For God's sake, why are there TWo smb.conf files? This is utterly confusing.... -- ______________________ Courtesy of SuSE Linux nibz.org
Check your firewall is not blocking access on all network interfaces. This was the problem on the PC used here. On Saturday 04 January 2003 11:54, FX Fraipont wrote:
I know this question has already been asked a zillion times, but I have done my homework (Teach yourself samba in x hours + newsgoup search + web search) and I have not been able to solve the problem.
Setup: Suse 8.1 samba server smb - nmb running 4 win98 boxes network configured and working workgroup = workgroup on all 5 machines, no spelling mistakes EnablePlainTextPassword=1 No wins server Internet connection via dsl, successfully shared
Network neighborhood shows all win98 boxes, but no samba server
Start>Search>computer finds the samba server, and shares can be mounted
my smb.conf hereafter.
I seem to have read somewhere that it was caused by the local loopback device lo.
If I shut down lo, my problem is not solved, and on top of it I cannot ping the server from the win boxes, so I guess lo is needed.
I know network neighborhood is supposed to be unreliable, but why does it work for most people an not for me?
Why me???
Any help would be appreciated. Thanks, and best samba wishes for 2003.
fx
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server load printers = yes guest account = pcguest log file = /usr/local/samba/var/log.%m max log size = 50 security = user socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 192.168.0.0/255.255.255.0 local master = yes os level = 33 domain master = no preferred master = yes wins support = no dns proxy = no message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s
[homes] comment = Home Directories browseable = yes writable = yes hide dot files = yes
[printers] comment = All Printers path = /usr/spool/samba browseable = yes guest ok = yes writable = no printable = yes public = yes
[tmp] comment = Temporary file space path = /tmp read only = no public = yes browseable = yes
[public] comment = Public Stuff path = /home/public public = yes writable = yes printable = yes write list = @staff browseable = yes
[Samba-share] comment = Samba share path = /home/Samba-share browsable = yes guest ok = yes
participants (10)
-
Abraham Bloom -
FX Fraipont -
Ivan Mojzis -
Jonathan Nichols -
Linux World -
magre -
Marshall Heartley -
Oliver Maunder -
Tom Emerson -
Willard E. Fullam III