[Openvpn-users] DHCP Server sent a DHCPNACK message ???

[Michael D Schleif]

I have setup a Windows client like this:

<http://openvpn.net/howto.html#windows>

Yes, it works, and I do NOT have any functionality issues.

However, the System EventLog has the following message every time that
OpenVPN starts up:

Source: Dhcp
Event ID: 1002
Type: Error

The IP address lease 10.255.1.1 for the Network Card with network
address 00FFF5F07327 has been denied by the DHCP server 10.255.1.9
(The DHCP Server sent a DHCPNACK message).

If this event was not RED, I may not worry; but, we pride ourselves in
running event-less windows boxes. Nor have I successfully googled any
similar experiences.

What do you think?
--
Best Regards,

mds
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--

[Kay Wischkony]

Post by Michael D Schleif
However, the System EventLog has the following message every time that
Source: Dhcp
Event ID: 1002
Type: Error
The IP address lease 10.255.1.1 for the Network Card with network
address 00FFF5F07327 has been denied by the DHCP server 10.255.1.9
(The DHCP Server sent a DHCPNACK message).

I am seeing this too.

K
W

[James Yonan]

Post by Michael D Schleif
<http://openvpn.net/howto.html#windows>
Yes, it works, and I do NOT have any functionality issues.
However, the System EventLog has the following message every time that
Source: Dhcp
Event ID: 1002
Type: Error
The IP address lease 10.255.1.1 for the Network Card with network
address 00FFF5F07327 has been denied by the DHCP server 10.255.1.9
(The DHCP Server sent a DHCPNACK message).
If this event was not RED, I may not worry; but, we pride ourselves in
running event-less windows boxes. Nor have I successfully googled any
similar experiences.

There are cases where it is perfectly reasonable to send a DHCPNACK
message -- such as when you want the client to reset its state and begin a
new negotiation. When OpenVPN is running in "ip-win32 dynamic" mode (the
default on Windows), the TAP-Win32 driver will emulate a DHCP server. You
can use another ip-win32 mode to eliminate DHCP messages altogether. I
also take issue with Windows logging a DHCP NACK as an error condition.
Suppose a DHCP server wants to give a client a new IP address, and doesn't
want to let the old lease be renewed. You need DHCP NACK for this, and in
this context, it shouldn't be considered an error.

James