Re: Weirdest behaviour - dns or active directory?
- From: "Steve Duff [MVP]" <ergodic@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 17:58:38 -0700
The ping result seems entirely expected - you are routing 192.168 to the default gateway, and your ISP is rejecting the address,
which they should. After that ICMP message nothing more will happen.
I would try simply de-authorizing and re-authorizing your DHCP server in the server's DHCP snap-in again. Then run a netdiag /fix
and dcdiag /fix on both servers to clean up any lingering configuration problems. Check in Routing and Remote Access if it is
enabled - it can run its own DHCP, and you may have a 192.168.x.x reference or two left in there.
If none of that fixes it, go to netsh...dhcp...show...\\192.168.1.2, and see if it can display ("show") any of the properties for
the phantom server. If all else fails you can look with adsiedit.
Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
"pscyime" <pscyime.1rglaa@> wrote in message news:ReWdnerFRtKI-lnfRVn_vg@xxxxxxxxxxxxxxx
>
> Hi People
>
>
> I have 2 dcs both run dns and one runs dhcp (dhcp server 10.0.0.2)
>
> when i run the following command on my DC DHCP server one
>
> netsh dhcp show server
>
> it reports 2 dhcp servers called server01.mydomain.local (my only DHCP
> server with ip 10.0.0.2 and another with another private ip
> 192.168.1.2)
>
> i changed the ip of the dhcp server from 192.168.1.2 to the 10.x.x.x
> range like a month ago but it appears that there is still a reference
> to it
>
> I guess this is more of an active directory thing as it says the
> records were found in the directory service the really weird thing is
> that if you ping that now non exitant 192.x.x.x ip address you DO get
> one response but it is from my WAN ip reporting net unreachable- now
> what on earth is going on there? the other 3 packets sent by ping fail
> to come back
>
> I have pasted the result of the above netsh command and the result of a
> ping - can anyone please explain what is going on here and also how can
> i remove the old 192.x.x.x dhcp server from the directory THIS IS WHAT I
> REALL NEED TO KNOW
>
> C:\Documents and Settings\manager>netsh dhcp show server
>
> 2 Servers were found in the directory service:
>
> Server [server01.mydomain.local] Address [10.0.0.2] Ds
> location: cn=10.0.0.2
>
> Server [server01.mydomain.local] Address [192.168.1.2] Ds
> location: cn=192.168.1.2
>
> Command completed successfully.
>
> C:\Documents and Settings\manager>ping 192.168.1.2
>
> Pinging 192.168.1.2 with 32 bytes of data:
>
> Request timed out.
> Reply from 83.146.17.222: Destination net unreachable.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.1.2:
> Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>
> Does anyone know if this record in AD will cause a problem? have
> checked and there is nothing i can see relating to this old server
>
> there is probably a simple explanation but where is it?
>
> thanks in advance
>
> Simon
>
>
> --
> pscyimePosted from http://www.pcreview.co.uk/ newsgroup access
>
.
- Follow-Ups:
- Re: Weirdest behaviour - dns or active directory?
- From: pscyime
- Re: Weirdest behaviour - dns or active directory?
- From: pscyime
- Re: Weirdest behaviour - dns or active directory?
- References:
- Weirdest behaviour - dns or active directory?
- From: pscyime
- Weirdest behaviour - dns or active directory?
- Prev by Date: Weirdest behaviour - dns or active directory?
- Next by Date: Re: Active Directory, DNS, and ISP hosted domains
- Previous by thread: Weirdest behaviour - dns or active directory?
- Next by thread: Re: Weirdest behaviour - dns or active directory?
- Index(es):
Relevant Pages
|
|
