|
Elizabeth,
It happened to me many many times and I called it in, wrote a report, sent in my logs.
I don't have a router... and yes, they tried to cry FIREWALL FIREWALL but I don't have one (I am on a Mac). So the problem is NOT with your firewall... it is a problem that cropped up with their latest update and they, as usual, try to blame the users.
It didn't happen to me on my last session, so they may have found their error... so please post here if you are still experiencing the problem.
My theory was they left a secure socket layer active AFTER the launching process which caused all sorts of timing problems. I think they found it after I flagged that issue for them in my email, so let us know if your problem went away. I think mine did.
|