Sophos and wireless network

Discussions around the setup, operation, replacement, and disposal of clerk computers, not to include using MLS
jdlessley
Community Moderators
Posts: 6526
Joined: Sun Mar 16, 2008 11:30 pm
Location: USA, TX

Sophos and wireless network

Postby jdlessley » Fri Jan 15, 2010 5:43 pm

Today I noticed another issue with Sophos - or rather the Sophos updater. I had installed the new security software more than a week ago on one ward's computer. I checked to see if the IDE's and the program had been updated. They had not.

The computer is connected to the internet over the building's wireless network. That creates the problem. When the computer boots up the wireless network takes a bit longer to get an IP address and open an internet connection than the Sophos updater takes to load and check for updates. Since the updater cannot connect to the server the updates are not downloaded and it waits 120 minutes to the next check for updates. The ward does not leave the computer on for that long and therefore Sophos does not get updated.

Sophos can be updated manually and that is what I did for this particular computer. But that is a work-around for an issue that may be corrected. I can see three possible solutions for computers connected wirelessly to the internet. The first is a delay after the computer boots before the updater checks the server for updates. For the computer I checked, a delay of 30 to 60 seconds may be adequate. The second is for the updater to continue checking for an internet connection a bit longer before timing out. The third is to shorten the 120 minute time to something shorter - say 90 minutes.

I can see problems for some people for all three solutions I suggested. But for now I have to instruct those units with wireless connections to manually start the update process.
JD Lessley
Have you tried finding your answer on the LDS.org Help Center page or the LDSTech wiki?

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

Postby russellhltn » Fri Jan 15, 2010 5:55 pm

Interesting. On dial-up units the updater will jump on a dial-up connection as soon as it's established. I can only guess that in your case Sophos is seeing the connection but it's not ready for traffic. I wonder why the delay.
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 » Fri Jan 15, 2010 8:22 pm

RussellHltn wrote:Interesting. On dial-up units the updater will jump on a dial-up connection as soon as it's established. I can only guess that in your case Sophos is seeing the connection but it's not ready for traffic. I wonder why the delay.
The delay appears to be because of the nature of the connection. While the wireless card recognizes the WAP the signal is at the lowest strength to maintain a connection. In any case the connection to the WAP is there but it takes a bit longer to get an IP address from the PIX. The Sophos updater must be seeing the connection to the WAP (signal traffic) but the internet connection has not yet been established.

I have checked the PIX for the same issue with the FHC computers that are cable connected - but they obtain their IP addresses nearly instantly. For other computers that connect wirelessly there is a correlation to the signal strength and the time it takes to get an IP address. In some cases a network connection can be established but an IP address is never obtained - thus no internet. This only happens when the signal strength is at the lowest end acceptable.

There may be other issues with the wireless network at work here of which I am not aware. But I can't tell what it would be.
JD Lessley
Have you tried finding your answer on the LDS.org Help Center page or the LDSTech wiki?

aprayzr
New Member
Posts: 38
Joined: Mon Nov 03, 2008 7:37 pm
Location: Pueblo, CO USA

Postby aprayzr » Fri Jan 15, 2010 8:27 pm

I have noticed the same problem in our units with wireless connections. I think the presence of broadband causes the program to assume a connection is available. Hardwire establishes a connection almost immediately on bootup, while wireless takes time to establish a connection with the access point and is not ready immediately. Dial-up must be initiated, requiring action on the part of Sophos. Thus, the problem is isolated to wireless connections.

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

Postby russellhltn » Fri Jan 15, 2010 8:34 pm

aprayzr wrote:Dial-up must be initiated, requiring action on the part of Sophos. Thus, the problem is isolated to wireless connections.


In my case it's activated by MLS.

I think the issue is that it's looking for a 'active' (media connected) network connection, not the IP stack status. The problem is there is too big a lag between becoming 'active' and being 'ready'.
Have you searched the Wiki?

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


Return to “Clerk Computers”

Who is online

Users browsing this forum: No registered users and 1 guest