> OK  learning a bit here and there.
> 
> Mark - I only have one DHCP server running.  Good idea though
> 
> It appears that the DHCP server is in fact only leasing IP addresses from 
> 192.168.1.50 which is the new setting I gave it.  Good news!
> 
> Thew problem is that the clients - and perhaps the DHCP server as well, are 
> caching or hanging on to their “old” IP addresses, and not asking the DHCP 
> server for a new on!
> 
> I have forced a windows 10 machine to get a new IP address - using 
> 
> ipconfig /release  
> net stop dhcp  
> net start dhcp 
> ifconfig /renew
> 
> Windows complained bitterly but a reboot fixed that!  Good news
> 
> My Android has sorted itself, as has an iMac, but my iPad and another Android 
> all refuse to play ball despite switching off, restarting, telling the iPad 
> to renew lease etc.  
> 
> My router appears not to have the ability to release IP addresses on demand, 
> or to have a clear out mechanism - scavenging I believe.  
> 
> I will be able to leave the router turned off for a few days, and perhaps 
> that might reset the lease time.
> 
> I shall wait and see.
> 
> 
> 
> 
> Edward Kerr
> ————————
> 
> 
> 
>> On 24 Oct 2016, at 10:49, Mark Rogers via Peterboro 
>> <peterboro@mailman.lug.org.uk <mailto:peterboro@mailman.lug.org.uk>> wrote:
>> 
>> On 22 October 2016 at 15:14, Edward Kerr via Peterboro 
>> <peterboro@mailman.lug.org.uk <mailto:peterboro@mailman.lug.org.uk>> wrote:
>> All my DHCP machines are still being given IP address below .50 and above 
>> .10  i.e. no change.  
>> 
>> You say "still being given" but have you confirmed that these are new leases 
>> issued since you updated the router, not old ones that pre-date the change?
>> 
>> In Linux you should find any lease information, including when it was 
>> obtained and when it expires, in /var/lib/dhcp/dhclient*.leases . On 
>> Windows, "ipconfig /all" should tell you.
>> 
>> If your lease is a new one but still wrong, then the next thing to check is 
>> that it is coming from your router, which you can verify in the same places. 
>> I think it's unlikely that you have two DHCP servers running coincidentally 
>> on the same subnet range, but I don't know your network and it's not 
>> impossible!
>> 
>> Note that when a device requests a new lease it will usually request the 
>> address it already have (it's up to the server to re-issue the same address 
>> or a new one); it might be that the server is re-issuing leases to existing 
>> addresses and only using the settings for new requests rather than renewals. 
>> Pretty unlikely though. 
>> 
>> Mark
>> -- 
>> Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450
>> Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER
>> _______________________________________________
>> Peterboro mailing list
>> Peterboro@mailman.lug.org.uk <mailto:Peterboro@mailman.lug.org.uk>
>> https://mailman.lug.org.uk/mailman/listinfo/peterboro
> 

_______________________________________________
Peterboro mailing list
Peterboro@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/peterboro

Reply via email to