Can't ping other foreset\domain

Hi,
When I use my HW router's DHCP server that has a VPN to another forest, I
can ping everything in that forest just fine.

But when I use my newly installed Windows 2003 DHCP server, I can't ping the
other forest (using computer name for FQDN). I can ping their IP addresses
however. Also, two of the other forests DC's are even on my own router, yet
I can't ping their computer names.

Both DHCP servers allow me to find the internet and everything within my own
single domain.

My windows DNS has forwarders to my ISP's DNS.

I suppose there is something wrong with my DNS, but I can't understand that
my DNS is adequate when I use my HW router's DHCP server, but no longer is
adequate when I use my Windows Server DHCP server.

Any idea what is wrong?

--
Bob

What DNS servers do your hardware routers DHCP settings hand out?

If you have a forwarder set up for "All other DNS domains" to your ISPs DNS
server then you will never get the resolution you are after.

You should consider setting up a conditional forwarder for the other
forest's domain name to forward to the other forest's DNS server(s).

Cheers,
Jeremy.

"Bob" <86c6c2e6-(E-Mail Removed)> wrote in message
news:92637FCF-20E7-413E-8429-(E-Mail Removed)...
> Hi,
> When I use my HW router's DHCP server that has a VPN to another forest, I
> can ping everything in that forest just fine.
>
> But when I use my newly installed Windows 2003 DHCP server, I can't ping
> the
> other forest (using computer name for FQDN). I can ping their IP addresses
> however. Also, two of the other forests DC's are even on my own router,
> yet
> I can't ping their computer names.
>
> Both DHCP servers allow me to find the internet and everything within my
> own
> single domain.
>
> My windows DNS has forwarders to my ISP's DNS.
>
> I suppose there is something wrong with my DNS, but I can't understand
> that
> my DNS is adequate when I use my HW router's DHCP server, but no longer is
> adequate when I use my Windows Server DHCP server.
>
> Any idea what is wrong?
>
> --
> Bob
>

My hw router forwards all DNS requests to my Windows 2003 DNS server. If the
router determines the 2K3 DNS server is down, then DNS requests are forwarded
to the ISP's DNS.

My forwarder is set up for "All other DNS domains" to my ISPs DNS
server and then my router as last choice.

You suggest setting up a conditional forwarder for the other forest's
domain. How do I do that? I'm guessing I simply use the "Forwarders" tab
where I see "All other DNS domains" and use the "New" button to add the other
forests DC as follows:

DNS Domain: OH-SERVER-3
Selected domains forwarder IP address list: 192.168.21.243

Note that when I use my routers DHCP, I can "ping OH-SERVER-3" and it
resolves to 192.168.21.243. But when I use Windows DHCP, I can only "ping
192.168.23.243".

Also note that 192.168.23.243 (the other forest) is on the same router as my
own forest which always resolves regardless of which DHCP server I use.

--
Bob

Hold up Jeremy,

You may have got it working for me after all. But could you please confirm
my question on "conditional forwarders". Do I understand it correctly in
that I simply use the "Forwarders" tab where I see "All other DNS domains"
and use the "New" button to add the other forest?

I found this combination seems to work:


DNS Domain: example.local
Selected domains forwarder IP address list: 192.168.21.243

But this requires I ping the FQDN "ping oh-server-3.example.local" where
with the router I only had to "ping oh-server-3".

--
Bob

Another different question, if I may.

It seems to me that my forwarders do not replicate between the DC's. Is
this normal operation?


--
Bob

Hello,

Thank you for using newsgroup!

"conditional forwarders" is a new feature on Windows Server 2003 DNS. This
means you can forward a specified zone to the specified DNS Server. In this
case, you should click New button to add the other forest DNS name and
specify a DNS server into the list.

If you have any concerns, please feel free let me know.

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Did you have any questions? If you need more help or have other concerns in
the future, just post back into the newsgroup. It is always our pleasure to
be of help. Have a nice day!

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,

That is normal. You have to configure forwarders on every DNS Server.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Bob,

I am Ken Zhao - Mike's backup engineer. Have you any other questions?

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
================================================== ==
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ==
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| X-Tomcat-ID: 51206328
| References: <92637FCF-20E7-413E-8429-(E-Mail Removed)>
<1FE6F36A-AF45-4CE6-8C2C-(E-Mail Removed)>
<CA98ABDC-87FD-4B16-B068-(E-Mail Removed)>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-(E-Mail Removed) (Mike Luo [MSFT])
| Organization: Microsoft
| Date: Mon, 30 Apr 2007 03:37:42 GMT
| Subject: Re: Can't ping other foreset\domain
| X-Tomcat-NG: microsoft.public.windows.server.networking
| Message-ID: <(E-Mail Removed)>
| Newsgroups: microsoft.public.windows.server.networking
| Lines: 13
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:4105
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hello,
|
| That is normal. You have to configure forwarders on every DNS Server.
|
| Thanks & Regards,
|
| Mike Luo
|
| Microsoft Online Partner Support
| Get Secure! - www.microsoft.com/security
|
| ================================================== ===
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ================================================== ===
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|

Thanks Jeremy & Mike,
My forwarders seem to work now. I think it is more of a timing issue. It
took several hours, but eventually my forwarders started working well.

Using ipconfig /flushdns might have helped as well.

I think I like stub zones better though.
--
Bob