samba - Dec 1999 - WIN 2K and Samba 2.0.5a

I'm usually not this thick, but I'm really having a hard time adding a
Win 2K
RC2 station to an existing domain. I though it would be a piece of cake since we
already have 600 NT4sp4 stations talking to it.

I have encrypted passwords enabled, it has a machine account (from when it was
NT4) that I reset the password on, nothing has changed about the Samba server in
any way.

Is there something I missed from all the Win2K talk?

Please advise...

Bill
-- 



	/------------------------------------------------------\
	|                                                      |
	|                 William E. Jojo, Jr.                 |
	|                                                      |
	|         Senior Systems and Network Specialist        |
	|                                                      |
	|            Hudson Valley Community College           |
	|                                                      |
	|                    (518) 629 7540                    |
	|                                                      |
	|                   jojowil@hvcc.edu                   |
	|                                                      |
	\------------------------------------------------------/


	
			     We are young

		    Wandering the face of the earth

		Wondering what our dreams might be worth

		   Learning that we're only immortal...

			...For a limited time

hi william,

chances of getting 2.0.x as a pdc to win2k workstations: zero.  in fact,
negative, because i am going to kick up a stink if anyone says, "hey i
just ported the samba 2.1prealpha code that gets win2k to join a domain,
here's the patch!".

almost a year ago i actually removed all the nt PDC code from 2.0.x, and
it was put back in.

i did not, and i do not want to see samba 2.0.x as a PDC, ever.  the MSRPC
code base is now well over a year old, and it was only set up
experimentally, _anyway_.

if you want a PDC that works with nt5, use the latest cvs code.  you will
find that all sorts of other things work, too.  microsoft has made their
MSRPC code SEVERELY more robust than nt4 MSRPC code, and as samba is a
network-reverse-engineering project, we can only work from existing netmon
traces.  the new versions of nt5 show us new things about the MSRPC
services, and i do NOT want to see those back-ported to samba 2.0.x.

time to move on.  the split for 2.0.x and 2.1prealpha was well over a year
ago, and that's way, way too long.

luke.