Guest User!

You are not Sophos Staff.

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

Wireless network will not allow re-connects after a day or so.

Initially the WiFi network works properly in all ways. My problem is this: wireless devices are not able to connect after about a 24 hour period. I have setup multiple Sophos XG routers with WAPs and built-in WiFi but this one is giving me grief.

I have an XG125W. I have deleted and rebuilt the wifi network, zone, dhcp, and policies multiple times.

If devices never leave the wifi they stay connected and pass traffic and the SSID is still being broadcast after 24 hours. It just won't allow new connections.

Turning the Wireles Network off and back on fixes the issue for the day but it just resets the situation. DHCP isn't running out of addresses and increasing the lease time doesn't have any effect.

I have 2 wireless networks (a private and guest) and this happens with both of them.

 

What am I missing? Does anyone have any ideas or suggestions?

 

Thank you for your time and help.

 

Mark



This thread was automatically locked due to age.
  • Mark,

    I do not have this problem on my XG.

    Can you give us more information about your configuration? I mean:

    Wireless Network type (bridged, zone)

    Encryption used

    Are you using clientless users?

    Thanks

  • WPA2 Personal

    Separate Zone

    TKIP (only abg)

    2.4 and 5 Ghz

    Clientless users

     

    Does that help? I have tried bridging the private wifi to the internal network but couldn't get the DHCP to work from the internal network properly. Zones seem like a better way to do things and that is how I have been doing them so I didn't put too much effort into that route.

  • Holli,

    by default if a device receives an IP address from the DHCP server (where the lease is for example 8 hours) and you move the same device (so same mac-address) to another wireless network belonging to another zone (different ip) you will not receive the correct IP address (because it is already registered from the first DHCP server).

    Make sure to enable dhcp global option from commad line. Use ssh or cli to connect to XG, option 4 and type: "system dhcp static-entry-scope global" without quota.

    Hope this helps!

    Thanks

  • I'm having the same issue with my new XG135W; after the initial setup of the internal WAP (I configured private and guest networks), I was able to connect to both networks and setup a few of my user's devices to connect to each network for testing. Everything worked fine at first. The next day no one was able to connect to either wifi network and I'm not even seeing the guest network SSID anymore when I scan. I see the private network, but can't connect to it. If I turn wireless off/on it will start working again, but that's not a fix. I do have a ticket open with support, but no help there yet. Any one else able to resolve this?

    Thanks,
    Dan

  • I am having this exact issue on an XG125W.  I setup the wireless and just as Mark has explained, clients can connect and then a day or so later connections are not successful.  Restarting will fix the issue, but it re-occurs within a day or so.  Any update to this thread?  

     

    Jeremy

  • Jeremy, someone else may be able to help, but my issue was never resolved. I ended up just disabling the built-in WiFi and using only external Sophos WAPs. All of the external ones work great, with no issues, but you can't configure the built-in the same as the external anyway.  In the future I'll just order the non-WiFi models and use external WAPs only. Sorry I can't be of more help, but this is what I ended up doing.

  • Thanks Dan.  I might go that route.

     

  • Hi all,

    I advise you to open a ticket with the support.

    I am sure it is a bug with W XG model.

    Let us know.