• State Verified Answer
  • Replies 3 replies
  • Subscribers 47 subscribers
  • Views 2897 views
  • Users 0 members are here
Options

"There was a connection protocol error" on connecting to GS 2017 server-based TMs

James Toner

We are currently unable to access GS server-based TMs via standard Windows authentication.

Our issue is covered by the following KB article: https://gateway.sdl.com/apex/communityknowledge?articleName=000004298

However, since on our server we do not see Windows authentication, the KB indicates that the solution is not relevant to us, without telling us what the solution might be (If you do not see Windows Authentication in step 4, this KB article does not apply to your situation.)

Has anyone come across similar issues? How have they been resolved?

Many thanks.

James

 

 

 
Rate translation
×
Suggest better translation
×
Parents Reply
  • 0 in reply to Mitja Kelenc
    Hi Mitja,

    Thanks very much for the response.

    I don't think that this is the issue for us: when we enter our Windows user IDs manually, we can access all of the TMs from the root organisation. But entering this data manually is fiddly and needs to be re-entered repeatedly, wasting time and increasing annoyance.

    It seems to be an issue with Windows IIS. Unfortunately, the KB article covers only one possible configuration of IIS, but does not suggest what should be done if that configuration does not apply...

    Since this is a known issue, perhaps the SDL teams would have some insight?
Children