Barts boot disk stops working w/Win2003 AD

[NetworkJedi]

Im completely lost, and google has been NO help on this one... As such, I would greatly appreciate it if you guys (or girls) could put on your collective thinking caps and help a fellow out.

I have a 2003 server that was just running vanilla and was holding my ghost images on \\servername\ghost$. Nothing complicated. I used Bart's disk to boot clients, pull the image, and it all worked. The other day I dcpromo'ed the server, and now I can no longer log into the server to get the images for other machines. Im using a short password (didnt know if barts had a long enough field for a large one) and I've even tried logging in with full UNC names...

Thoughts? Questions? Jokes?

Thanks,
Mike Cain
Senior Network Engineer
C&N, INC

 

[vbrocks]

Security signing gets enabled on domain controllers in the registry, could this be part of the problem?

 

[NetworkJedi]

I thought about that... But Im not sure how to reinact that process in the msnet login process...The other part of that is that it works fine on a win2K server with AD. Odd...


I am going to try taking the msnet.cab from the 2003 server CD instead of the other one I am using... I doubt they are different...

Any and all other ideas appreciated.

MC

 

[Seaspray0]

It could be in the type of authentication allowed. 2003 likes kerberos authentication. I know 2000 will accept NTLM authentication and I suspect 2003 will accept this as well. Bart's will want NTLM authentication. When you set the server up, there were a few questions on the authentication you were going to allow. Try applying the security template that lowers the requirements.

 

[NetworkJedi]

thats a great point... Does dcpromo enable kerberos by default? I dont remember getting asked that question, but I have slept since then so...

Ill try it and let you all know if thats it. For those of us that use network boot floppies for over 1/2 of their work, this will be an ever increasing encounter with 2003 I thinking.

MC

 

[Titleist]

NetworkJedi,

Check the default DC policy for who has permissions to access the Domain Controller. When you dcpromo it locks the security tighter than a regular member server.

HTH
John