Re: Yet another multisite VPN DNS question!
- From: Jason <Jason@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 18:21:00 -0700
Sure I don't mind! I'm all for digging around in places I may not have
checked already to see what could cause an issues like this. However I don't
have much of anything interesting to report in response to your questions :P
If I may jump in, look in DNS properties, Nameservers tab. Do you see the172.1.1.1 doesn't appear under any tabs in Properties under the zone for my
172.1.1.1 address anywhere? How about anywhere else in DNS properties? Also,
do you see a SID or GUID number instead of a server IP and name under the
Nameservers tab?
internal domain (and my external which I checked as well). Nor does it appear
under DNS properties in general, anywhere.
Cisco's method for configuring DHCP is actually pretty simple once you get
If you check each router's DHCP service, do you see it in there? How about
the router's interface configs, is it listed there?
to understand Cisco router programming a bit. I have three or four lines of
statements that configure DHCP for what will be given out to hosts, and
172.1.1.1 doesn't appear anywhere in that. In fact, I just configured this
router from scratch, and 172.1.1.1 doesn't appear anywhere at all in the
whole Cisco configuration!
The VPN is handled by IPSec tunnels between the Cisco routers and Linksys
Is a VPN (Windows RRAS or using your router's VPN service) in place using
that subnet or address anywhere?
routers I have across my network. 172.1.x.x isn't even a part of my network
design. Everything we use is 172.20.x.y, which I think I mentioned earlier. x
= location specific, y = host specific.
I appreciate both what Anthony has had me check on so far and your questions
Anthony has been very helpful. I was just thinking out loud with this one
and needed to ask, after reading your last post.
as well. Unfortunately I'm not sure where that EventID comes into play with
that IP address it tried to register with. Like I said in my last response,
other people who have gotten that ID had a similar x.1.1.1 address being
listed, despite that it wasn't a part of their network. I'm curious if this
is some sort of inherent bug or such that could cause the weird address to
appear for networks which don't even utilize that address scheme anywhere.
Again, I'm keeping an eye on things and will see if my DNS issues have gone
back to acting normally or if they'll crop back up.
Thanks again for everything so far, from both of you!
--Jason
.
- Follow-Ups:
- Re: Yet another multisite VPN DNS question!
- From: Ace Fekay [MVP]
- Re: Yet another multisite VPN DNS question!
- References:
- Yet another multisite VPN DNS question!
- From: Jason
- Re: Yet another multisite VPN DNS question!
- From: Anthony [MVP]
- Re: Yet another multisite VPN DNS question!
- From: Jason
- Re: Yet another multisite VPN DNS question!
- From: Anthony [MVP]
- Re: Yet another multisite VPN DNS question!
- From: Jason
- Re: Yet another multisite VPN DNS question!
- From: Anthony [MVP]
- Re: Yet another multisite VPN DNS question!
- From: Jason
- Re: Yet another multisite VPN DNS question!
- From: Anthony [MVP]
- Re: Yet another multisite VPN DNS question!
- From: Jason
- Re: Yet another multisite VPN DNS question!
- From: Ace Fekay [MVP]
- Yet another multisite VPN DNS question!
- Prev by Date: Re: Wide area failures?
- Next by Date: Re: Yet another multisite VPN DNS question!
- Previous by thread: Re: Yet another multisite VPN DNS question!
- Next by thread: Re: Yet another multisite VPN DNS question!
- Index(es):
Relevant Pages
|