Error: can't find _ldap._tcp.dc._msdc.<DNSDomainName>
- From: "Ron" <nobody@xxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 12:47:51 +0100
Hi All,
Still struggling with DNS configuration a W2k3 server.
Single server with DC / DNS(internal addresses only) / Exchange /
IntranetWebserver / Fileserver duties
Locally, workstations can join the domain by using what is/was the workgroup
name.
If browsing the network ( entire network / microsoft windows network ) this
name appears as if it were a workgroup
The FQDN of the server is resolvable for pinging, although it resolves to
the second of two IP addresses on the servers NIC both are internal network
addresses.
If I want to join a machine to the domain over the VPN (site to site
tunnel), I can't see the NETBIOS name and I'm told I should be using the
FQDN anyway. The FQDN is not resolvable but the IP address pings happily.
***
So when i try to connect I get the message can't find
_ldap._tcp.dc._msdc.<FQDN>
Any attempts to find help on this subject have so far ended up in
instructions to run nslookup just to prove what I already know - that the
SRV record is missing !
What I need to know is How to set up the SRV record. I thought at first that
this would be a trivial matter but try as I may, I can't seem to work out
where in the rats nest of a DNS management console I can insert a correctly
formatted record in the right place in the structure.
Any guidance of exactly where the SRV record is supposed to be and how to
add it would be greatly appreciated.
*** The VPN isn't obstructing anything as far as I know and the workstations
can run outlook and connect to the exchange server.
BTW rebuilding the server is not an option !
Thanks in advance,
Ron Barnett
.
- Follow-Ups:
- Re: Error: can't find _ldap._tcp.dc._msdc.<DNSDomainName>
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: Error: can't find _ldap._tcp.dc._msdc.<DNSDomainName>
- Prev by Date: Re: domain FQDN not resolving on client machine
- Next by Date: Re: CNAME not working
- Previous by thread: Re: Setting Metrics on A Records
- Next by thread: Re: Error: can't find _ldap._tcp.dc._msdc.<DNSDomainName>
- Index(es):
Relevant Pages
|
Loading