Re: "Windows cannot obtain the domain controller name..."
From: jokerchan (jokerchan_at_discussions.microsoft.com)
Date: 07/08/04
- Next message: C Hall: "Re: OU design"
- Previous message: frank brown: "ipsec filter shooting ads in foot?"
- In reply to: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Next in thread: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Reply: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 12:35:01 -0700
Lovely. However:
1.) I'm not running two domain controllers.
2.) I cannot do ANYTHING with Active Directory settings of any kind because it barks the "Invalid argument was specified" crap at me.
*shrug* Thanks for your help anyways. I'm going to try a repair under the assumption some files got corrupt somehow. All I'm really looking for is a Band-Aid to this problem so it'll function for about a week before we upgrade desktop OSs, upon which I can setup the network the way I want instead of fixing how it's been left for me. Anywho, thanks again.
-- - jokerchan "Oli Restorick [MVP]" wrote: > I'm surprised your network is quirky. To be honest, I'm surprised it's > running at all. > > That DNS configuration is never going to work. > > I'm going to make an assumption here that you have two domain controllers. > Here's a good configuration: > > Make your AD domain controllers DNS servers and switch to Active Directory > integrated DNS. > > Disable the unused NICs in your servers. > > In the TCP/IP config of every machine, include the DNS addresses of your two > local DCs *only*. > > In the DNS configuration utility on each DC, create forwarders to your ISP's > DNS servers. > > Use DHCP to configure TCP/IP for all your workstations. I would suggest > using DHCP for your members servers as well. In the DHCP config, make sure > that you only provide DNS entries for your internal DNS servers and *not* > your ISP's servers. Include your WINS servers if you're using them. > > It looks like you're using your router to do DHCP. That's fine as long as > it allows you the flexibility to configure it appropriately, as described > above. If not, make one of your Windows boxes a DHCP server. > > I suggest you go and buy a copy of Mastering Windows Server 2003 by Mark > Minasi et al (published by Sybex). It gives a readable introduction of how > to configure your network. > > Regards > > Oli > > > > "jokerchan" <jokerchan@discussions.microsoft.com> wrote in message > news:3A0ED4D4-3E72-4A72-BD2F-65AA44F298B5@microsoft.com... > > Event log contains the following error: > > > > "Windows cannot obtain the domain controller name for your computer > > network. Return value (10022)." > > > > Attempting to access any of the Active Directory Administration Tools > > produces the following error: > > > > "The configuration information describing this enterprise is not > > available. An invalid argument was supplied." > > > > I'm assuming this is why our network is acting quirky (e.g. won't resolve > > Internet addresses, lost ability to print to network printer, some > > services won't start, etc.)? Any help would be appreciated. > > > > -- > > - jokerchan > > >
- Next message: C Hall: "Re: OU design"
- Previous message: frank brown: "ipsec filter shooting ads in foot?"
- In reply to: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Next in thread: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Reply: Oli Restorick [MVP]: "Re: "Windows cannot obtain the domain controller name...""
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
