Can anyone tell me what this message means? It appeared on the console of
our Samba server (Sun Ultra 2170 running Solaris 2.5.1):
nmbd[7287]: sync_browse_lists: Failed to start browse sync with DMKT7
We are running Samba 1.9.18p8.
Thanks in advance.
Sally
--
_______________________________________________________________________________
Sally L Goldberg | Information Technology
goldberg@saintmarys.edu | Saint Mary's College
phone: 1-219-284-4737 | Notre Dame, IN 46556
Does anyone recognize this error message? Sep 28 10:28.34 :inetd[62] : /usr/local/samba/bin/nmbd : exit status 0x100 Daniel Hardy Email: danh@metasensors.com
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: vipin_mehta.vcf Type: text/x-vcard Size: 260 bytes Desc: Card for vipin Url : http://lists.samba.org/archive/samba/attachments/20000904/d640c4ee/vipin_mehta.vcf
Try the following settings: interfaces = 127.0.0.0/24 xx.xx.xx.xx/xx bind interfaces inly = yes where xx.xx.xx.xx/ss is the network address and mask of the interface samba should listen to. Maby this will do the trick. Ries
Hi all, I have a unix box running solaris 2.6 and SAMBA 2.0.4. I am getting the following error messages in the /var/adm/messages log: /opt/samba/bin/nmbd: HANGUP last message repeated XX times netbios-ns/udp server failing (looping), service terminated Can anyone tell me what this means and how to correct it? Thanks, Jose Salicrup Unix Systems Administrator Snelling and Snelling, Inc., Dallas, TX 75243
Anybody know what this message means? [2002/01/26 20:48:04, 0] nmbd/nmbd_incomingdgrams.c:process_master_browser_announce(398) process_master_browser_announce: Not configured as domain master - ignoring master announce. -- -Rob
Hello, I have installed samba 2.0.7 on a Redhat v7.0 machine. When I typed in the following command while logged in as root: [root@localhost /root]# smbclient -L server name SSL: Error error setting CA cert locations: error:00000000::lib(0) :func(0) :reason(0) trying default locations. added interface ip=192.168.100.2 bcast=192.168.100.255 nmask=255.255.255.0 Password: All I want to know is what does the SSL error mean? Thank you for any assistance you may be able to give me. Wade -------------- next part -------------- HTML attachment scrubbed and removed
Every time a user (on 2K or XP) logs in, I get these error messages:
[2003/08/04 17:34:47, 0] printing/print_cups.c:cups_printername_ok(388)
Unable to get printer status for USERNAME client-error-not-found
[2003/08/04 17:34:47, 0] smbd/service.c:make_connection(252)
MACHINENAME(10.x.x.x) couldn't find service USERNAME
[2003/08/04 17:34:47, 0] printing/print_cups.c:cups_printername_ok(388)
Unable to get printer status for USERNAME client-error-not-found
[2003/08/04 17:34:47, 0] smbd/service.c:make_connection(252)
MACHINENAME(10.x.x.x) couldn't find service USERNAME
Any clue as to what's causing them?
snippets from smb.conf
[general]
printing = cups
printcap name = cups
[printers]
comment = All Printers
path = /var/spool/lpd/
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
printer admin = root,scott
[print$]
comment = Printer Drivers
path = /usr/local/samba/printers
browseable = yes
guest ok = yes
read only = yes
write list = root,scott
thanks,
Scott
I noticed this error message within some of my users log files; rpc_server/srv_samr_nt.c:_samr_query_aliasmem(2626) _samr_query_aliasmem: Not yet implemented. Why does this mean and what do I need to do to stop this error message from appearing. BTW, the users all have XP machines. Martin Stacey IT Support Manager Safcol Australia Pty Ltd
On Thu, Nov 27, 2003 at 09:58:31AM +1030, Martin Stacey wrote:> I noticed this error message within some of my users log files; > > rpc_server/srv_samr_nt.c:_samr_query_aliasmem(2626) _samr_query_aliasmem: > Not yet implemented. > > Why does this mean and what do I need to do to stop this error message from > appearing.This is an RPC call not implemented in Samba 2.2.x but now implemented in Samba 3.0. You don't say what your version of Samba is (which should really be a pre-requisite for a bug report) but I'm assuming 2.2.x. This will dissapear if you upgrade to 3.0.x. Jeremy.