Win9x and TNG status?

Karl Denninger karl at Denninger.Net
Mon Feb 21 22:04:28 GMT 2000


Ok, what am I doing wrong.

I just CVS'd a new copy of TNG.  The version claims to be "pre-3.0.0", so I
assume its correct.

The configure/makefile pleasantly put the files in a different base under
/usr/local/samba (thank you!), making it possible for me to leave alone my
2.0.6 config.

So I do that, change inetd.conf, kill the existing daemons and hit inetd,
and then hit the disk.  It fails, as expected (no password entry). 

So I move the password entry for my current logged-in user on the workgroup
from Win2K, and reclick the drive.  It comes up.

So at this point I know that file service is actually working off TNG
(because it had to read the new config and control files).

Now I go try to conncet to the domain and get a bunch of:

[2000/02/21 16:00:43, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 192.168.3.1: code = 12
[2000/02/21 16:00:43, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 192.168.3.1: code = 12
[2000/02/21 16:00:48, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
  process_logon_packet: Logon from 192.168.3.1: code = 12

Exactly what I was getting under 2.0.6!

What did I do wrong?

--
-- 
Karl Denninger (karl at denninger.net)  Web: http://childrens-justice.org
Isn't it time we started putting KIDS first?  See the above URL for
a plan to do exactly that!


More information about the samba-ntdom mailing list