Probably what happened was the client tried to renew its existing IP. The
rogue server responded and had that address available. So, it was more than
happy to hand it out - along with the wrong DNS IP. Go get 'em, Luis!
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Luis R." <(E-Mail Removed)> wrote in message
news:1A00A73A-32D4-4E18-9701-(E-Mail Removed)...
> Yes, it seems to be that problem. The strange thing about it is that
the
> ip configuration was mixed, for example, the ip address from the real DHCP
> and the DNS from the other one.
>
> Thanks for all your help.
>
> "Doug Sherman [MVP]" escribió:
>
> > Are you sure the affected clients are getting a lease from your DHCP
server?
> > My first thought would be a rogue server - perhaps a router with DHCP
> > enabled.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Luis R." <(E-Mail Removed)> wrote in message
> > news:89D8A9E3-FC68-422E-9620-(E-Mail Removed)...
> > > I would like to know if anybody knows about a problem with DHCP. Our
> > DHCP
> > > server is configured, for example, with two DNS servers, 192.168.30.11
and
> > > 192.168.30.16. But, when some clients try to renew their ip
> > configuration,
> > > they received from the server the DNS 192.168.1.1. I looked up in
the
> > event
> > > viewer and nothing wrong appears. I restart the DHCP service and the
> > same.
> > >
> > > Anybody has any idea about this strange behavior? Thanks for all
your
> > help.
> > >
> >
> >
> >
|