Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

New Reservation for client does not match IP!!

Apr 17 04 9:20 am

I recetly upgrade to 5.2.3 and am now having problems binding IP addresses with one of my clients. I turned on DHCP debug logging and am seeing the following error message for each RENEW attempt:

New Reservation for client solomon does not match IP

I took this client off of the network and attached it directly to a Linksys cable modem router and it was immediately served an IP address. Therefore I was able to determine that the problem clearly was with the Wingate DHCP server.

Is there a way to clear the DHCP lease history for Wingate?

While I'm at it, I have also noticed that if I reboot the Wingate PC (running Win2000), none of the clients get access to the internet unless I disable and re-enable the firewall first.

AND...I find that PureSight is no longer blocking sex web sites any longer.

What is going wrong????

-Bill

Apr 17 04 7:03 pm

Hi

To clear the DHCP lease history you would need to edit the registry.

1. Stop the engine
2. edit the key HKEY_LOCAL_MACHINE\Softare\Qbik Software\WinGate\DHCP\Leases

You can delete whichever keys in there you like, and that will make WinGate forget about that lease. However, that error looks like an issue with whatever IP address the client is requesting. Basically if we have a reservation for a computer, but it requests a different IP (DHCP clients nowadays often request the last IP they had), then WinGate logs this message, and sends a NACK back to the client. The client then SHOULD simply make another request not setting its requested DHCP address.

As for PureSight, you mean it no longer blocks sites it used to? We have found some sites change the way they operate, and since PureSight uses a heuristic method to determine whether a page is likely to contain content of a certain type, it can be fooled. In fact the next version of PureSight (which we are looking at at the moment) seems to have moved to a list-based approach, rather than trying to figure it out automatically.

So in the end, you may have to add the site to a block list anyway.

Adrien
Post a reply