Meeting house lease Wi-Fi connection duration too short (for someone who goes in a daily basis to the building)

Discussions about Internet service providers (ISPs), the Meetinghouse Firewall, wired and wireless networking, usage, management, and support of Meetinghouse Internet
roblad
New Member
Posts: 33
Joined: Tue Jan 08, 2013 10:37 am
Location: Santa Rosa, CA
Contact:

Re: Meeting house lease Wi-Fi connection duration too short (for someone who goes in a daily basis to the building)

#11

Post by roblad »

I have several devices in a meetinghouse that need to be connected to the meetinghouse network. This includes two primary ZOOM clients, two printers, a wall mounted display used for ZOOM calls, a dedicated device that hosts a ZOOM camera.

I have had all of these devices assigned static IP addresses and have their MAC addresses captured in Technology Manager.

This was necessary to suppress the splash page interaction. This worked fine initially but over the last month or so, it has not worked.

I prefer this solution over connecting to the private network, because the 90 day time limit sets a fuse that can expire when no one is thinking about it and then something critical does not work when it is needed. When this happens it is often the case that no one is available who can fix it.

I understand that when the device is registered in Technology Manager that the splash page is supposed to be suppressed. What changed? Can the original functionality be restored? In either case, the behavior should be documented on the TM site.

Perhaps the splash page is suppressed on a set of known device types where a user can’t interact with the splash page but not on others. If this is the case, then I believe there needs to be a new feature where an email notification is sent to all who have TM access privileges for the associated meetinghouse that the “Lehi” password will expire in something like 7 days. If the 90-day passwords can expire without this warning, the feature just can’t be used because the time will come when it will disrupt an important meeting. I also think that the TM user should be allowed to extend the existing password for another 90 days. If the password changes, then all devices that are connected this way must be individually reconnected to the network every 90 days. This is inconvenient and should be unnecessary.
Last edited by roblad on Mon Dec 06, 2021 12:29 pm, edited 1 time in total.
russellhltn
Community Administrator
Posts: 31962
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: Meeting house lease Wi-Fi connection duration too short (for someone who goes in a daily basis to the building)

#12

Post by russellhltn »

Assigning a static IP is separate from the adding them to the "NoSplash" policy. The NoSpash is set via the "Group Policy Manager" which you can find in the "three dot" menu at the Firewall level.

Please note that NoSpash is only needed for devices that need to reach out over the internet and are connected via WiFI. It's not needed for wired devices, nor is it normally needed for devices that only communicate over the local network (like I'd expect printers to work - unless they are using some web services for connection).
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
nmecantwin73
Member
Posts: 192
Joined: Thu Oct 11, 2007 9:36 am
Location: Utah

Re: Meeting house lease Wi-Fi connection duration too short (for someone who goes in a daily basis to the building)

#13

Post by nmecantwin73 »

roblad wrote: Mon Dec 06, 2021 12:21 pm I understand that when the device is registered in Technology Manager that the splash page is supposed to be suppressed. What changed? Can the original functionality be restored? In either case, the behavior should be documented on the TM site.

Perhaps the splash page is suppressed on a set of known device types where a user can’t interact with the splash page but not on others. If this is the case, then I believe there needs to be a new feature where an email notification is sent to all who have TM access privileges for the associated meetinghouse that the “Lehi” password will expire in something like 7 days. If the 90-day passwords can expire without this warning, the feature just can’t be used because the time will come when it will disrupt an important meeting. I also think that the TM user should be allowed to extend the existing password for another 90 days. If the password changes, then all devices that are connected this way must be individually reconnected to the network every 90 days. This is inconvenient and should be unnecessary.
Nothing has changed, to my knowledge. I was able to use this process last night to add a TV connecting to Liahona to the NoSplash group policy and it worked perfectly. One thing to keep in mind when you go to the Group Policy Manager page in TM is to be sure to change the Group Policy drop-down on the right (under the pink banner) to NoSplash and not Iot. Also, the device itself needs to be attempting to connect to Liahona and not Lehi.

Lehi is designed to be used by ward/stake leadership on their mobile devices in the event Liahona needs to be disabled in a building (for Stake Conference, for example). It wasn't envisioned to be used for any other device, especially those needing to bypass the Splash screen for sign in to Liahona.

More info about the NoSplash setup is found on the MHTech Help page at https://www.churchofjesuschrist.org/hel ... s?lang=eng.
User avatar
carloswm85
New Member
Posts: 21
Joined: Sat Dec 31, 2016 4:54 am
Location: Zapala Argentina Stake

Re: Meeting house lease Wi-Fi connection duration too short (for someone who goes in a daily basis to the building)

#14

Post by carloswm85 »

Thanks for your comments, everybody.
Charity never faileth.
Post Reply

Return to “Meetinghouse Internet”