JohnShaw wrote:For Instance, maybe a stake has a ward conference next week they are relying on broadcasting for, A Stake President might be doing PPI's over Video Conferencing, or a stake conference that is webcast.

Use a wired connection. They're not affected by this latest problem. Using wireless for conference is a bad idea even in good times.

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.

JohnShaw wrote:For Instance, maybe a stake has a ward conference next week they are relying on broadcasting for, A Stake President might be doing PPI's over Video Conferencing, or a stake conference that is webcast.

Use a wired connection. They're not affected by this latest problem. Using wireless for conference is a bad idea even in good times.

I'm hoping the conversation wasn't seen as a specific request for a specific situation I'm particularly i, it was meant to point out that there are any number of ways a stake is taking advantage of technology that has been in place for them. We are accustomed to it working the way it dones because it has been stable for so long, but when it isn't stable (like now), I could see disruption to meetings all over the place that might rely on the wireless technology. Just telling someone to plug in a cable doesn't work because we don't all have wired connections.

My Stake President and the 8 other Bishops he does PPI's for do not use a wired connection, and only a couple of them even have that access in their rooms. They have successfully done PPI's over Video for a year now... leading them to believe there is no need to modify their behavior.

So, if I knew there was a potential for the wireless to be down, I could then Inform my Stake President that he should use a wired connection, or they need to schedule to meet face to face in case something happens.

Only if the Church communicates with us can we spot a potential issue to avoid.

Again, I'm not referencing the unkowns, only the knowns

Last edited by johnshaw on Tue Jan 08, 2013 11:39 am, edited 1 time in total.

“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense

JohnShaw wrote:Nothing is more frustrating for me, than to have a problem, try to work through that problem, only to find out it was a known issue, that would've been avoided if I had the information to work with.

For the record, there was no "known" issue which affected us this past Sunday. We all got hit with unexpected behavior and are now doing everything possible to minimize the chances of a recurrence this Sunday.

Pretty sure that both 12/30 and 1/6 had the same issue occur, making the 1/6 a known issue from 12/30 until 1/6 without any notification out to the Group of STS that something may happen because our issue from 12/30 is not resolved...Even if the events are unrelated, one still occurred on 1/6 that now is a known issue.

The sentence you chose to respond to was immediately following several scenarios which imagined a future on 1/13 --> I appreciate your very sharp correction, but isn't the more important thing to help the ENTIRE support group of STS know and understand that there IS an issue being worked on, that potentially it will not be solved by Sunday 1/13 and that they should be preparing a work around or a re-scheduling of the event? All with the hopes that the issue will be resolved by 1/13.

I only offered that last statement of frustration from experience. The CUBS transition, the MLS 3.5 upgrade experiences, The Sophos False-Positive issue on clerk computers - all show there is clearly something broken in our communication channels between the Church Employees and the Stake Volunteers.

“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”

Looks like you got your wish as I received a email about it just a half-hour ago.

Some of us don't have the official calling of STS, but still have to deal with managing the wireless for our meetinghouse. Could you share what the email said?

Here is the body of the e-mail:

Experiencing wireless connection problems?

Some units have reported problems with wireless connectivity in their meetinghouses over the last few weeks. This may be the result of an issue occurring with one of the wireless controllers at Church headquarters. Wireless devices connecting to 881W Meetinghouse Firewalls and 1041N wireless access points may have been affected. Work is being done to prevent this problem from happening in the future.

If you experience problems connecting to 881Ws or 1041Ns that cannot be resolved locally, stake or district technology specialists should contact the Global Service Center (GSC) by email or phone.

Another obstacle that may prevent some people from connecting to Meetinghouse Internet is if there are not enough IP addresses available in a building. Stake or district technology specialists can verify how many IP addresses are configured for a particular building by going to tm.lds.org.

The Church is also working to reduce the lease time for all meetinghouses with 881Ws to 30 minutes, to allow IP addresses that are no longer being used to be available sooner.

If more IP addresses are needed for a particular meetinghouse, stake or district technology specialists should contact the Global Service Center (GSC) by email or phone.