Re: users logging in
From: kjs \(nospam\) _at_verizon.net (_at_verizon.net)
Date: 09/10/04
- Next message: Bob: "Re: Service Pack"
- Previous message: Laura E. Hunter \(MVP\): "Re: server problem"
- In reply to: Miha Pihler: "Re: users logging in"
- Next in thread: Miha Pihler: "Re: users logging in"
- Reply: Miha Pihler: "Re: users logging in"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 10 Sep 2004 11:43:18 -0700
i ran the "dcdiag" and received all ok except for the
following:
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER1
Starting test: Connectivity
The host 0e6bd70f-1e82-42ad-9351-
17ce0dfd3ef3._msdcs.lw206.nscc.mass.ed
u could not be resolved to an
IP address. Check the DNS server, DHCP, server
name, etc
Although the Guid DNS name
(0e6bd70f-1e82-42ad-9351-
17ce0dfd3ef3._msdcs.lw206.nscc.mass.edu)
couldn't be resolved, the server name
(server1.lw206.nscc.mass.edu)
resolved to the IP address (10.2.2.1) and was
pingable. Check that
the IP address is registered correctly with the
DNS server.
......................... SERVER1 failed test
Connectivity
>-----Original Message-----
>Hi,
>
>Did you try these steps?
>
>*******************************************
>USER ACTION
>Determine what might have caused this failure, resolve the
>problem, and initiate registration of the DNS records by
>the domain controller. To determine what might have caused
>this failure, run DCDiag.exe. You can find this program on
>the Windows Server 2003 installation CD in
>Support\Tools\support.cab. To learn more about
>DCDiag.exe, see Help and Support Center. To initiate
>registration of the DNS records by this domain
>controller, run 'nltest.exe /dsregdns' from the command
>prompt on the domain controller or restart Net Logon
>service. Nltest.exe is available in the Microsoft Windows
>Server Resource Kit CD.
> Or, you can manually add this record to DNS, but it is
>not recommended.
>*******************************************
>
>This is error from the server? How about error on the
client? Can you post
>back Event IDs of error that you provided in your
previous post? Do you
>allow Dynamic Updates on your DNS server?
>
>Mike
>
>"kjs (nospam) @verizon.net"
<anonymous@discussions.microsoft.com> wrote in
>message news:9a4101c49740$0288aff0$a301280a@phx.gbl...
>> here is an error i'm receiving:
>>
>> The dynamic registration of the DNS
>> record '_ldap._tcp.Default-First-Site-
>> Name._sites.DomainDnsZones.lw206.nscc.mass.edu. 600 IN
SRV
>> 0 100 389 server1.lw206.nscc.mass.edu.' failed on the
>> following DNS server:
>>
>> DNS server IP address: 134.241.1.3
>> Returned Response Code (RCODE): 5
>> Returned Status Code: 9017
>>
>> For computers and users to locate this domain
controller,
>> this record must be registered in DNS.
>>
>> USER ACTION
>> Determine what might have caused this failure, resolve
the
>> problem, and initiate registration of the DNS records by
>> the domain controller. To determine what might have
caused
>> this failure, run DCDiag.exe. You can find this program
on
>> the Windows Server 2003 installation CD in
>> Support\Tools\support.cab. To learn more about
>> DCDiag.exe, see Help and Support Center. To initiate
>> registration of the DNS records by this domain
>> controller, run 'nltest.exe /dsregdns' from the command
>> prompt on the domain controller or restart Net Logon
>> service. Nltest.exe is available in the Microsoft
Windows
>> Server Resource Kit CD.
>> Or, you can manually add this record to DNS, but it is
>> not recommended.
>>
>> ADDITIONAL DATA
>> Error Value: DNS bad key.
>>
>> For more information, see Help and Support Center at
>>
>>
>> >-----Original Message-----
>> >Hi,
>> >
>> >Can you check your client's DNS settings under TCP/IP.
>> Client's Preferred
>> >DNS should point to Active Directory DNS (probably your
>> Active Directory
>> >server). Computers use DNS to find Global Catalog and
>> Domain Controller
>> >servers. If DNS is set to point to e.g. ISP they will
not
>> be able to find
>> >this information and client will either logon slowly or
>> not at all.
>> >
>> >If this doesn't solve your problem, can you please
check
>> your Event logs
>> >(System and Application logs) for any Errors and post
>> back with more
>> >details.
>> >
>> >Mike
>> >
>> >"kjs (nospam) @verizon.net"
>> <anonymous@discussions.microsoft.com> wrote in
>> >message news:097001c49738$078f96b0$a401280a@phx.gbl...
>> >> i have a small active directory domain with 20 pc's
and
>> a
>> >> windows 2003 server. when the users try to login to
the
>> >> server it takes forever to finally login and apply
>> settings
>> >> (roughly 20minutes). when i go into the task manager
and
>> >> see what users are loggd in, none appear. help
>> >
>> >
>> >.
>> >
>
>
>.
>
- Next message: Bob: "Re: Service Pack"
- Previous message: Laura E. Hunter \(MVP\): "Re: server problem"
- In reply to: Miha Pihler: "Re: users logging in"
- Next in thread: Miha Pihler: "Re: users logging in"
- Reply: Miha Pihler: "Re: users logging in"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
