DHCP Service

[edumelres]

I have active the DHCP Mode Full automatic and DHCP Settings(the allocate ip), but don´t work, the clients don´t have the range ip?

[MattP]

Hi,

WinGate will assign IP addresses based on the IP address of the INTERNAL adapter. You should check your adapter settings on the network tab in GateKeeper, your LAN adapter should be marked as INTERNAL and your Internet adapter should be marked as EXTERNAL. If you need to change an adapter's settings just double click it and select the appropriate radio button.

We recommend using a private IP address range on your LAN, if you use a public IP address range then WinGate will assume that the adapter is an EXTERNAL adapter. What IP address range are you using on your LAN?

Can you open a DOS window on a client machine and run an IPCONFIG/ALL command? Does the machine show the WinGate server as the DHCP server? If so, what is the IP address and the default gateway set to?

Thanks,

Matt

[edumelres]

I have the internal(server) and external(modem) configured, and the server ip is 192.168.0.11, then i see the client IPCONFIG/ALL.but the client in the Local netwok is 169.254.xxx.xxx

[Nev]

I have the internal(server) and external(modem) configured, and the server ip is 192.168.0.11, then i see the client IPCONFIG/ALL.but the client in the Local netwok is 169.254.xxx.xxx

If so, what is the IP address and the default gateway set to?

Hi,

As Matt says set the IP address for the server [192.168.0.11] as the 'default gateway' on a client then run ipconfig /release and ipconfig /renew to see if a DHCP address is served.

[edumelres]

in client i put gateway 192.168.0.11 , in the ipconfig/all appear DHCP service NO

[MattP]

Ok, now set it back to DHCP and see if it picks up an IP address.

169.254.*.* is the auto-net address which means that your machine was not able to connect to a DHCP server to get an IP address. If you continue to have problems with obtaining an IP address by DHCP then you should check that there are no problems connecting to the WinGate server from the clients. Is there a personal firewall running on the WinGate server that could be blocking the broadcast request from the client machine?

Matt

[edumelres]

Matt , if i configure manual, the client run great, in the server i have a windows firewall of windows xp only, and i have disable the extending network in wingate(to see the details activity).

[Nev]

Matt , if i configure manual, the client run great, in the server i have a windows firewall of windows xp only, and i have disable the extending network in wingate(to see the details activity).

Hi,

Well if you want to see the user activity [I assume via proxy] then there is a way using Wingate's Nat and Firewall, this may sort out your DHCP fault perhaps.

* Disconnect from the Internet and re-install Wingate enabling NAT then reboot.

* Check that NAT is enabled and running.

* Disable XP's ICS / Firewall service then stop the service.

* Check the adaptor usage in Wingate's Network tab for 'External to Internet / Internal to Clients.

* In the WWW Proxy Service enable Transparent Redirection, this will allow you to view the NAT web traffic passing through by the Proxy.

* Connect to the Internet and try DHCP Clients for an IP again.