Re: Problems with AD configuration?
From: Fran (no email)
Date: 08/11/04
- Next message: umesh: "using internet on Server 2000"
- Previous message: Delo: "Networking"
- Maybe in reply to: Fran: "Problems with AD configuration?"
- Next in thread: Fran: "Re: Problems with AD configuration?"
- Messages sorted by: [ date ] [ thread ]
Date: 11 Aug 2004 05:35:15 -0500
Actually, I did reboot. It was required when I joined the domain.
I also found that article on the MS site about fixing this problem.
The article states:
----------------------------------<clip>---------------------------------------
If the Sysvol is not shared, use Regedt32 to navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
Double-click the SysvolReady value, and change the data value from 0
to 1. Shutdown and restart the domain controller.
When the computer has restarted, open a CMD prompt and type:
nslookup and press Enter.
set q=srv and press ENTER.
_ldap._tcp.<FQDN> where <FQDN> is the domain controller's Fully
Qualified Domain Name.
----------------------------------<clip>---------------------------------------
When I try this I get errors.
When I type NSLOOKUP and hit enter I get: "*** Can't find server
name for address 192.168.94.10: Non-existent domain"
When I type in the line "_ldap._tcp.HDServer.DomainName.com (where
DomainName.com represents the real domain) I get:
Server: UnKnown
Address: 192.168.94.10
*** UnKnown can't find _ldap._tcp.hdserver.DomainName.com:
Non-existent domain.
This must be my configuration error as I set up another server here at
the office for testing and I get the very same issue(s) so I must be
doing something initally wrong.
(At least I'm consistent, huh?)
Fran
- Next message: umesh: "using internet on Server 2000"
- Previous message: Delo: "Networking"
- Maybe in reply to: Fran: "Problems with AD configuration?"
- Next in thread: Fran: "Re: Problems with AD configuration?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|