|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hi,
I can't figure out why I can't ping my simple Belkin $50 router (which of
course means I can't find the internet).
My configuration is as follows:
Router address is 192.168.21.1 and its DHCP server is disabled.
I've three Windows 2003 Server DC's all of which have DNS Server and two
have DHCP Server.
The DHCP Server's are configured has follows:
Scope option "003 Router" is set for 192.168.21.1 (IPCONFIG on workstation
and server confirms the Default Gateway as 192.168.21.1)
Scope option "006 DNS Servers" is set as follows:
192.168.21.54 (DC #1 with DHCP & DNS)
192.168.21.112 (DC #2 with DNS)
192.168.21.171 (DC #3 with DHCP & DNS)
192.168.21.1 (Belkin Router)
The DNS Server forwarder "All other DNS domains" lists various ISP DNS
servers. At the end of this list I placed 192.168.21.1
If I shutdown the server and either statically assign an address to a
workstation or re-enable the DHCP server on the router, all works well.
What am I doing incorrectly?
Thanks much!
---
Bob
|
|
Bob <86c6c2e6-2146512712[ at ]news.postalias> wrote:
[Quoted Text] > Hi,
>
> I can't figure out why I can't ping my simple Belkin $50 router
> (which of course means I can't find the internet).
>
> My configuration is as follows:
>
> Router address is 192.168.21.1 and its DHCP server is disabled.
>
> I've three Windows 2003 Server DC's all of which have DNS Server and
> two have DHCP Server.
With non-overlapping scopes, one trusts!
>
> The DHCP Server's are configured has follows:
>
> Scope option "003 Router" is set for 192.168.21.1 (IPCONFIG on
> workstation and server confirms the Default Gateway as 192.168.21.1)
>
> Scope option "006 DNS Servers" is set as follows:
> 192.168.21.54 (DC #1 with DHCP & DNS)
> 192.168.21.112 (DC #2 with DNS)
> 192.168.21.171 (DC #3 with DHCP & DNS)
OK (although for reasons of tidiness, I suggest putting all your servers in
a contiguous/excluded block of IP addresses - as in, 192.168.21.10 - .20).
>> 192.168.21.1 (Belkin Router)
Get rid of this one.
>
> The DNS Server forwarder "All other DNS domains" lists various ISP DNS
> servers.
Various? You should probably have two - generally your ISP's.
> At the end of this list I placed 192.168.21.1
Get rid of that one. The only place your router's LAN IP should be
referenced is in the router/default gateway.
>
> If I shutdown the server and either statically assign an address to a
> workstation or re-enable the DHCP server on the router, all works
> well.
> What am I doing incorrectly?
If you can't ping your router's LAN IP, it has nothing to do with your AD
config (or DNS) - I suggest taking a look at the Belkin's config (does it
block inbound ICMP?) and perhaps reset it back to its defaults.
However, the above advice re DNS is worth taking. If your internal DNS isn't
set up right, AD won't work right.
>
> Thanks much!
>
> ---
> Bob
|
|
Hello Bob,
Thank you for using newsgroup!
Thanks for our MVP Lanwench's great suggestions.
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.
--------------------
| From: "Lanwench [MVP - Exchange]"
<lanwench[ at ]heybuddy.donotsendme.unsolicitedmailatyahoo.com>
| References: <uxHkmAkwHHA.5036[ at ]TK2MSFTNGP03.phx.gbl>
| Subject: Re: Can't ping router
| Date: Mon, 9 Jul 2007 13:59:52 -0400
| Lines: 65
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
| X-RFC2646: Format=Flowed; Response
| Message-ID: <eVOMuWlwHHA.3364[ at ]TK2MSFTNGP02.phx.gbl>
| Newsgroups: microsoft.public.windows.server.dns
| NNTP-Posting-Host: cpe-24-193-56-181.nyc.res.rr.com 24.193.56.181
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.dns:3964
| X-Tomcat-NG: microsoft.public.windows.server.dns
|
| Bob <86c6c2e6-2146512712[ at ]news.postalias> wrote:
| > Hi,
| >
| > I can't figure out why I can't ping my simple Belkin $50 router
| > (which of course means I can't find the internet).
| >
| > My configuration is as follows:
| >
| > Router address is 192.168.21.1 and its DHCP server is disabled.
| >
| > I've three Windows 2003 Server DC's all of which have DNS Server and
| > two have DHCP Server.
|
| With non-overlapping scopes, one trusts!
| >
| > The DHCP Server's are configured has follows:
| >
| > Scope option "003 Router" is set for 192.168.21.1 (IPCONFIG on
| > workstation and server confirms the Default Gateway as 192.168.21.1)
| >
| > Scope option "006 DNS Servers" is set as follows:
| > 192.168.21.54 (DC #1 with DHCP & DNS)
| > 192.168.21.112 (DC #2 with DNS)
| > 192.168.21.171 (DC #3 with DHCP & DNS)
|
| OK (although for reasons of tidiness, I suggest putting all your servers
in
| a contiguous/excluded block of IP addresses - as in, 192.168.21.10 - .20).
|
| >> 192.168.21.1 (Belkin Router)
|
| Get rid of this one.
|
| >
| > The DNS Server forwarder "All other DNS domains" lists various ISP DNS
| > servers.
|
| Various? You should probably have two - generally your ISP's.
|
| > At the end of this list I placed 192.168.21.1
|
| Get rid of that one. The only place your router's LAN IP should be
| referenced is in the router/default gateway.
|
|
| >
| > If I shutdown the server and either statically assign an address to a
| > workstation or re-enable the DHCP server on the router, all works
| > well.
| > What am I doing incorrectly?
|
| If you can't ping your router's LAN IP, it has nothing to do with your AD
| config (or DNS) - I suggest taking a look at the Belkin's config (does it
| block inbound ICMP?) and perhaps reset it back to its defaults.
|
| However, the above advice re DNS is worth taking. If your internal DNS
isn't
| set up right, AD won't work right.
|
| >
| > Thanks much!
| >
| > ---
| > Bob
|
|
|
|
|
|
Thanks Lanwench,
With your reassurance that this is a router problem and not my Windows
setup, that got me to look at the router once again and I found the stupid
problem. I had MAC address filtering enabled!
I'm a little confused about why you don't want any more than two forwarding
addresses and to not list the router as one of them?
I suspect the way DNS works is to try the first in the list and it works, go
no further. If it doesn't, try the next. If that's the case, then what's
the harm in having several DNS forwarders? Just a waste of time maybe?
I've found my Charter.net to loose its DNS servers about twice a year in
Newtown, CT.
The reason for including the router is that the router certainly knows what
the ISP DNS Servers are, but I don't know if it is recursive, so I guess
once Windows asks the router where xyz is, I don't know if the router would
continue on or what.
I didn't say, but my three DC's are in three sites on the same router and
therefore I'm using superscopes. That is why my servers are not in a
contiguous/excluded block of IP addresses. I also reserve addresses for the
workstations so I don't see a need to exclude any addresses. If a new
workstation comes online, it is welcome to grab what it can find.
Thanks for your help!
---
Bob.
|
|
|