Re: unable to resolve domain name
From: kwise (kwiseme_at_yahoo.com)
Date: 10/23/04
- Next message: Herb Martin: "Re: NSLookup Shows Local Machine Name"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: AD Integrated problem"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: unable to resolve domain name"
- Next in thread: Ace Fekay [MVP]: "Re: unable to resolve domain name"
- Reply: Ace Fekay [MVP]: "Re: unable to resolve domain name"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 23 Oct 2004 10:37:03 -0700
Hello everyone,
The setup of DC1 was done before I was to hire to clean the mess. DC1 has
Exchange 2000 with possible corrupted m drive ( no backup). Overall , DC1
performance warrented to bring a new dc to the domain and move everything to
it.
My guessing why it was setup that way, is because WG box will only see one
connection coming to it from the internal network. This org only has ten
licenses for that box.
This is only explansion that I can come up with. As you can tell , I am not
a gure guy like you guyes. Nor do I have adquate knowledge in AD.
I will do my best through your tips and advice to get this messy network up
and running in the proper way. I will keep you posted ! Thanks for your help
"Kevin D. Goodknecht Sr. [MVP]" wrote:
> In news:A48FC47A-1398-4C84-A7F6-0556C7F07703@microsoft.com,
> kwise <kwiseme@yahoo.com> commented
> Then Kevin replied below:
> > After installing a new win2000 ad in a domain that has
> > only one win2000 ad , and moving the operations master
> > role to the new box. The front end system are unable to
> > login to the domain. Nslookup is unable to login to the
> > domain name even though I was able to ping the domain
> > name from the front end. The old box was taking off line
> > because it has performance issues . I know it has
> > something to with dns , but I don't how to resolve it.
>
> Nslookup does not login to anything, it only resolves addresses, as I said
> in my other post using your ISP's DNS on any NIC in any position on any
> member of an AD domain is going to cause connectivity issues. Do not use
> your ISP's DNS anywhere except as a forwarder.
> 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
> http://support.microsoft.com/?id=300202&FR=1
>
> 825036 - Best practices for DNS client settings in Windows 2000 Server and
> in Windows Server 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
- Next message: Herb Martin: "Re: NSLookup Shows Local Machine Name"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: AD Integrated problem"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: unable to resolve domain name"
- Next in thread: Ace Fekay [MVP]: "Re: unable to resolve domain name"
- Reply: Ace Fekay [MVP]: "Re: unable to resolve domain name"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
