DHCPNAK

Mark Damrose mdamrose at elgin.cc.il.us
Mon Jan 28 18:35:53 UTC 2002


I have never had a problem like that.

Do you reboot your machine when you move from 1 segment to another, or just
expect that it should work?

You could force the client to give up its lease with
ipconfig /release
ipconfig /renew

If that doesn't work, try the DHCP server mailing list.
http://www.isc.org/services/public/lists/dhcp-lists.html  This is for the
BIND DNS server.

"Alaa Alamood" <aaa at netman.dk> wrote in message
news:a33mu6$et at pub3.rc.vix.com...
>
> Hi
>
> I have problem between dhcp server and dhcp client windows 2k, that when
> the client has been used in onther network, can not get new IP
> address and it try until it give op, the log file in the server side it
> look like the following
>
>
> Jan 28 08:38:30 cluster1 dhcpd: DHCPNAK on 192.168.1.6 to
> 00:d0:59:2a:e4:70 via tu1
> Jan 28 08:38:34 cluster1 dhcpd: DHCPREQUEST for 192.168.1.6 from
> 00:d0:59:2a:e4:70 via tu1: wrong network
> .
> Jan 28 08:38:34 cluster1 dhcpd: DHCPNAK on 192.168.1.6 to
> 00:d0:59:2a:e4:70 via tu1
> Jan 28 08:38:42 cluster1 dhcpd: DHCPREQUEST for 192.168.1.6 from
> 00:d0:59:2a:e4:70 via tu1: wrong network
> .
> Jan 28 08:38:42 cluster1 dhcpd: DHCPNAK on 192.168.1.6 to
> 00:d0:59:2a:e4:70 via tu1
> Jan 28 08:39:04 cluster1 dhcpd: DHCPDISCOVER from 00:d0:59:2a:e4:70
> (MOBILE-CHP) via tu1
> Jan 28 08:39:05 cluster1 dhcpd: DHCPOFFER on 172.16.0.189 to
> 00:d0:59:2a:e4:70 (MOBILE-CHP) via tu1
> Jan 28 08:39:08 cluster1 dhcpd: DHCPDISCOVER from 00:d0:59:2a:e4:70
> (MOBILE-CHP) via tu1
> Jan 28 08:39:08 cluster1 dhcpd: DHCPOFFER on 172.16.0.189 to
> 00:d0:59:2a:e4:70 (MOBILE-CHP) via tu1
>
>
> does any one have a good idea what's going on and what should I do to
> solve the problem
>
> regrads
> Alaa
>
>
>




More information about the bind-users mailing list