Re: Cannot ping Active Directory Domain Name
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Fri, 17 Oct 2008 13:56:59 +0000 (UTC)
Hello PhilTeale,
On WAN DC, what is the DNS server 172.74.15.2? This is not the WAN DCand also from another subnet, but should be the WAN DC. Also do not use the loopback address 127.0.0.1 use the real ip address the server has.
Loopback address on the LAN change also.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi
The WAN domain controller and the LAN domain controller are on the
same physical site. They are connected via Ethernet and it's one hop
across a Cisco router from one to the other. The other WAN domain
controllers are connected via Ethernet presented from an SDH fibre
ring.
IP Config from WAN Domain Controller:
Windows IP Configuration
Host Name . . . . . . . . . . . . : dc1
Primary Dns Suffix . . . . . . . : contoso.wan
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : contoso.wan
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-21-5A-4C-DF-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.76.90.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.76.90.250
DNS Servers . . . . . . . . . . . : 127.0.0.1
172.74.15.2
Ipconfig from LAN Domain Controller:
Configurazione IP di Windows
Nome host . . . . . . . . . . . . . . : SRV
Suffisso DNS primario . . . . . . . . : domain
Tipo nodo . . . . . . . . . . . . . . : Sconosciuto
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : domain
Scheda Ethernet Connessione alla rete locale (LAN):
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) PRO/1000 PL
Network
on
Indirizzo fisico. . . . . . . . . . . : 00-30-48-89-2B-DA
DHCP abilitato. . . . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . . . : 192.168.1.4
Subnet mask . . . . . . . . . . . . . : 255.255.255.128
Gateway predefinito . . . . . . . . . : 192.168.1.100
Server DNS . . . . . . . . . . . . . : 127.0.0.1
It's in Italian, but I guess you can work out the important bits :-)
Cheers
Phil
"Meinolf Weber" wrote:
Hello PhilTeale,
How did you connect the domains? Can you also post and unedited
ipconfig /all from both.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi Meinolf
Thanks for your reply.
We would love to rename the domain, but unfortunately it is not
under our control.
I have followed the steps in the document you linked to, and
although the secondary zones work, we still have the same problem;
we cannot ping the "domain" or "domain." domains from the WAN
domain.
nslookup of "domain." on the WAN domain does resolve to the domain
controller on the LAN domain, but still the AD Trust Wizard fails on
the WAN domain because it is not able to contact the LAN domain.
Do you have any other ideas?
Cheers
Phil
"Meinolf Weber" wrote:
Hello PhilTeale,
See here for DNS setup for a trust:
http://searchwinit.techtarget.com/expert/KnowledgebaseAnswer/0,2896
25
,sid1_gci1101656,00.html
Also your domain names should look like "domain.local" instead of
using single lable domain names like domain. See here:
http://support.microsoft.com/kb/300684
Did you ever thought about renaming the domain?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi
I am trying to establish a trust from a WAN domain to a domain on
a LAN. Network connectivity is established and confirmed.
The problem I am experiencing is that I cannot ping the domain
name from the domain on the WAN. I have configured forwarders on
the WAN DNS and can ping individual servers on the LAN domain, but
not the domain name itself.
Eg. I can ping server1.contoso. but not contoso. itself
(To complicate matters, the LAN domain does not use RFC compliant
naming; it is called "contoso" (or "contso.", I am not sure of the
difference). I don't think that it is a problem as both are AD
domains, but I thought it best to point out.)
I suspect the problem is actually with the LAN domain itself, as
when I log onto the domain controller server.contoso. I cannot
ping either "contoso" or "contoso."
My question is, what records need to be present in DNS to allow me
to ping the domain name from the domain controller? In all our
other domains, we can ping the domain name, eg example.com or
example.zone.
If run nslookup on the LAN domain controller ("server1.contoso")
and enter "contso" it returns non-existant domain, however if I
enter "contso." then it returns the IP address of the DNS server.
This demonstrates that DNS is somewhat working.
I understand that we will not be able to establish the trust until
both servers can contact a domain controller on the other domain
by resolving the domain name.
I hope someone is able to help.
Regards
Phil
.
- References:
- Re: Cannot ping Active Directory Domain Name
- From: PhilTeale
- Re: Cannot ping Active Directory Domain Name
- Prev by Date: Re: Cannot ping Active Directory Domain Name
- Next by Date: Re: what are member domains of a Forest
- Previous by thread: Re: Cannot ping Active Directory Domain Name
- Index(es):
Relevant Pages
|
