IainK
07-07-2013, 12:02
This is probably due to a lot of users inside the same subnet accessing Google.
Whether or not this is because of automated means or simply too many users trying to access at the one time I'm unsure.
Occasionally some of the Terminal Services servers I manage at AWS experience the same thing, usually changing their external IP will fix this.
Whether or not this is because of automated means or simply too many users trying to access at the one time I'm unsure.
Occasionally some of the Terminal Services servers I manage at AWS experience the same thing, usually changing their external IP will fix this.