Client can't find DHCP server

[jsa500]

Hi,
My LAN comprises of only 2 computers, one running WinGate server and the other is the client. The client has NETBIOS name BOND. I keep getting the following message on the server:

ID OBJECT USER

0602 DHCP service SYSTEM

Client BOND denied access - non private address allocation denied

The IP address of BOND is an APIPA, not static. If I try and renew using ipconfig /renew then ipconfig says something like "Error: Can't find your DHCP server". I've also tried re-booting the client, it assigns itself an APIPA again.

My NICs are by RealTech. I read there were issues with these NICS
on one version of WinGate. With respect to today's date I have the latest version of WinGate installed.

Any ideas?

[Pascal]

Issue is not with the version of WinGate, but with a specific version of the Realtek chipset and drivers. It should only affect you if your card is based on the 8029 chipset, and there is a workaround in the "Advanced Options" program.

What is the setup like on the server? What IP Addresses do you have bound to the DHCP service?

Have you double checked that your adapters are setup correctly in GateKeeper (Internal vs External).

[jsa500]

Hi,

169.254.0.1 and 169.254.19.180 are bound to DHCP on port 67.

169.254.0.1 is the IP of the NIC on the server that connects the client machine.

169.254.19.180 is bound to Local Area Connection 4 (something that AOL installs, don't know why)

Binding Policy:

Bind to any IP address on any internal adaptor, is selected

I've checked the adaptor setup on the server and it is selected as internal. I don't know how to check this on the client though...

Something else interesting. If I set the client a static address of 169.254.0.2 and a gateway of 169.254.0.1 it works, but then I get a system message on the server saying that ATHLON has been denied access - nonprivate address allocation denied.

ATHLON is the NETBIOS name of the server, strange huh?

[Nev]

Hi,

169.254.0.1 and 169.254.19.180 are bound to DHCP on port 67.

169.254.0.1 is the IP of the NIC on the server that connects the client machine.

169.254.19.180 is bound to Local Area Connection 4 (something that AOL installs, don't know why)

Binding Policy:

Bind to any IP address on any internal adaptor, is selected

I've checked the adaptor setup on the server and it is selected as internal. I don't know how to check this on the client though...

Something else interesting. If I set the client a static address of 169.254.0.2 and a gateway of 169.254.0.1 it works, but then I get a system message on the server saying that ATHLON has been denied access - nonprivate address allocation denied.

ATHLON is the NETBIOS name of the server, strange huh?

Hi,

Ip range 169.254.x.x is the default assignment when DHCP is unavailable.

Try moving to a private range of 10.10.x.x or 192.168.0.1 & 192.168.0.2

Report back how it goes!

Nev.