nmbd weirdness
Tim Potter
tpot at acsys.anu.edu.au
Wed Nov 18 02:16:47 GMT 1998
Just wondering if there is some domain controller stuff in the latest
version of nmbd that doesn't have a "no" default. When I started running
the latest CVS version of nmbd on the local network, weird stuff started
happening with (windows) clients unable to connect or browse any other
machines. A newly installed machine was unable to contact the domain
controller.
The following interesting entries in the log file are shown below
(aplogies for the crappy formatting). ACSYS-NT is the primary domain
controller and ALEXANDRIA is running the latest nmbd out of CVS.
[1998/11/17 16:33:20, 3] smbd/ipc.c:api_reply(3373)
Got API command 104 of form <WrLehDz> <B16BBDz>
(tdscnt=0,tpscnt=42,mdrcnt=645
11,mprcnt=8)
[1998/11/17 16:33:20, 3] smbd/ipc.c:api_reply(3378)
Doing NetServerEnum
[1998/11/17 16:33:20, 4] smbd/ipc.c:api_RNetServerEnum(1231)
server request level: B16BBDz 80000000 domains_req:Yes local_only:No
[1998/11/17 16:33:20, 4] smbd/ipc.c:get_server_info(1015)
Servertype search: 80000000
[1998/11/17 16:33:20, 4] smbd/ipc.c:get_server_info(1082)
**SV** ACSYS-NTDOM 80001000 ACSYS-NT
ACSYS-NTDOM
[1998/11/17 16:33:20, 4] smbd/ipc.c:get_server_info(1060)
r:serv type s: dom mismatch ALEXANDRIA 19a03 THE ACSYS UNIX
WWW/F
TP/EXTRANET SERVER ACSYS-NTDOM
[1998/11/17 16:33:20, 4] smbd/ipc.c:get_server_info(1060)
r:serv type s: dom mismatch ACSYS-NT 6124b THE ACSYS
OFFICE S
ERVER ACSYS-NTDOM
[1998/11/17 16:33:20, 4] smbd/ipc.c:api_RNetServerEnum(1259)
fill_srv_info ACSYS-NTDOM 80001000 ACSYS-NT
ACSY
S-NTDOM
[1998/11/17 16:33:20, 4] smbd/ipc.c:api_RNetServerEnum(1290)
fill_srv_info ACSYS-NTDOM 80001000 ACSYS-NT
ACSY
S-NTDOM
[1998/11/17 16:33:20, 3] smbd/ipc.c:api_RNetServerEnum(1305)
NetServerEnum domain = ACSYS-NTDOM uLevel=1 counted=1 total=1
As soon as I killed the new nmbd everything went back to normal within
minutes.
Tim.
More information about the samba-technical
mailing list