Re: Can't ping router
- From: "Bob" <86c6c2e6-2146512712@xxxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 15:57:33 -0400
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.
.
- Follow-Ups:
- Re: Can't ping router
- From: Lanwench [MVP - Exchange]
- Re: Can't ping router
- References:
- Can't ping router
- From: Bob
- Re: Can't ping router
- From: Lanwench [MVP - Exchange]
- Can't ping router
- Prev by Date: Re: DHCP server non domain member
- Next by Date: Re: recursive query fails
- Previous by thread: Re: Can't ping router
- Next by thread: Re: Can't ping router
- Index(es):
Relevant Pages
|