Customer Service:Guest wireless access - Revision history

Norwinu at 19:14, 11 April 2018

2018-04-11T19:14:44Z

Norwinu at 19:11, 11 April 2018

2018-04-11T19:11:13Z

Norwinu: /* Notes */

2018-04-11T18:51:50Z

Notes

Norwinu at 18:47, 11 April 2018

2018-04-11T18:47:06Z

Norwinu: /* Notes */

2018-04-11T18:44:30Z

Notes

Norwinu: Created page with "==Granting visitors WiFi access== Guests may request WiFi access since the guest network is open/visible. I.S. does not need to be contacted to request access to the guest ne..."

2018-04-11T18:43:18Z

Created page with "==Granting visitors WiFi access== Guests may request WiFi access since the guest network is open/visible. I.S. does not need to be contacted to request access to the guest ne..."

New page

==Granting visitors WiFi access==

Guests may request WiFi access since the guest network is open/visible. I.S. does not need to be contacted to request access to the guest network; it is left to the discretion of the hosting staff member to allow their guests access.

* Wireless network: uwd_guest
:* Username: unipharm
:* Password: guest

==Notes==
Some notes to keep in mind. These don't need to be relayed to guest users, but are meant as an internal FYI.

* It is a known issue that currently, the guest network does not hold sessions very well. That is, after initial login, if you put your device to sleep (or even press the power button on your phone to turn off the display), attempts to use the WiFi thereafter may prompt the user to log in again. At most, this is a minor inconvenience and it does not seem to dissuade guests from using the guest network (empirically speaking, at least).

* Roaming around the building and hopping to another WiFi "hotspot" may also prompt for re-login. Basically, guests may be asked to log in frequently if they're not continuously using their device and/or are mobile.

* I.S. is notified of failed and successful authentications.

* This network is intended for guests. Staff should connect to uwd_staff. The staff network is not affected by the issues described above.

[[Category: uniPHARM]]

@@ Line 10: / Line 10: @@
  Some notes to keep in mind. These don't need to be relayed to guest users, but are meant as an internal FYI.
-* It is a known issue that the guest network does not currently hold sessions very well. That is, after initial login, if you put your device to sleep (or even press the power button on your phone to turn off the display), attempts to use the WiFi thereafter may prompt the user to log in again. At most, this is a minor inconvenience and it does not seem to dissuade guests from using the guest network (empirically speaking, at least).
+* It is a known issue that the guest network does not currently hold sessions very well. That is, after initial login, if the user puts their device to sleep (including pressing the power button on a phone to turn off the display), attempts to use the WiFi thereafter may prompt the user to log in again. At most, this is a minor inconvenience and it does not seem to dissuade guests from using the guest network (empirically speaking, at least).
-* Roaming around the building and hopping to another WiFi "hotspot" may also prompt for re-login. Basically, guests may be asked to log in frequently if they're not continuously using their device and/or are mobile.
+* Roaming around the building and hopping to another WiFi "hotspot" may also prompt for re-login. Basically, guests may be asked to log in frequently if they're not continuously using their device and/or are mobile. I.S. is looking to fix this in the future.
 * I.S. is notified of failed and successful authentication attempts.

@@ Line 10: / Line 10: @@
  Some notes to keep in mind. These don't need to be relayed to guest users, but are meant as an internal FYI.
-* It is a known issue that the guest network does not hold sessions very well. That is, after initial login, if you put your device to sleep (or even press the power button on your phone to turn off the display), attempts to use the WiFi thereafter may prompt the user to log in again. At most, this is a minor inconvenience and it does not seem to dissuade guests from using the guest network (empirically speaking, at least).
+* It is a known issue that the guest network does not currently hold sessions very well. That is, after initial login, if you put your device to sleep (or even press the power button on your phone to turn off the display), attempts to use the WiFi thereafter may prompt the user to log in again. At most, this is a minor inconvenience and it does not seem to dissuade guests from using the guest network (empirically speaking, at least).
 * Roaming around the building and hopping to another WiFi "hotspot" may also prompt for re-login. Basically, guests may be asked to log in frequently if they're not continuously using their device and/or are mobile.

@@ Line 14: / Line 14: @@
 * Roaming around the building and hopping to another WiFi "hotspot" may also prompt for re-login. Basically, guests may be asked to log in frequently if they're not continuously using their device and/or are mobile.
-* I.S. is notified of failed and successful authentications.
+* I.S. is notified of failed and successful authentication attempts.
 * This network is intended for guests. Staff should connect to uwd_staff. The staff network is not affected by the issues described above.

@@ Line 1: / Line 1: @@
 ==Granting visitors WiFi access==
-Guests may request WiFi access since the guest network is open/visible. I.S. does not need to be contacted to request access to the guest network; it is left to the discretion of the hosting staff member to allow their guests access.
+Guests may request WiFi access since the guest network is open/visible. I.S. does not need to be contacted to request access to the guest network; it is left to the discretion of the hosting staff member to allow their guests access, in which case they can be provided with the following connection details:
 * Wireless network: uwd_guest