Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 5 of 5
  1. #1

    Exclamation problems with EAP110 type 2

    Model :

    Hardware Version : Not Clear

    Firmware Version :

    ISP : [/COLOR]

    hello ALL!

    I am from another country, so please exuse for my English.

    Well, moderators, if the letter with activation is gone for some reasons (spam filter or deleted ) you cannot resend a message (only new password), so you have to register a new user. Please take care of it.

    We have EAP110, i tried all the firmwares available. The problem is: while switching from DHCP to Static to ANOTHER subnet the EAP110 do not respond. So, our DHCP subnet is 96, so, for example EAP110 has a 192.168.96.115 address. then we are switching it to static, as 192.168.96.115 - it still works well. After that we changing an ip address from another subnet - for example 192.168.47.2 - and that's all, EAP110 do not respond, no pings.

    Got any ideas what to do? All the firmares have been used including the very first one.

    Thanks a lot, waiting for your anser

  2. #2
    The DHCP subnet is 96 which mean equipment only in the same subnet(96) could communicate with each other in the LAN. If you want to change it to 47.2, then you also need to change the DHCP LAN subnet to 47. Whether the IP is available you can also see from the DHCP server. If server is a router, you can see the IP Address Pool in the LAN option. It will show you what address is legal in the LAN side.

  3. #3

    Simmilar problem

    Hello,

    I have the simmilar problem - we have many offices (different subnets) connected with our HQ office with PPTP tunels, where is the TP-LINK EAP Controller placed.
    Every subnet has own Mikrotik router with own DHCP set. I've placed option 138 on each DHCP pointing to EAP Controller in HQ.

    There are many APs (EAP110 v1.0) in different sunbnets. I've connected them in HQ and all was discovered without problems.
    On external offices (with DHCP option 138) they can't be discovered by controller.

    Subnets are connected together in the right way - all services are working across whole site - nor the EAP Controller discovery
    There is only one historical stupidity in this network -> my ancestor used 0 subnet for HQ, but I think it's not the point of this problem.

    Is there another/third option to make discovery work across many subnets?

    Thanks, BR

  4. #4
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Quote Originally Posted by kubik256 View Post
    There are many APs (EAP110 v1.0) in different sunbnets. I've connected them in HQ and all was discovered without problems.
    On external offices (with DHCP option 138) they can't be discovered by controller.
    Did you open UDP port 29810 and TCP ports 29811 to 29813 in your HQ's firewall for the external offices?

  5. #5
    @R1D2: Thanks for your reply.
    Comunication between routers via PPTP (inside LAN's subnets) isn't going through firewall, coz the firewall is set to filter only gateway incomming connections - not PPTP pears.
    While I was writing this post, I've resolved the problem ...EAP Controller on Hyper-V silently changed it's IP address from static to DHCP.... OMG!

    After I set back to the right static IP it ligths up like christmass tree with pending APs from all other subnets

    Have a nice day and sorry for this
    Last edited by kubik256; 04-26-2017 at 09:12.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.