Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

can not connect outside of local network

More
24 Feb 2015 09:50 - 24 Feb 2015 09:51 #2845 by support
Yes, that's precisely why I have asked these questions and what I expected.

What happens there is that the endpoint URL returned by the server is not usable outside its local network. Version 5.32 has a different default behavior and replaces the host part in the endpoint URLs returned by the server by the host part provided by you originally. It is possible to achieve the same in 5.30, but the default behavior in 5.30 is to use the endpoint URL as it is returned by the server, without change.

Best regards
Last edit: 24 Feb 2015 09:51 by support.

Please Log in or Create an account to join the conversation.

More
24 Feb 2015 07:36 #2844 by adid@contel.co.il
hello,

1. opc.tcp://14.1.2.164:49323 is not accessible outside network.

2. problem solved after upgrade to OPCLabs version 5.32.

thank you,
Adi Damty

Please Log in or Create an account to join the conversation.

More
22 Feb 2015 15:06 #2836 by support
1) Is opc.tcp://14.1.2.164:49323 also accessible from the outside network ?

2) Is there any reason why you don't upgrade to version 5.32? (it's free of charge if you are licensed to 5.30, 5.31).

Best regards
The following user(s) said Thank You: adid@contel.co.il

Please Log in or Create an account to join the conversation.

More
22 Feb 2015 12:53 #2835 by adid@contel.co.il
i am trying to connect from opc client to opc server Kepware.
when i inside my network i succeed connect to the server, but when i am trying to connect from outside my network to computer inside my network i didn't succeed - see the errors below.
if i am using your opc sample client i succeed to connect from outside to the computer inside the network.
what i am doing wrong ?

- Licensing for EasyUAClient component started, license serial number 1953000002, issuer name "OPC Labs", subject name "Contel Group". - License validity check for EasyUAClient component has been successful. - The OPC-UA engine executing from assembly "OpcLabs.EasyOpcUAInternal, Version=5.30.1114.1, Culture=neutral, PublicKeyToken=6faddca41dacb409", manifest location "C:\Windows\Microsoft.Net\assembly\GAC_MSIL\OpcLabs.EasyOpcUAInternal\v4.0_5.30.1114.1__6faddca41dacb409\OpcLabs.EasyOpcUAInternal.dll", loaded from the global assembly cache: True. - Running under common language runtime version '4.0.30319.18408', pointer size in this process is 4 bytes. - Running under operating system "Microsoft Windows NT 6.2.9200.0". - Logged on user name "Administrator", associated network domain "WIN-ME800LKSJ27", running in user interactive mode: True. - The OPC-UA engine is connecting to the underlying subsystems. - The OPC-UA engine has determined the client certificate parameters as listed below.
SubjectName: CN=CI_OPC_Tester, DC=WIN-ME800LKSJ27
ApplicationName: CI_OPC_Tester
ApplicationUri: urn:WIN-ME800LKSJ27:CI_OPC_Tester:1.0.0.0:neutral:null
ProductUri: urn:literal:string:CI_OPC_Tester
- The OPC-UA engine has successfully connected to the underlying subsystems. - The OPC-UA client session is connecting to endpoint URL "opc.tcp://213.8.54.50:49323". - OPC-UA endpoint selection on discovery URL "opc.tcp://213.8.54.50:49323" candidate report (10 entries) follows.
[0:Winner(1000+0), 1:EligibleNotAccepted(80), 2:EligibleNotAccepted(130), 3:EligibleNotAccepted(90), 4:EligibleNotAccepted(140), 5:EligibleNotAccepted(1000+0), 6:EligibleNotAccepted(80), 7:EligibleNotAccepted(130), 8:EligibleNotAccepted(90), 9:EligibleNotAccepted(140)]. - The OPC-UA server endpoint URL "opc.tcp://14.1.2.164:49323" with security policy URI "opcfoundation.org/UA/SecurityPolicy#None" and transport policy URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary", selected using discovery on endpoint URL "opc.tcp://213.8.54.50:49323", has zero security level. Using this endpoint is not recommended and is only supported for backward compatibility. This happens when no other endpoints are available and eligible for selection. - An OPC-UA endpoint has been selected for discovery URL "opc.tcp://213.8.54.50:49323" with following parameters:
Endpoint URL "opc.tcp://14.1.2.164:49323", message security mode 'None', security policy URI "opcfoundation.org/UA/SecurityPolicy#None", transport profile URI "opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary". - The server certificate failed validation with error code 0x801A0000 while establishing OPC-UA client session to endpoint URL "opc.tcp://213.8.54.50:49323".
BadCertificateUntrusted 'Certificate is not trusted.
SubjectName: CN=KEPServerEX/UA Server, O=Microsoft, C=IL, DC=yoraml-win7.contel.co.il
IssuerName: CN=KEPServerEX/UA Server, O=Microsoft, C=IL, DC=yoraml-win7.contel.co.il' - The server certificate has been accepted for the OPC-UA client session to endpoint URL "opc.tcp://213.8.54.50:49323" by a fallback method.
Certificate information: [Subject]
CN=KEPServerEX/UA Server, O=Microsoft, C=IL, DC=yoraml-win7.contel.co.il

[Issuer]
CN=KEPServerEX/UA Server, O=Microsoft, C=IL, DC=yoraml-win7.contel.co.il

[Serial Number]
8199A4CB

[Not Before]
11/19/2013 1:05:14 PM

[Not After]
11/17/2023 1:05:14 PM

[Thumbprint]
FC2DBE289D47557A02E67AA3155C984F724A117E
- The OPC-UA client session failed to connect to endpoint URL "opc.tcp://213.8.54.50:49323".
OPC-UA service result - BadConnectionClosed.
---- SERVICE RESULT ----
StatusCode: {BadConnectionClosed} = 0x80AE0000 (2158886912)
- The OPC-UA client session on endpoint URL "opc.tcp://213.8.54.50:49323" failed at tick -104514613 and will retry in 10000 milliseconds. - The status subscription for an OPC-UA session on endpoint URL "opc.tcp://213.8.54.50:49323" is in failure. Further such warnings on this session will not be logged.
OPC-UA service result - BadConnectionClosed.
---- SERVICE RESULT ----
StatusCode: {BadConnectionClosed} = 0x80AE0000 (2158886912)

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.056 seconds