Dear reader,
The problem we are having is very random, but various colleagues of mine are getting a NET::ERR_CERT_COMMON_NAME_INVALID in Chrome when trying to access their gmail or calendar from Google. Now I know what you might think, this must be a browser problem, but in most cases, switching to another browser simply results in the same problem, just a different formulation of the problem (since hey, it's another browser).
Now here comes the weird part, this all started SINCE we placed the Cisco RV130 router in our network. Before that our ISP issued Modem was in Modem/Router mode (now it's been set to Bridge mode by the ISP, I cannot set this myself!) and the aforementioned router was placed in between our first switch (A Netgear GS748T) and the modem.
Various things that I have checked, but first and foremost lets handle the occurrence. The problem only happens sometimes, say a person comes into the office, starts his or her computer, gmail works fine. Then after a few hours they get this error, and after refreshing for like 5 minutes the problem disappears and they can check their Gmail again. Others have this when accessing their calendar but not when opening their gmail. So to sum this all up, it's completely random. So far I am the only one who's experienced it with another website (as in, other than gmail or the gmail calendar) and that was when I tried to access Facebook.com, but this has only been once so far, and honestly I don't care at all if this would ever happen again since the other two websites are way more important.
Computers are running Kaspersky Internet Security, and although the problem only started recently I have tried disabling it when somebody was experiencing the problem but this didn't result in being able to access the aforementioned pages.
Another thing I have checked which seemed to pop up quite often (but given this error message I think it doesn't matter) is the system time on computers. Which I have made sure it was synced and therefore correct.
Also, just now I was able to find out this. When I had the problem on a colleague's computer I did a ping to both
www.google.com and
www.apple.com (given the subject of the error) and the results were this:
www.google.com:
Pinging www.google.com [95.100.141.15] with 32 bytes of data:
Reply from 95.100.141.15: bytes=32 time=11ms TTL=59
Reply from 95.100.141.15: bytes=32 time=11ms TTL=59
Reply from 95.100.141.15: bytes=32 time=10ms TTL=59
Reply from 95.100.141.15: bytes=32 time=9ms TTL=59
Ping statistics for 95.100.141.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 10ms
&
www.apple.com:
Pinging e3191.dscc.akamaiedge.net [95.100.141.15] with 32 bytes of data:
Reply from 95.100.141.15: bytes=32 time=16ms TTL=59
Reply from 95.100.141.15: bytes=32 time=9ms TTL=59
Reply from 95.100.141.15: bytes=32 time=15ms TTL=59
Reply from 95.100.141.15: bytes=32 time=10ms TTL=59
Ping statistics for 95.100.141.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 16ms, Average = 12ms
I don't think it can be correct that both resolve to the same IP address even though I'm pinging to two different webpages. Am I transitioning into a rounting / switching / dns problem here or is this still a Chrome problem? Any help would be appreciated because I'm quite at loss!
Best regards,
Fred
P.s. I have added two images of the resulting errors from Chrome.
[edit]
Forgot to mention that I have started a similar discussion on the Google Chrome forums, but other than flushing my dns in Windows and clearing my host cache in chrome I haven't gotten any results yet. And that only seems to solve the problem temporarily.
