The auto-redirect is most likely the culprit. Since your desktop is
expecting to get a CA signed cert for, in my example www.google.com, but
it's coming from netreg.uvm.edu, it barks.
University of Vermont
[log in to unmask]
On 6/26/2015 11:26 AM, Andrew Hendrickson wrote:
> We’re either looking at the auto redirect that tries to go directly to netreg, or we’re in a hurry and we type the address in.
>> On Jun 26, 2015, at 11:22 AM, Dan Brisson <[log in to unmask]> wrote:
>> Are you sure the machines were trying to connect directly to https://netreg.uvm.edu? Or, were they trying to go to something like https://www.google.com, which Netreg is going to intercept, resulting in a certificate warning from the browser.
>> Dan Brisson
>> Network Engineer
>> University of Vermont
>> (Ph) 802.656.8111
>> [log in to unmask]
>> On 6/26/15 10:42 AM, Andrew Hendrickson wrote:
>>> So, we have a new wired network installed in 589 last October-ish. Our IP addressing is controlled by netreg.
>>> On one or two of our data jacks, we get certificate errors when connecting to netreg.uvm.edu from any un-netregged computer, of any platform, that we connect to those jacks.
>>> Basically the machine thinks the certificate is untrusted. No other data jack in the building shows the same behavior.
>>> Why would this be?
>>> Andrew Hendrickson
>>> CAS IT Administrator
>>> UVM, College of Arts & Sciences
>>> [log in to unmask]
>>> To submit a request for service please use:
> Andrew Hendrickson
> CAS IT Administrator
> UVM, College of Arts & Sciences
> [log in to unmask]
> To submit a request for service please use: