Re: specified domain either does not exist...
- From: Tcs <TSmithATEastPointCityDOTorg@>
- Date: Fri, 28 Oct 2005 08:56:59 -0400
Thanks. It *was* DNS. Our DNS servers were *not* in our/my DNS server table. I
replaced our ISP's DNS server entries with *our* DNS servers, and voila! My
script now works. Amazing.
Thanks a lot,
Tom
On Thu, 27 Oct 2005 15:53:44 -0600, "Danny Sanders"
<Danny.Sanders@xxxxxxxxxxxxxxxxx> wrote:
> the junior tech), is long logon times (I pretty much *always* have to wait
>> 1minute 35 seconds at the "Applying your security settings..." window. I
>> think
>> this is too long. And of course the network guy doesn't have long logon
>> times.
>> He says he thinks my problem is a bad port on the switch. (Riiight.)
>
>
>Sounds like DNS to me.
>
>> I've taken a quick look thru the trees(?)/paths. I usually see 3 "ldap"
>> entries
>> (our two DCs and the Exchange server). The two DCs run DNS, the ES (2k3)
>> does
>> not. *Normally* the ES is the 1st of the 3 entries. (The 3 entries I
>> refer to
>> are all the Service Location (SRV) records with "_ldap" in the 1st
>> column.)
>
>I don't think this is a problem as long as the client can "find" the SRV
>record. If in the properties of TCP/IP on a client, they point to *any*
>*other* server other than the one with the SRV records, that would cause
>problems.
>If you run ipconfig /all from command prompt on a client you can see the IP
>address of the server it uses for DNS. Check with your admin to see if these
>are your DNS servers
>
>
>hth
>DDS W 2k MVP MCSE
>
>"Tcs" <TSmithATEastPointCityDOTorg@> wrote in message
>news:cj22m1tqhhfshqmipi7fb8jm0e8mse7520@xxxxxxxxxx
>> Thank you. I'm looking into it. And yes, another problem *I* have (along
>> with
>> the junior tech), is long logon times (I pretty much *always* have to wait
>> 1minute 35 seconds at the "Applying your security settings..." window. I
>> think
>> this is too long. And of course the network guy doesn't have long logon
>> times.
>> He says he thinks my problem is a bad port on the switch. (Riiight.)
>>
>> I've taken a quick look thru the trees(?)/paths. I usually see 3 "ldap"
>> entries
>> (our two DCs and the Exchange server). The two DCs run DNS, the ES (2k3)
>> does
>> not. *Normally* the ES is the 1st of the 3 entries. (The 3 entries I
>> refer to
>> are all the Service Location (SRV) records with "_ldap" in the 1st
>> column.)
>>
>> I'm told that the ES *was* x.x.x.123, and is *now* x.x.x.12. But in DNS
>> however, it still shows as x.x.x.123.
>>
>> It's been maybe 5 years since I played with DNS myself (NT4/w2k), but
>> isn't the
>> "order" of the records significant? (The 3 I see repeated in multiple
>> places
>> can't be in alphabetical order. They're spelled correctly, but the ES
>> record is
>> usually 1st, when it should be last, shouldn't it?) Anyway, I've tried
>> using
>> Remote Desktop to log onto the 2 DCs, and did so without incident. The
>> ES?
>> NOPE. I get *no* response at x.x.x.123. I *can* log on at x.x.x.12.
>>
>> I don't know if changing all the appropriate DNS records from x.x.x.123 to
>> x.x.x.12 will fix what's wrong, but it's certainly a start, no?
>>
>> And if the "order" of the DNS records is significant, perhaps rearranging
>> them
>> will fix the/another problem.
>>
>> I hope the network guy understands. I'm not trying to do his job. I'm
>> just
>> trying to get my problem fixed. (A problem which isn't very high on his
>> priority list, since everything seems to pretty much be working. Or so it
>> seems.)
>>
>> Thanks again for the assist...
>>
>> Tom
>>
>> On Thu, 27 Oct 2005 09:05:34 -0600, "Danny Sanders"
>> <Danny.Sanders@xxxxxxxxxxxxxxxxx> wrote:
>>
>>>> The specified domain either does not exist or could not be contacted.
>>>>
>>>
>>>I'm not a programmer but this message does not seem to be a programming
>>>error to me. It seems to be a DNS error.
>>>
>>>An AD domain totally relies on DNS to "find" the domain.
>>>Basic DNS set up is install DNS on the existing AD DC. In the properties
>>>of
>>>TCP/IP point the DNS server to itself for DNS. Point all AD clients to the
>>>DNS server set up for the AD domain only. For Internet access configure
>>>your
>>>AD DNS server to forward requests and list your ISP's DNS server as the
>>>forwarder, or use root hints.
>>>
>>>See:
>>>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
>>>
>>>
>>>
>>>Setting Up the Domain Name System for Active Directory
>>>
>>>http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
>>>
>>>
>>>
>>>How to configure DNS for Internet access in Windows Server 2003
>>>
>>>http://support.microsoft.com/default.aspx?scid=kb;en-us;323380
>>>
>>>
>>>
>>>An AD client "finds" the AD domain by querying the DNS server for SRV
>>>records. Pointing the DNS server to itself for DNS allows the DNS server
>>>to
>>>register it's SRV record the client needs to find the domain. When this
>>>SRV
>>>record is not found the *most* common response is "The specified domain
>>>either does not exist or could not be contacted"
>>>
>>>
>>>
>>>Another common side effect is long log in times on the client machines,
>>>and
>>>group policy problems.
>>>
>>>
>>>
>>>It's solved by setting up DNS properly.
>>>
>>>
>>>
>>>hth
>>>
>>>DDS W 2k MVP MCSE
>>>
>>>
>>>
>>>"Tcs" <TSmithATEastPointCityDOTorg@> wrote in message
>>>news:8fqvl15mkvl8sebthl7k0fhmagb1u9rgl3@xxxxxxxxxx
>>>> This is probably one of those really simple things, but I don't know
>>>> what
>>>> my
>>>> problem is, so here goes...
>>>>
>>>> I'm trying to use a .vbs script to enumerate all the computers in my
>>>> domain. (We
>>>> have an old NT4 domain with 2 DCs, and one new w2k3 domain with 2 DCs.)
>>>> All
>>>> users have been moved to the new domain. Most clients and the NT4 DCs
>>>> are
>>>> still
>>>> in the old domain. My PC is in the new domain.
>>>>
>>>> Whenever I try to run my scripts (I've tried several [alledgedly]
>>>> working
>>>> scripts) they all error out. The error that *seems* to be the most
>>>> telling is:
>>>>
>>>> The specified domain either does not exist or could not be contacted.
>>>>
>>>> I've tried both specifying a domain name, and not. (I don't really
>>>> think
>>>> that
>>>> I'm supposed to.) Something is apparently wrong, but I don't know what.
>>>> I've
>>>> been playing with this for quite some time, and have *sort of* narrowed
>>>> it
>>>> down
>>>> to something about the 'LDAP' statement. One website mentioned
>>>> something
>>>> about
>>>> it *probably* being a syntax error, or something likewise simple.
>>>> Here's
>>>> my
>>>> code:
>>>>
>>>> ----------code----------
>>>> ' Get Domain name from RootDSE object.
>>>> Set objRootDSE = GetObject("LDAP://RootDSE";)
>>>> strDomain = "LDAP://"; & objRootDSE.Get("defaultNamingContext")
>>>>
>>>> Const ADS_SCOPE_SUBTREE = 2
>>>> Set objConnection = CreateObject("ADODB.Connection")
>>>> Set objCommand = CreateObject("ADODB.Command")
>>>> objConnection.Provider = "ADsDSOObject"
>>>> objConnection.Open "Active Directory Provider"
>>>> Set objCommand.ActiveConnection = objConnection
>>>> objCommand.CommandText = "Select printerName, serverName from 'LDAP://'
>>>> &
>>>> strDomain where objectClass='printQueue'"
>>>> objCommand.Properties("Page Size") = 1000
>>>> objCommand.Properties("Timeout") = 30
>>>> objCommand.Properties("Searchscope") = ADS_SCOPE_SUBTREE
>>>> objCommand.Properties("Cache Results") = False
>>>>
>>>> Set objRecordSet = objCommand.Execute
>>>> objRecordSet.MoveFirst
>>>> Do Until objRecordSet.EOF
>>>> Wscript.Echo "Printer Name: " &
>>>> objRecordSet.Fields("printerName").Value
>>>> Wscript.Echo "Server Name: " & objRecordSet.Fields("serverName").Value
>>>> objRecordSet.MoveNext
>>>> Loop
>>>> ----------code----------
>>>>
>>>> I've also tried netdom. (I found reference to it in the scripting
>>>> group.)
>>>> Makes
>>>> no difference if I try to query the new or old domain, it says it was
>>>> unsuccessful.
>>>>
>>>> I can 'remote desktop' to the servers, and it looks like Active
>>>> directory
>>>> is
>>>> working to me, but I'm not really the network guy.
>>>>
>>>> Would anyone happen to know how I might try to find what my problem is?
>>>> And
>>>> even possibly how I might fix it?
>>>>
>>>> Any help is appreciated, thanks in advance,
>>>>
>>>> Tom
>>>>
>>>
>
.
- Prev by Date: Re: Active Directory account permissions
- Next by Date: RE: extending Active Directory
- Previous by thread: Re: specified domain either does not exist...
- Next by thread: Automatic AD login via web?
- Index(es):
Relevant Pages
|
