Connecting to Oddessy client Family history centre

Discussions about Internet service providers (ISPs), the Meetinghouse Firewall, wired and wireless networking, usage, management, and support of Meetinghouse Internet
stephen500
Member
Posts: 105
Joined: Sun Feb 15, 2009 8:45 am
Location: Chester, England

Connecting to Oddessy client Family history centre

Postby stephen500 » Sun Feb 15, 2009 9:00 am

I am the asst stake clerk for Chester England Stake, Family history.
Here is the context of the problem I have been having.
Birkenhead ward and family history centre were shut down and amalagmated with Moreton ward.
Moreton had a family history centre.
The stake president decided that Moreton chapel for too small for the amalgamated ward (above) and moved Moreton ward into the physical building of Birkenhead chapel.
So now I had to connect Moreton family history centre computer to oddssey client at the old Birkenhead building now known as Moreton ward....!!!!
Birkenhead chapel had its own ccid number as did Moreton.
We attempted to connect using both Moreton and Birkenhead ccid numbers.
I was not able to establish any connection using Moreton's ccid number.
I was able to establish a connection using Birkenhead's ccid number in the new Moreton (old Birkenhead) chapel , but was unable to get up any internet pages either family search or google.
So cnn facility shows authenticated connection but no internet pages are viewable??
In another ward I changed to cnn roaming and this solved the problem, however changing to cnn roaming did not solve the problem on this occassion.
I have had the fault upgraded a level and will be ringing back the oddessy client helpdesk on Tuesday But if any one else can point me in the right direction I will be grateful.

russellhltn
Community Administrator
Posts: 20775
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Sun Feb 15, 2009 2:32 pm

There's a lot of things that could be going on.

Are you sure the "new" building has wireless? I say that because on this side of the pond, not all buildings have wireless installed. You could be connecting to a neighbor.

Also, Odyssey was a client used in older Church installs. It's no longer used as part of new installs. So perhaps the Odyssey client needs to be removed.

Lastly, there are different filtering levels for access. Since the old system was running Odyssey and served a FHC, it probably had "General Access". The one in the new building may be much tighter. I doubt if it would allow Google. Try going to lds.org.

That said, your best bet would be to call up support since they can give you the specifics of the new building.
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

jdlessley
Community Moderators
Posts: 6526
Joined: Sun Mar 16, 2008 11:30 pm
Location: USA, TX

Postby jdlessley » Sun Feb 15, 2009 2:47 pm

The Church is migrating away from using Odyssey Client as a means of controlling wireless access. As such they have not upgraded their licensed version of Odyssey Client to support Wi-Fi Protected Access (WPA) or Wi-Fi Protected Access 2 (WPA2). The licensed version of Odyssey Client the Church has uses only the depricated Wired Equivalent Privacy (WEP) protocol which is less secure than WPA or WPA2.

Since you are trying to solve a connectivity issue you may just as well uninstall Odyssey Client from the computers and have the GSD tech people remove the Odyssey Client scripting from the wireless access points and have them scripted for LDSAccess. LDSAccess uses the WPA protocol. I have not checked but it may also be compatible with WPA2. LDSAccess does not require third party network control software to function.
JD Lessley
Have you tried finding your answer on the LDS.org Help Center page or the LDSTech wiki?

russellhltn
Community Administrator
Posts: 20775
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Sun Feb 15, 2009 8:42 pm

jdlessley wrote:Since you are trying to solve a connectivity issue you may just as well uninstall Odyssey Client from the computers and have the GSD tech people remove the Odyssey Client scripting from the wireless access points and have them scripted for LDSAccess. LDSAccess uses the WPA protocol. I have not checked but it may also be compatible with WPA2. LDSAccess does not require third party network control software to function.


Not a bad idea, but any changes will have to be done to all affected computers, not just the one new one.

I forget, is LDSAccess the one that's supposed to be most like the old FHC one or does it have a different name.... I'm running out the door right now. I'l have to check later.
Have you searched the Wiki?

Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Mon Feb 16, 2009 8:35 am

RussellHltn wrote:I forget, is LDSAccess the one that's supposed to be most like the old FHC one or does it have a different name.


That question doesn't make much sense. LDSAccess is a wireless security profile using WPA. It is used on Cisco Aironet Wireless Access Points and replaces the old "moroni" profile that required the Odyssey client.

But your question seems to be obliquely referring to a filtering mechanism called General Access which has been used in Family History Centers for years that have a Cisco PIX firewall, and which is recently been made available on the Cisco ASA firewalls that are part of the Meetinghouse Internet program. The other two profiles that have been available for some time on the ASA firewalls are called LDS Restricted Access and LDS Extended Access. But those filtering profiles have nothing at all to do with the wireless security profile which unfortunately has a similar name (LDSAccess).

russellhltn
Community Administrator
Posts: 20775
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Mon Feb 16, 2009 1:33 pm

Alan_Brown wrote:But your question seems to be obliquely referring to a filtering mechanism called General Access which has been used in Family History Centers for years that have a Cisco PIX firewall, and which is recently been made available on the Cisco ASA firewalls that are part of the Meetinghouse Internet program.


That's the one! I'm going to have to keep a set of notes to keep track of this stuff.
Have you searched the Wiki?

Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

stephen500
Member
Posts: 105
Joined: Sun Feb 15, 2009 8:45 am
Location: Chester, England

Postby stephen500 » Tue Feb 17, 2009 9:36 am

Thanks for your reply.
I solved the problem by making Oddssesy CNN Facillity and reseting the Cisco access point by disconnecting and turning it off for two minutes.
It now works fine.


Return to “Meetinghouse Internet”

Who is online

Users browsing this forum: No registered users and 1 guest