TNG > 2.2 Problems

[Michael Glauche]

Hi,
  I did a "field test" with TNG today, and I ran into a couple of 
problems.
Setup: linux intel/rh 6.2/glibc2.1, 10x NT4.0 SP 5
TNG set up similar to that in the FAQ, is WINS-server, nmbd
logs domain master ok.

When I do a "smbclient -L server" I get a segfault in smbd.

I did test it with 2.2, 2.3, 2.4, 2.4.1, 2.4.2 (yes, the machine
compiles fast ;)
Only 2.2 does it right, starting with 2.3 i get the segfault:
Program received signal SIGSEGV, Segmentation fault.
0x805eafe in api_RNetShareEnum (conn=0x80ad398, vuid=100,
param=0x80ad370
"",
    data=0x0, mdrcnt=65535, mprcnt=1024, rdata=0xbffffa8c,
rparam=0xbffffa88,
    rdata_len=0xbffffa84, rparam_len=0xbffffa80) at smbd/lanman.c:1696
1696                    sh2.info2_hdr = *ctr.share.info2.info_2[i];

#0  0x805eafe in api_RNetShareEnum (conn=0x80ad398, vuid=100,
    param=0x80ad370 "", data=0x0, mdrcnt=65535, mprcnt=1024,
rdata=0xbffffa8c,
    rparam=0xbffffa88, rdata_len=0xbffffa84, rparam_len=0xbffffa80)
    at smbd/lanman.c:1696
#1  0x8062d12 in api_reply (conn=0x80ad398, vuid=100, outbuf=0x80c6999
"",
    data=0x0, params=0x80ad370 "", tdscnt=0, tpscnt=19, mdrcnt=65535,
    mprcnt=1024) at smbd/lanman.c:3725
#2  0x805a2d9 in named_pipe (conn=0x80ad398, vuid=100, outbuf=0x80c6999
"",
    name=0xbffffbda "LANMAN", setup=0x0, data=0x0, params=0x80ad370 "",
    suwcnt=0, tdscnt=0, tpscnt=19, msrcnt=0, mdrcnt=65535, mprcnt=1024)
    at smbd/ipc.c:366
#3  0x805acec in reply_trans (conn=0x80ad398, inbuf=0x80b6591 "",
    outbuf=0x80c6999 "", size=99, bufsize=17408) at smbd/ipc.c:555
#4  0x8084d05 in switch_message (type=37, inbuf=0x80b6591 "",
    outbuf=0x80c6999 "", size=99, bufsize=17408) at smbd/process.c:550
#5  0x8084dc0 in construct_reply (inbuf=0x80b6591 "", outbuf=0x80c6999
"",
    size=99, bufsize=17408) at smbd/process.c:582
#6  0x8084fa7 in process_smb (inbuf=0x80b6591 "", outbuf=0x80c6999 "")
    at smbd/process.c:656
#7  0x80859a8 in smbd_process () at smbd/process.c:1004
#8  0x8051889 in main (argc=2, argv=0xbffffd84) at smbd/server.c:784

So, the problem lies somewhere in lanman.c the section at 1690 has
changed
quite a bit from 2.2 to 2.3.

So, I did continue testing 2.2, and run into a couple of more problems:
a) During logon screen, when I enter a wrong password, it takes VERY
long
time to verify, then I get something like "cannot log in to domain ...
error code
C0000253".
The strange thing is, that ALL following logins fail with a simmilar
message, but
with error nr# C0000037

b) sometimes the profiles are written as root, sometimes as user. That
leads to many
problems using profiles ;) but outsourcing them to a 2.0.7pre4 server
works fine ;)

c) When I try to change the password I sometimes get the error "cant
change password, 
error c00000BE"

d) sometimes NT tells me it can't find domain controller, usually after
logging
of one user. TNG is wins-server, client is registered, etc. did not look
any further
into this one yet. too tired ;)
This can only be cured with a reboot of NT, then everything works fine
again.

TIA,
   Michael
-- 
Samba Information HQ (in german)
http://www.sambahq.de/