Andrew, Sorry, got disturbed there and accidently hit send... I've read a number of MSKB articles which seem similar to the problem but all their fixes haven't worked thus far... If you (or anyone else, please!) have any other suggestions or details of what I can try, I would be greatly appreciative.
Joe Pochedley If you have time to do it twice, you had time to do it right in the first place. -----Original Message----- From: Joe Pochedley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 4:17 PM To: NT 2000 Discussions Subject: RE: Domain does not exist? Andrew, In general I'd agree with that assumption, but by all accounts DNS is working properly... Now I have DNS set up on the DC as AD Integrated Zone... I have PTR records for the DNS servers, DC, and any NT4 BDC's... I can resolve both forward and backward and I have the primary DNS set to the Win2K DC... I have the appropriate SOA record pointing to the DC and the appropriate PTR records for FSMO, LDAP, etc etc (automatically created during DCPROMO) are all in place... We're using 10.1.0.0/16 for the network address with 10.1.1.x for the servers and 10.1.2.x through 10.1.4.x for the clients (only about 300 clients altogether).... Not that big a network. Joe Pochedley If you have time to do it twice, you had time to do it right in the first place. -----Original Message----- From: Andrew S. Baker [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 2:11 PM To: NT 2000 Discussions Subject: RE: Domain does not exist? Sounds like a Name Resolution issue, specifically DNS How large is the network? http://www.ultratech-llc.com/KB/?File=ADnetwork.TXT ASB http://www.ultratech-llc.com/KB -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Joe Pochedley Sent: Tuesday, December 17, 2002 12:11 PM To: NT 2000 Discussions Subject: AD: Domain does not exist? Last night I took the first step in upgrading our WinNT4 domain to Win2K with AD. I upgraded our PDC and most everything appears to have gone well. The problem I'm having though is this: I loaded the Admin tools on my Win2K workstation (also tried the .Net tools on my XP Pro station too with the same results)... When I try to open ADUC from my workstation, I get this message: Naming information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your System Administrator...etc... After clicking OK ADUC opens and if I attempt to connect to the domain I get nearly the same error message. If I attempt to connect to the newly upgraded DC, I can then at least view and somewhat administer the users and computers.... Opening the properties for the user takes upwards of 20 seconds, and if I go to the Account tab I get an error message stating that the "Pre Windows 2000 domain name for the user cannot be displayed." From that point I can't seem to save any changes to the account... Everything works fine on the Win2K "PDC" just not on any workstations... It's presently running in mixed mode, replicating to 4 other NT4 BDC's (I'm hoping to upgrade those in the next couple weeks)... I've verified that DNS is working correctly (on a separate Win2K server, but all entries appear in place and I can resolve the _ldap._tcp.domain name just fine).... I have also verified my workstation knows about the Win2K DC by running NLTEST /SC_RESET and that was successful... Is this normal of mixed mode domains or what am I missing? Thanks for any help! Joe Pochedley If you have time to do it twice, you had time to do it right in the first place. ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
