>>>It's been the same for a while now, regardless of exact FF version.
>>>
>>>You can get the latest version by hitting the Alt key to bring up the FF menu, then Help...About FireFox. That will check for new versions.
>>
>>Yes, this is what I have done. When I do this it says 32.0.3 and that it is up to date.
>>
>>I still do not understand what would make this situation happen on specific locations only.
>>
>>Maybe Firefox also needs to have a checkup on updating the Root Certificates when it becomes corrupted.
>
>A wild guess -- perhaps the time and date on the workstation are off by a large enough amount that it's playing havoc with autnetication? I've seen on more than one situation where on a computer a person was getting all sorts of warnings with certifications being expired or not being activated yet. After a bit of futzing around to correct the problem, I'd noticed the date & time were off. Trying to synch up with time server wouldn't work. Manually updating the date and time finally corrected both the certificate issues as well as the time resynch.

I've seen that too, most often with old computers where the CMOS battery has died so date/time are way off at system boot. Syncing with a time server in Windows will still work, but the Windows Time service refuses to correct time that is too far off. Depending on the version of Windows and how it's configured that can be as short as 5 minutes or as long as 48 hours. So, as you say you have to manually set it close to the correct date/time, then you can manually resync via the Time service, or let Windows do it automatically at the next scheduled time.