DHCP Problems

[psicoz]

Hello,

A few weeks ago we bought a license Firstspot 606 advanced edition which is giving us many problems in the network it manages.

As we have seen, the main problem is that suddently DHCP assigns IP addresses wrong.

Firstspot is running on a clean installation of Windows 2003 Server with no antivirus or firewall.

The card connected to the hotspot has the address 192.168.2.1

when it works well assigns addresses like 192.168.2.x but there comes a time when starts assigning addresses such 192.168.11.X

We've gone crazy trying to solve the problem but there is no way ... Could you give us some idea? we do not know where to look ...

Thanks in advance and best regards.

[chrisli]

Please reproduce your problem again?

client (which get the wrong ip address eg. 192.168.11.X)
- run ipconfig/release
- run ipconfig/renew
- run ipconfig/all


Can you zip and email us your :

1) firstspot_DHCP_(timestamp).log file which under [FirstSpot directory]\log,
2) dhcpservice.ini which under [FirstSpot directory]\dhcp,
3) ipconfig/all text output of your client

to firstspot@patronsoft.com
_________________
~ Patronsoft Limited ~

[psicoz]

Hello again

- run ipconfig/release
- run ipconfig/renew
- run ipconfig/all

that don't work in client laptop

I have sent the information you requested

thank you in advance and best regards

[dominic]

Having checked the information you've sent us, FirstSpot DHCP Server didn't contain any lease record of either 192.168.11.x or the client MAC address. Futhermore, the DHCP log only shown up to 12:27 while the client obtained the IP 192.168.11.17 at 12:35.

Please double check whether the client attached to the correct AP. After that, executing the following in Command Prompt should help to obtain correct IP:
ipconfig /release
ipconfig /renew

[psicoz]

Hello,

yes it's true, the client obtained the ip at 12:35 but if you take a look to the DHCP log you could see several incorrect ip's such:

05/07/2010 10:14:21 ---> (ObtainPoolIP) 3: Client requests address [192.168.11.10]

05/07/2010 10:14:21 ---> (Run) 4: requested_address [192.168.11.10]

05/07/2010 10:25:52 ---> (Run) 1: requested_address [192.168.11.10]

05/07/2010 10:58:07 ---> (Run) 6: requested_address [192.168.11.10]

05/07/2010 11:06:18 ---> (Run) 0: requested_address [192.168.11.6]

05/07/2010 11:20:44 ---> (Run) 2: requested_address [192.168.11.8]

05/07/2010 11:24:39 ---> (Run) 4: requested_address [192.168.11.8]

and more...

and as I said before, running

ipconfig /release
ipconfig /renew

doesn't work.

Thank you.

[dominic]

Yes, and as I said before, we've checked the information you've sent.

If you're interested in investigating the log, the following are several lines right after your examples respectively (MAC addresses are removed):

05/07/2010 10:14:21 ---> (ObtainPoolIP) 3: Random IP address NOT FOUND, offer a new IP
05/07/2010 10:14:21 ---> (Delete Node) 3: next != NULL
05/07/2010 10:14:21 ---> (ObtainPoolIP) 3: Router[0], Auto config IP = 192.168.2.157, Order Type = 0

05/07/2010 10:14:21 ---> (LookupClientData) Client [...] configured IP [192.168.2.157]
05/07/2010 10:14:21 ---> (ProcessRequest) 4: Reject request because client asks for another address
05/07/2010 10:14:21 ---> (ProcessRequest) 4: ipaddr!=requested_address, PrepareNegativeResponse

05/07/2010 10:25:52 ---> (LookupClientData) Client [...] configured IP [192.168.2.157]
05/07/2010 10:25:52 ---> (ProcessRequest) 1: Reject request because client asks for another address
05/07/2010 10:25:52 ---> (ProcessRequest) 1: ipaddr!=requested_address, PrepareNegativeResponse

05/07/2010 10:58:07 ---> (LookupClientData) Client [...] configured IP [192.168.2.157]
05/07/2010 10:58:07 ---> (ProcessRequest) 6: Reject request because client asks for another address
05/07/2010 10:58:07 ---> (ProcessRequest) 6: ipaddr!=requested_address, PrepareNegativeResponse

05/07/2010 11:06:18 ---> (LookupClientData) Client [...] configured IP [192.168.2.22]
05/07/2010 11:06:18 ---> (ProcessRequest) 0: Reject request because client asks for another address
05/07/2010 11:06:18 ---> (ProcessRequest) 0: ipaddr!=requested_address, PrepareNegativeResponse

05/07/2010 11:20:44 ---> (LookupClientData) Client [...] configured IP [192.168.2.18]
05/07/2010 11:20:44 ---> (ProcessRequest) 2: Reject request because client asks for another address
05/07/2010 11:20:44 ---> (ProcessRequest) 2: ipaddr!=requested_address, PrepareNegativeResponse

05/07/2010 11:24:39 ---> (LookupClientData) Client [...] configured IP [192.168.2.18]
05/07/2010 11:24:39 ---> (ProcessRequest) 4: Reject request because client asks for another address
05/07/2010 11:24:39 ---> (ProcessRequest) 4: ipaddr!=requested_address, PrepareNegativeResponse

The above shows that FirstSpot DHCP Server was trying to offer 192.168.2.x and was rejecting DHCP renew requests for those 192.168.11.x.

If what you mean by "doesn't work" after running the commands is the client still obtained 192.168.11.x, most likely there's another DHCP server offering that segment of IPs and your clients preferred to accept those offers. Please really double check this.

[psicoz]

Hello,

You were right. After reviewing all the ap's I have found a device that was not working properly.

Thanks for everything and best regards.