<
WiFi
TP-LINK EAP120 - Getting Disconnected & Firmware Problems
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.TP-LINK EAP120 - Getting Disconnected & Firmware Problems
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-09-24
TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-02 22:11:03
Tags:
Model :
Hardware Version :
Firmware Version :
ISP :
Hi,
I have ordered the TP-LINK EAP120 access point on the other day and managed to set it up on the day it arrived, but unfortunately it doesn't seem to be working as it should do.
The EAP Controller detects the access point is available and ready to connect from Pending. There was strange things started to happen a few minutes later after connection to the network, the access point begins to become 'Disconnected' from the network by itself and not obtaining an IP address (no upload/download speeds given).
I have to update the firmware for the access point, as in the EAP controller was saying that the firmware for the EAP120 needed to be updated, but the update does not resolve the issue.
I also tried resetting the access point by pressing the reset button the back of the access point with a paper clip, but this does not also resolve the issue.
Is there any other solutions I could to make this access point to work, otherwise I will send it back and receive a new access point.
Much help will be appreciated!
Many thanks,
Ben
Hardware Version :
Firmware Version :
ISP :
Hi,
I have ordered the TP-LINK EAP120 access point on the other day and managed to set it up on the day it arrived, but unfortunately it doesn't seem to be working as it should do.
The EAP Controller detects the access point is available and ready to connect from Pending. There was strange things started to happen a few minutes later after connection to the network, the access point begins to become 'Disconnected' from the network by itself and not obtaining an IP address (no upload/download speeds given).
I have to update the firmware for the access point, as in the EAP controller was saying that the firmware for the EAP120 needed to be updated, but the update does not resolve the issue.
I also tried resetting the access point by pressing the reset button the back of the access point with a paper clip, but this does not also resolve the issue.
Is there any other solutions I could to make this access point to work, otherwise I will send it back and receive a new access point.
Much help will be appreciated!
Many thanks,
Ben
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
6 Reply
Posts: 4334
Helpful: 990
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-02 22:27:53
Could you adopt the EAPs in the controller before they disconnected? How did you find out that the EAPs don't obtain an IP anymore?
To find out wether it is really a problem with the EAPs loosing heir IPs, just set a static IP for a quick test. If the EAP will stay connected to the EAC after having adopted it with a fixed IP, there might be a problem with your DHCP server.
To find out wether it is really a problem with the EAPs loosing heir IPs, just set a static IP for a quick test. If the EAP will stay connected to the EAC after having adopted it with a fixed IP, there might be a problem with your DHCP server.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#2
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-09-24
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-02 23:47:56
Hi R1D2,
I have answered your statements, and they are as follows:
Q: Adopting the EAP
A. Sometimes the EAP can adopt and sometimes it doesn't.
Q: DHCP not obtaining IP address to EAP
A. I find that the DHCP server is not giving an IP address to the EAP because its not listed and it was addressed as: 192.168.0.254 as when the DHCP server only does 192.168.1.100 to 192.168.1.199.
Q: Giving a try with a Static IP
A. I will give it a go with a static IP which hope to solve the problem.
I will let you know if anything happens.
Many thanks,
Ben
I have answered your statements, and they are as follows:
Q: Adopting the EAP
A. Sometimes the EAP can adopt and sometimes it doesn't.
Q: DHCP not obtaining IP address to EAP
A. I find that the DHCP server is not giving an IP address to the EAP because its not listed and it was addressed as: 192.168.0.254 as when the DHCP server only does 192.168.1.100 to 192.168.1.199.
Q: Giving a try with a Static IP
A. I will give it a go with a static IP which hope to solve the problem.
I will let you know if anything happens.
Many thanks,
Ben
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#3
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-09-24
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-03 02:11:58
Just to update,
I have discovered that it was something to do with the main router, and also when the EAP is configuring in the EAP Controller - the connection cuts there and becomes disconnected (this might be a TP-LINK bug which they need to fix), or this might be a technical problem with the coding in which it got confused between the DHCP server and the EAP Controller and delays the connection.
But in another way, the EAP-120 works independently with its own IP address and its own configuration page, no problems at all and the connection works stable in that way. But I prefer to use the EAP Controller as it is easier to configure all at the same time, so I would prefer getting another EAP-110 (as said below).
Anyways, I will send back the EAP-120 and get the basic EAP-110, just to save time with the hassle of getting it to work correctly. With the EAP-110's seem to work very well with our network and had all three connected with no problems, straight forward to do! We all know that EAP-110 comes with a POE adapter to make the job look messy, but I will sort that out. ;)
Many thanks,
Ben
I have discovered that it was something to do with the main router, and also when the EAP is configuring in the EAP Controller - the connection cuts there and becomes disconnected (this might be a TP-LINK bug which they need to fix), or this might be a technical problem with the coding in which it got confused between the DHCP server and the EAP Controller and delays the connection.
But in another way, the EAP-120 works independently with its own IP address and its own configuration page, no problems at all and the connection works stable in that way. But I prefer to use the EAP Controller as it is easier to configure all at the same time, so I would prefer getting another EAP-110 (as said below).
Anyways, I will send back the EAP-120 and get the basic EAP-110, just to save time with the hassle of getting it to work correctly. With the EAP-110's seem to work very well with our network and had all three connected with no problems, straight forward to do! We all know that EAP-110 comes with a POE adapter to make the job look messy, but I will sort that out. ;)
Many thanks,
Ben
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#4
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 4334
Helpful: 990
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-03 04:02:23
You are right, there seems to be a problem in the firmware version 2.0.2_[20160405-rel33786] at least. Just tested it with a brand-new EAP120 and its initial firmware 20160405 using
tcpdump. While the EAP successfully can request an IP with my DHCP server, it doesn't obey DHCP option 138, which tells the EAP the IP of the controller to connect to (last 3 octets of MAC anonymized):
[CODE]20:50:41.903864 IP (tos 0x0, ttl 64, id 63754, offset 0, flags [none], proto UDP (17), length 576)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 98:de:d0:xx:xx:xx (oui Unknown), length 548, xid 0x3c48fff2, Flags [Broadcast]
Client-Ethernet-Address 98:de:d0:xx:xx:xx (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63805363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Client-ID Option 61, length 7: ether 98:de:d0:xx:xx:xx
Hostname Option 12, length 24: "EAP120-98-DE-D0-XX-XX-XX"
Vendor-Class Option 60, length 7: "TP-LINK"
Parameter-Request Option 55, length 12:
Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
Static-Route, Vendor-Option, Netbios-Name-Server, Netbios-Node
Netbios-Scope, Classless-Static-Route, Option 138, Classless-Static-Route-Microsoft
[...]
20:50:42.134082 IP (tos 0x0, ttl 64, id 59148, offset 0, flags [none], proto UDP (17), length 331)
core07.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 303, xid 0x3c48fff2, Flags [Broadcast]
Your-IP 192.168.1.167
Server-IP core07
Client-Ethernet-Address 98:de:d0:xx:xx:xx (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63805363
DHCP-Message Option 53, length 1: Offer
Server-ID Option 54, length 4: core07
Lease-Time Option 51, length 4: 3600
RN Option 58, length 4: 1800
RB Option 59, length 4: 3150
Subnet-Mask Option 1, length 4: 255.255.255.0
BR Option 28, length 4: 192.168.1.255
Default-Gateway Option 3, length 4: core07
Domain-Name-Server Option 6, length 4: core07
Domain-Name Option 15, length 3: "lan"
T138 Option 138, length 4: 429437614
[...]
20:51:20.976409 IP (tos 0x0, ttl 64, id 32353, offset 0, flags [none], proto UDP (17), length 563)
192.168.1.167.51740 > 255.255.255.255.29810: UDP, length 535
E..3~a..@..
..........tr........{
"header": {
"version": "TP-LINK ECS ver 1.0.0",
"mac": "98:de:d0:xx:xx:xx",
"type": 1,
"error": 0
},
[/CODE]
I upgraded its firmware to latest version 2.0.3 Build 20170113 and did reset it to factory settings. Now it connects to my EAP controller through DHCP option 138 and I can successfully adopt it:
[CODE]21:47:48.121268 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto UDP (17), length 585)
192.168.1.167.49574 > xxxxxxxx.eu-ccn.xxxxxxx.net.29810: UDP, length 557
....E..I..@.?.J.....#. ...tr.5_....){
"header": {
"version": "TP-LINK ECS ver 1.0.0",
"mac": "98:de:d0:xx:xx:xx",
"type": 1,
"error": 0
},
[/CODE]
What firmware did you use in your last test?
BTW: 192.168.0.254 is the fallback IP in case the EAP does not get an IP by DHCP. You can use this IP to upgrade the EAP manually, not through the EAC.
[CODE]20:50:41.903864 IP (tos 0x0, ttl 64, id 63754, offset 0, flags [none], proto UDP (17), length 576)
0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 98:de:d0:xx:xx:xx (oui Unknown), length 548, xid 0x3c48fff2, Flags [Broadcast]
Client-Ethernet-Address 98:de:d0:xx:xx:xx (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63805363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Client-ID Option 61, length 7: ether 98:de:d0:xx:xx:xx
Hostname Option 12, length 24: "EAP120-98-DE-D0-XX-XX-XX"
Vendor-Class Option 60, length 7: "TP-LINK"
Parameter-Request Option 55, length 12:
Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
Static-Route, Vendor-Option, Netbios-Name-Server, Netbios-Node
Netbios-Scope, Classless-Static-Route, Option 138, Classless-Static-Route-Microsoft
[...]
20:50:42.134082 IP (tos 0x0, ttl 64, id 59148, offset 0, flags [none], proto UDP (17), length 331)
core07.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 303, xid 0x3c48fff2, Flags [Broadcast]
Your-IP 192.168.1.167
Server-IP core07
Client-Ethernet-Address 98:de:d0:xx:xx:xx (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63805363
DHCP-Message Option 53, length 1: Offer
Server-ID Option 54, length 4: core07
Lease-Time Option 51, length 4: 3600
RN Option 58, length 4: 1800
RB Option 59, length 4: 3150
Subnet-Mask Option 1, length 4: 255.255.255.0
BR Option 28, length 4: 192.168.1.255
Default-Gateway Option 3, length 4: core07
Domain-Name-Server Option 6, length 4: core07
Domain-Name Option 15, length 3: "lan"
T138 Option 138, length 4: 429437614
[...]
20:51:20.976409 IP (tos 0x0, ttl 64, id 32353, offset 0, flags [none], proto UDP (17), length 563)
192.168.1.167.51740 > 255.255.255.255.29810: UDP, length 535
E..3~a..@..
..........tr........{
"header": {
"version": "TP-LINK ECS ver 1.0.0",
"mac": "98:de:d0:xx:xx:xx",
"type": 1,
"error": 0
},
[/CODE]
I upgraded its firmware to latest version 2.0.3 Build 20170113 and did reset it to factory settings. Now it connects to my EAP controller through DHCP option 138 and I can successfully adopt it:
[CODE]21:47:48.121268 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto UDP (17), length 585)
192.168.1.167.49574 > xxxxxxxx.eu-ccn.xxxxxxx.net.29810: UDP, length 557
....E..I..@.?.J.....#. ...tr.5_....){
"header": {
"version": "TP-LINK ECS ver 1.0.0",
"mac": "98:de:d0:xx:xx:xx",
"type": 1,
"error": 0
},
[/CODE]
What firmware did you use in your last test?
BTW: 192.168.0.254 is the fallback IP in case the EAP does not get an IP by DHCP. You can use this IP to upgrade the EAP manually, not through the EAC.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#5
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-09-24
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-03 08:05:46
Hi R1D2,
With my EAP-120, the firmware right now is on 2.0.3 Build 20170113. So far, it's not working correctly as it should... so I am going to request an return and I will be buying myself another EAP which is the EAP-110 or maybe a EAP-220 and see if the issue would work as normal, by the way - I need an EAP to boost the internet signal a bit better, they are VERY good access points.
Although that I need to explain the issue with TP-LINK technical support and see if they know about this bug and hopefully they'll fix it on the next firmware update for the EAP and EAP Controller.
I have altered the fallback IP address to the address for the DHCP to detect easily, but I don't think that makes any difference. But I have manually reset the EAP-120 with using a paperclip, so the fallback IP right now is back to its default.
Many thanks,
Ben
With my EAP-120, the firmware right now is on 2.0.3 Build 20170113. So far, it's not working correctly as it should... so I am going to request an return and I will be buying myself another EAP which is the EAP-110 or maybe a EAP-220 and see if the issue would work as normal, by the way - I need an EAP to boost the internet signal a bit better, they are VERY good access points.
Although that I need to explain the issue with TP-LINK technical support and see if they know about this bug and hopefully they'll fix it on the next firmware update for the EAP and EAP Controller.
I have altered the fallback IP address to the address for the DHCP to detect easily, but I don't think that makes any difference. But I have manually reset the EAP-120 with using a paperclip, so the fallback IP right now is back to its default.
Many thanks,
Ben
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#6
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 4334
Helpful: 990
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:TP-LINK EAP120 - Getting Disconnected & Firmware Problems
2017-06-03 08:50:15
That's strange. My EAP120 is now running 5 hours without interruption. Anyway, if it makes problems, an EAP110 would be an alternative, they are really priceworthy and pretty stable.
As for the EAP220: I would recommend the new EAP225 instead, since it supports IEEE802.11ac and therefore doubles the WiFi speed compared to the EAP220 at nearly the same price. I will test the EAP225 as soon as it arrives, just ordered mine yesterday.
As for the EAP220: I would recommend the new EAP225 instead, since it supports IEEE802.11ac and therefore doubles the WiFi speed compared to the EAP220 at nearly the same price. I will test the EAP225 as soon as it arrives, just ordered mine yesterday.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#7
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-09-24
Information
Helpful: 0
Views: 2407
Replies: 6
Voters 0
No one has voted for it yet.
Tags
Report Inappropriate Content
Transfer Module
New message