New problem solver
•
17 Messages
Comcast Business Internet Closing Connection with Google Drive while Syncing via SyncDocs
Can't sync using Comcast, but using AT&T it works just fine... Clearly demonstrating that this is a Comcast ISP issue.
For the past 5yrs+ I have used Comcast business internet and had virtually no problems. I have been syncing business files with Google drive via Syncdocs. This too has worked flawlessly for the past 2 years or so. In fact it worked so well that I was a bit slow in catching this problem.
Starting on May 3 I began having problems with accessing Google servers. I didn't realize that I was no longer syncing until I happened to observe some out of date files on my local machine. I reviewed my error logs and started finding entries like this:
"5/11/2017 7:59:27 AM(ver. 6.931) Failed to connect to Google Drive v2. Check your Internet connection."
After confirming that I could successfully log into Google Drive via web browser, resetting my permissions, and reauthenticating with Google I was getting frustrated looking for a solution. Then I switched the PC involved to a redundant AT&T internet account and syncing resumed without error.
Any suggestions to find/fix this Comcast error on my business account?
hlothrop
New problem solver
•
17 Messages
9 years ago
More of the same....Log file shows continued failure to connect
6/2/2017 1:15:12 PM(ver. 6.951) Could not contact Google servers. Network might be down. Will retry in a few seconds...
Execution of request failed System.Exception : sd criticality=0
Inner:
Source: Syncdocs : sd criticality=0
6/2/2017 1:41:24 PM(ver. 6.951) Failed to connect to Google Drive v2. Check your Internet connection.
If your connection is OK, you may need to set up the Proxy Server settings.
If this is not the cause, look at the error log in the Advanced tab in the Preferences menu.
The underlying connection was closed: An unexpected error occurred on a send. System.Net.WebException : sd criticality=6
Inner: System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
Source: Syncdocs : sd criticality=6
6/2/2017 1:41:41 PM(ver. 6.951) Could not contact Google servers. Network might be down. Will retry in a few seconds...
Execution of request failed System.Exception : sd criticality=0
Inner:
Source: Syncdocs : sd criticality=0
0
0
hlothrop
New problem solver
•
17 Messages
9 years ago
FWIW...just to fully compare, switched back over to the AT&T ISP connection and is syncing fine. Here's what error log looks like when it's working...
6/2/2017 2:20:53 PM(ver. 6.951) (re)started standard1 Syncdocs at 6/2/2017 2:20:53 PM
0
0
CCMichael
Gold Problem solver
•
575 Messages
9 years ago
Thank you again for all your patience in getting this resolved. I have created a Tier II ticket informing them to look at our SSL certificates for our systems in your area. Understandably this may need to get escalated to our Network Operations Control center for further review so I cannot give an accurate estimation to resolution. Again I appreciate your help and patience in getting this resolved. Please let me know if anything changes in the mean time.
0
0
hlothrop
New problem solver
•
17 Messages
9 years ago
Michael, thank you for your help. So basically I will let you know if something changes. I know you can't make promises, but just to set my own expectations, should I consider that this is likley an hours, days or weeks type of solution timeline?
0
0
hlothrop
New problem solver
•
17 Messages
7 years ago
After 18 months of flawless performance, this exact same issue has reared it's head once again.
Here's the Error log snippet showing SSL problem on my Comcast ISP primary connection...
"12/3/2018 11:25:44 AM(ver. 6.985) Google reported credentials (SSL) problem during upload. Stopping this sync and re-authenticating in a minute...
RestartSyncFromLogin System.Exception : sd criticality=7 Inner: Source: Syncdocs : sd criticality=7
12/3/2018 11:58:08 AM(ver. 6.985) "
And here's the log showing successful connection and sync when connected to my redundant/backup AT&T ISP...
"12/3/2018 1:12:01 PM(ver. 6.985) (re)started standard1 Syncdocs at 12/3/2018 1:12:01 PM"
Exact same problem, exact same symptoms, exact same proof it's a Comcast SSL issue.
Last time this is when it was resolved..." I have created a Tier II ticket informing them to look at our SSL certificates for our systems in your area. Understandably this may need to get escalated to our Network Operations Control center for further review"
Could we please ask for help again? Thanks. Howard
0
0