Server 2003 vs Server 2000

edited September 2004 in Science & Tech
whats up everyone. Wanted to see if anyone out there had any ideas about a problem that has me beating my head. Here is the problem in a nutshell

I have a Win2000 server that is my domain controller
i have a win2003 server that attaches to the domain controller but everyother day the 2003 server loses connection to the domain causing havoc. the error i get on the event viewer is (ID# 5719 NELOG_netlogonAuthNODOMAINController) that basically say that the computer was not able to set up a secure session with the domain causing it to not authenticate to the domain server.

my question to everyone is why is this happening ?

i have found a workaround for this problem ( only temporary as problem still continues) but in order to rejoin the domain i have to take it off the domain and put it in WORKGROUP and then restart. Login to WORKGROUP and then put it back on the DOMAIN then restart and PRESTO i am back on and everything working good for another day ( but original problem happens again in 2 days)

my second question is does anyone know what i need to change either on the domain server or the 2003 server?

thanks to everyone that takes time to read and help out

Comments

  • ShortyShorty Manchester, UK Icrontian
    edited September 2004
    Is there any reason why both can't be Domain Controllers???

    Having redundant DC's is very wise in any enterprise for redundancy :)

    As to your problem, Im not 100% sure.. I've never seen or heard of it before.
  • edited September 2004
    Shorty first of all i want to thank you for your quick response and input on this issue.

    but here is the problem 2000 and 2003 (per Microsoft) there are some issues between them getting along kind of like a powerstruggle of some kind but my understanding is that you cannot have 2 primary domain controllers one has to be the primary and then the other can be a back domain controller. The backup does not have the same rights until you promote it.

    i have been searching frantically for answers to this problem and have not seen any documentation for it but i have seen others complain about the same thing. The only thing right now that i have changed that i wont know until a couple of days is
    under the PROPERTIES OF NETWORK CONNECTIONS. there is a tab called Authentication. There are 3 boxes the first one states "ENABLE IEEE 802.1x authentication for this network". the next one states "Authenticate as computer when computer information is available". and finally "Authenticate as guest when usere or computer information is unavailable".

    The 1st and 2nd boxes are the ones that i checked off now but after i checked off the first box i had to select the EAP type I had 3 choices
    A. MD5-Challenge
    B. Protected EAP (PEAP)
    C. Smart Card or other certificate

    I selected the Smart Card or other certificate

    does anyone know what exactly that is doing?

    thanks again
  • ShortyShorty Manchester, UK Icrontian
    edited September 2004
    That's incorrect information regarding having two Win2x servers :)

    They are equal peers. You have to assign <a href="http://www.svrops.com/svrops/documents/fsmo.htm">FSMO roles</a> between them.. but there is no PDC/BDC architecture ala NT4 :)
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited September 2004
    What he said..... active directory does away with the concept of primary/secondary. A domain controller is a domain controller, and they will replicate to each other.

    Lets get the basics out of the way. Is DNS installed and configured correctly on one of the servers? Can you ping, by name only, the win2K box from the 2k3 one?

    It seems like it might be a name resolution problem.
Sign In or Register to comment.