Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to see my access points

I purchased an AP 55 and connected it to my a Netgear Wireless router that I was using while trying to configure my new XG 105.  I couldn't see the AP 50 and noticed, when I viewed devices on the Netgear wireless router, it had assigned an IP that was not in the same network.  OK makes sense why the XG 105 couldn't see it at that point.  So I removed the Netgear and put a cheapo 10/100 switch in place then plugged the AP 55 into that.  Still I cannot see it.  I am wondering if somehow the IP that was assigned by the Netgear is still in the AP 55 somehow because I am still unable to see the AP 55 in my XG 105.  I cannot find a way to reset the AP 55 to a "default" state.  There doesn't appear to be a way to do so from the guides I found online.  What could i possibly be doing wrong.  This "plug in play" has taken me hours and still I have not been successful to see the AP 55 so I can configure it.



This thread was automatically locked due to age.
  • The AP50 will only work with Sophos security products. The AP will pickup an IP address from your XG if it can see it assuming the dhcp server is on the XG? The AP does basic communication using 1.2.3.4. The nether box would not have been able to use or configure the AP50. The AP is capable of 1gb, so why the 10/100 switch?

    Ian,

    home UTM 9.x running in ESXi 6 e3-1275v2

    AP55c and AP10 (courtesy Astaro)

    Three other UTMs, SUM and SFM in hibernation

    XG 15.x MR3 in hibernation

  • Is the XG on the internet, because there is/was a software up2date for the XG AP function?

    Ian,

    home UTM 9.x running in ESXi 6 e3-1275v2

    AP55c and AP10 (courtesy Astaro)

    Three other UTMs, SUM and SFM in hibernation

    XG 15.x MR3 in hibernation

  • The problem was the AP were not getting an IP because the DHCP was not setup yet. Its not in the documentation that its a requirement prior to setting up the AP. I think something like that should have been in there.