I have set up a Pi 3 as a web server on my college's WPA2 Enterprise network, with a static IP configured in
I've connected it to the Wi-Fi manually by editing
/etc/wpa_supplicant/wpa_supplicant.conf (and am using a CA certificate). It stays connected to the Wi-Fi consistently, so I can always access it remotely through a RealVNC cloud connection.
Since the Pi is set up as a web server, students whose laptops are connected to the same Wi-Fi network should be able to access it simply by entering the IP address in their web browser. However, most of the time the IP address is not accessible, and attempting to load it in a browser results in a "connection timed out" error.
If I connect to the Pi through VNC over the cloud, then the IP address loads in a web browser instantly, and continues to work for about 10 minutes or so afterwards. It seems like there is a timeout on accessing the IP address over the Wi-Fi, but somehow starting a cloud connection enables it temporarily.
I can't do pings on my school's network, but I tried running a traceroute command on the Pi every minute to see if that kept the IP address accessible, and it didn't. I'm not sure what is affecting whether the IP address can be accessed?