Page 2 of 2

Posted: Mon May 28, 2012 11:50 am
by russellhltn
sammythesm wrote:Also @RussellHltn - I don't think there's anything precluding bonjour from being used in a non-"home" setting. And I certainly haven't seen a policy saying you have to configure a FHC printer in a certain way.

Perhaps they haven't gotten to your FHC yet. The Family History Department is trying to standardize the printers used in a FHC. They replaced a number of ours and it included specific instructions on how to install them - including static IP. I then had to fill out a form and send it in. (And they do pester if they don't get the forms.) The reason for this is that the printers are now being remotely monitored. When the toner gets low, a new one is autometally shipped. This assures the FHC will always have toner without having to stock up on it.

Posted: Mon May 28, 2012 1:50 pm
by johnshaw
This sounds like a fantastic improvement. Here's hoping our 5 FHC's are upgraded sometime soon.

Posted: Thu May 31, 2012 8:07 am
by Aczlan
aclawson wrote:It has been reported that Bonjour was causing some machines to take up to 20 minutes to boot because the LDS firewall wasn't letting it through and the application wouldn't stop trying.
I have seen that at work with Kaspersky. Bonjour was trying 3x/second to connect and failing. Know how fast that gets rid of anything useful in the error log?

Bonjour is on my list of services to "disable unless someone is actually using it"

Aaron Z

Posted: Thu May 31, 2012 9:05 am
by Biggles
I've found that Sophos is the biggest culprit for blocking. I had the problem when trying to update Ward Tools over the meeting house WiFi. Someone else at the time mentioned that it wasn't the firewall as I thought causing the problem, but was Sophos. I temporarily disabled Sophos and the update worked. Bonjour wasn't the problem.

Please don't ask me how I disabled Sophos, as I won't divulge that information. Suffice to say I'm also the STS. A little knowledge is a dangerous thing. ;-)