What's new

Multiple entries in log allocating the same ip to the same computer

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Smokin_Joe

Regular Contributor
I have a number of students staying in my home and they all access the internet through an AP designated to each individual students use. They are all separated by hardware wired to a managed switch.
I am trying to find ways to make my network to be reliable and high speed.
The following is an example of the log in my router.
These multiple allocations to the same computer can go into the hundreds.
It is a windows 11 computer and I am looking for ways to stop it from doing this.
Where should I start?
Why does, this computer, keep doing this and yet able to preform as if nothing is wrong from the students perspective?
7 2023-05-30 21:59:22 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
8 2023-05-30 21:59:23 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
9 2023-05-30 21:59:32 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
10 2023-05-30 21:59:33 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
11 2023-05-30 22:00:02 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
12 2023-05-30 22:00:03 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
13 2023-05-30 22:09:31 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
14 2023-05-30 22:09:33 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
15 2023-05-30 22:09:34 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
16 2023-05-30 22:09:35 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
17 2023-05-30 22:09:51 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
18 2023-05-30 22:09:52 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
19 2023-05-30 22:10:29 <5> : DHCP Server allocated IP address 192.168.1.124 for the client from LAN port.
20 2023-05-30 22:32:44 <5> : DHCP Server allocated IP address 192.168.1.125 for the client from LAN port.
21 2023-05-30 22:32:47 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
22 2023-05-30 22:32:50 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
23 2023-05-30 22:34:04 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
24 2023-05-30 22:34:05 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
25 2023-05-30 22:34:22 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
26 2023-05-30 22:34:25 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
27 2023-05-30 22:35:10 <5> : DHCP Server allocated IP address 192.168.1.127 for the client from LAN port.
28 2023-05-30 22:35:17 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
29 2023-05-30 22:35:57 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
30 2023-05-30 22:36:21 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
31 2023-05-30 22:36:30 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
32 2023-05-30 22:39:27 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
33 2023-05-30 22:39:39 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
34 2023-05-30 22:40:37 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
35 2023-05-30 22:40:38 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
36 2023-05-30 22:41:03 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
37 2023-05-30 22:41:04 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
38 2023-05-30 22:41:38 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
39 2023-05-30 22:41:39 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
40 2023-05-30 22:41:40 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
41 2023-05-30 22:41:49 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
42 2023-05-30 22:41:53 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
43 2023-05-30 22:41:56 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
44 2023-05-30 22:41:57 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
45 2023-05-30 22:47:26 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
46 2023-05-30 22:47:29 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
 
I have a number of students staying in my home and they all access the internet through an AP designated to each individual students use. They are all separated by hardware wired to a managed switch.
I am trying to find ways to make my network to be reliable and high speed.
The following is an example of the log in my router.
These multiple allocations to the same computer can go into the hundreds.
It is a windows 11 computer and I am looking for ways to stop it from doing this.
Where should I start?
Why does, this computer, keep doing this and yet able to preform as if nothing is wrong from the students perspective?
7 2023-05-30 21:59:22 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
8 2023-05-30 21:59:23 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
9 2023-05-30 21:59:32 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
10 2023-05-30 21:59:33 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
11 2023-05-30 22:00:02 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
12 2023-05-30 22:00:03 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
13 2023-05-30 22:09:31 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
14 2023-05-30 22:09:33 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
15 2023-05-30 22:09:34 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
16 2023-05-30 22:09:35 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
17 2023-05-30 22:09:51 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
18 2023-05-30 22:09:52 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
19 2023-05-30 22:10:29 <5> : DHCP Server allocated IP address 192.168.1.124 for the client from LAN port.
20 2023-05-30 22:32:44 <5> : DHCP Server allocated IP address 192.168.1.125 for the client from LAN port.
21 2023-05-30 22:32:47 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
22 2023-05-30 22:32:50 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
23 2023-05-30 22:34:04 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
24 2023-05-30 22:34:05 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
25 2023-05-30 22:34:22 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
26 2023-05-30 22:34:25 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
27 2023-05-30 22:35:10 <5> : DHCP Server allocated IP address 192.168.1.127 for the client from LAN port.
28 2023-05-30 22:35:17 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
29 2023-05-30 22:35:57 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
30 2023-05-30 22:36:21 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
31 2023-05-30 22:36:30 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
32 2023-05-30 22:39:27 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
33 2023-05-30 22:39:39 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
34 2023-05-30 22:40:37 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
35 2023-05-30 22:40:38 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
36 2023-05-30 22:41:03 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
37 2023-05-30 22:41:04 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
38 2023-05-30 22:41:38 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
39 2023-05-30 22:41:39 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
40 2023-05-30 22:41:40 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
41 2023-05-30 22:41:49 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
42 2023-05-30 22:41:53 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
43 2023-05-30 22:41:56 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
44 2023-05-30 22:41:57 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
45 2023-05-30 22:47:26 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.
46 2023-05-30 22:47:29 <5> : DHCP Server allocated IP address 192.168.1.109 for the client from LAN port.

If it is just one computer (and the rest connected in the same way are not having the issue) something on that PC seems broken. However it is possible something in your managed switch is messed up and the response is never making it back to that computer, so it keeps trying over and over. Why one AP per student? That seems overkill, a guest network will keep them isolated from each other and should be plenty of bandwidth. You may actually be doing more harm than good having multiple APs in close proximity.

What happens if you hardwire that PC to the switch or directly to the router? If it still happens, it is a PC issue, perhaps firewall interfering with the DHCP communication. If not, then try hardwiring it to the switch. If issue happens, some setting on the switch is messing it up. If not, then it is a setting in the AP.
 
"If it is just one computer (and the rest connected in the same way are not having the issue) something on that PC seems broken."
My thoughts exactly..drinkingbird...
But what specifically could be causing it?
 
"If it is just one computer (and the rest connected in the same way are not having the issue) something on that PC seems broken."
My thoughts exactly..drinkingbird...
But what specifically could be causing it?

There are many possibilities, testing as I mentioned will help narrow it down. Could be a firewall on the device improperly blocking the DHCP traffic.
 
Pluggin it in won't be an option.
Router is not wireless.
Plugging in someone else's equipment is not a risk I wish to take.
Connecting to another AP is an option.

Wonder if power settings on computer could be causing this?
 
Pluggin it in won't be an option.
Router is not wireless.
Plugging in someone else's equipment is not a risk I wish to take.
Connecting to another AP is an option.

Wonder if power settings on computer could be causing this?

Power settings would only cause that if it was set to go to sleep every few seconds. My only other guess is that it is having a weak signal (or maybe some other issue with the wireless card/driver in the PC), are you seeing any wireless disconnect/reconnects in the log of the AP in question? You would think they would notice, but never know. If you are not able to plug it in to test, then the next step is to check the logs on the AP and the PC.
 
On a tangent, that one computer could be using a "killer" version of an Intel wifi card along with the killer drivers. I'm not 100% but using Intel drivers with these can calm things down a lot.
/tangent
 
Only log entries in the AP (TL-WA901ND) is info entries of Startup,alg types and initialization...nothing about any devices connecting
Ripshod...I will be setting up my laptop on Sunday, to test all the AP's and have a look at this problematic computer..
I was thinking about deleting the Wifi on their computer and reinstalling it.
Also have a look at the services and apps they are running
Drinkingbird..I will see if I can find any answers in it's logs..
Thanks..
 
Pluggin it in won't be an option.
Router is not wireless.
Plugging in someone else's equipment is not a risk I wish to take.
Connecting to another AP is an option.

Wonder if power settings on computer could be causing this?
If you are in the same network then I am not sure you are helping your security. If you run a separate VLAN then you are secure wire or wireless.
Be careful plugging in a wireless router as you may be securing the inter-most router.
 
I have a number of students staying in my home and they all access the internet through an AP designated to each individual students use. They are all separated by hardware wired to a managed switch.

An access point for each student - or is this a dedicated AP that all the students share...

Just asking
 
I also want to know more about this designated to each individual student AP solution.
 
Only log entries in the AP (TL-WA901ND) is info entries of Startup,alg types and initialization...nothing about any devices connecting
Ripshod...I will be setting up my laptop on Sunday, to test all the AP's and have a look at this problematic computer..
I was thinking about deleting the Wifi on their computer and reinstalling it.
Also have a look at the services and apps they are running
Drinkingbird..I will see if I can find any answers in it's logs..
Thanks..

Hm not sure if you can bump up the log level in that AP? Really need to see if the client is losing its connection repeatedly. Can probably also get that info from event viewer on the PC itself.

Maybe that AP is faulty, have you tried that same PC on another AP?
 
Dedicated ap for each guest..
Modem>guest network router>managed enterprise level switch>6 different poe ap's one on each port.
Each port could be adjusted for bandwidth etc.
Too many settings for me, on switch, most disabled...lol
To expand on the network...
Modem (fibre)>Guest router>VPN router subneted to guest>Home router subneted to vpn all subnets outside managed switch..
From Home I can see everything on all the other routers, switches and ap's
Connected to guest, vpn, or local coffee shop:D... I cannot access home network.
Safe as I can make it
 
Hm not sure if you can bump up the log level in that AP? Really need to see if the client is losing its connection repeatedly. Can probably also get that info from event viewer on the PC itself.

Maybe that AP is faulty, have you tried that same PC on another AP?
I will be testing it on another ap this Sunday.
Long ago the guest was using a different ap with no issues..got a new phone and started having issues..
Changed to older gen ap and issues stopped with new phone..
He wanted the current ap
Can't say, for sure, when the high number of log entries for the DCHP on this computer started.
Sunday I will be testing all ap's with my laptop.
Current ap is older gen..tp link TL-WA901ND
 
One AP can broadcast 6 different VLAN separated SSIDs.
Old school, I know nothing, but I do what I can kinda guy feels that if you separate things via hardware instead of witchcraft (lol) you are more likely to pinpoint causes & solutions to issues you are trying to find.
A perfectly running computer folding at home of a rate of 20 million points per day can be brought down by an unwanted windows (witchcraft) update.
The more we know the more we don't know...:)
I am sure hackers can get around software based config more easily than hardware based config..
(not to mention the bottlenecks caused by using one AP)
 
if you separate things via hardware

It's basically the same thing. You just have 6x wires to the switch with VLANs and 6x more hardware used.
 
It's basically the same thing. You just have 6x wires to the switch with VLANs and 6x more hardware used.
No..not quite from a suffering point of view
If one guest takes your Ap out they all suffer...including you
One guest takes out a perfectly good ap, in my system, then takes out a brand new ap...then runs perfectly well on an old ap with DD WRT installed ...the only people who suffer is that one guest...oh and me too:eek:
Ka peesh?
This happened recently and is not the computer that is needing DCHP attention endlessly
Still don't know why she was able to disable two ap's
 
Last edited:
If one guest takes your Ap out they all suffer...

Bandwidth limiter per VLAN/SSID. You don't have 6x 80MHz wide channels available anyway. The APs on the same channel share the bandwidth. Interesting approach solving an issue with adding more hardware, perhaps a result of hardware choice limitations. I see it as unnecessary Wi-Fi pollution from 6x (or perhaps 12x) radios working in close proximity. Nothing wrong with it since it's unlikely you're one of my neighbors. :)
 
Bandwidth limiter per VLAN/SSID. You don't have 6x 80MHz wide channels available anyway. The APs on the same channel share the bandwidth. Interesting approach solving an issue with adding more hardware, perhaps a result of hardware choice limitations. I see it as unnecessary Wi-Fi pollution from 6x (or perhaps 12x) radios working in close proximity. Nothing wrong with it since it's unlikely you're one of my neighbors. :)
lol
Bandwidth should not have been an issue that caused it
Bandwidth controlled by switch individual port settings.
Wasn't too many open sessions either because that is controlled by router.
Replaced cable... which was a monoprice...no more monoprice..second one with issues.
I think it was one of the many hungry malware like apps the kids like to use today...and it could have been demanding too much bandwidth.
Which the ap shouldn't have taken the abuse... the switch should of been the one dealing with it.
Got to go
Thanks for input
Later..
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top