| Author |
Message
|
| ganesh |
 Posted: Mon Jan 14, 2019 10:04 am Post subject: IIB Toolkit and TFS 2018 connection. |
 |
|
Master
Joined: 18 Jul 2010
Posts: 294
|
Hi Guys,
We connect to TFS from our IIB toolkit and we recently upgraded from TFS 2015 to TFS 2018. Since the upgrade we are unable to connect to TFS from our toolkit, we get a connection reset error while trying to connect.
I tried changing the network connection from native to direct and still doesn't work.
Has anyone else faced the same issue and if so how did you resolve the problem?
IIB toolkit - 10.0.0.6
Toolkit installed on - Win 10.
PMR was also raised and we are waiting for IBM's response.
Thanks |
|
| Back to top |
|
 |
| ganesh |
| Posted: Mon Jan 14, 2019 10:32 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| One point to add is that the TFS 2015 connection was HTTP and the TFS 2018 is HTTPS. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 14, 2019 11:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Have you checked the PKI setup?
The obvious starting point is that the S in your HTTPS isn't working.
The next point will be asking your TFS admins what they're using, and if you're one certificate short of a trust store.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ganesh |
| Posted: Mon Jan 14, 2019 3:14 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| IBM tech support thinks it could be because of lack of TLS V1.2 support for connections from 10.0.0.6 toolkit. I tried upgrading to fix pack 9 but still had the same connectivity issue. |
|
| Back to top |
|
|
| ganesh |
| Posted: Thu Jan 17, 2019 11:49 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
We added the below to system variable and that resolved our issue.
TF_SSL_PROTOCOL_NAME = TLSv1.2 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 17, 2019 2:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ganesh wrote: |
We added the below to system variable and that resolved our issue.
TF_SSL_PROTOCOL_NAME = TLSv1.2 |
Well done!  Glad that it now works for you. Thanks for providing the solution 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
