Remote connection to the SmartClient server
Hi,
I'm trying to connect SmartClient 2.3 remotely trough a router, form customer's office network.
The external connection to the client network trough the router seems to be OK, Windows RemoteDesktop is working fine. Also, I can open the user defined web page (usersite) on the server remotely trough the router, using the following syntax:
"http://172.16.4.11/usersite"
(172.16.4.11 is the IP address of the server from client network)
The server is Windows server 2016 with 800xA ver. 6.0.3.2. Currently the SmartClient is installed on the Aspect+Connect Server. The router is connected to the client network. There is no domain controller, the system is based on workgroup.
If I connect another node (PC) directly to the client network, I can reach the SmartClient from the server using the following syntax:
"https://ASCS1/SC?feature=SCPG2"
where ASCS1 is the name of the server. So I think certificate and firewall settings for the SmartClient are OK.
If I write "https://172.16.4.11/SC?feature=SCPG2" in IE, even on the server, the SmartClient doesn't want to open. In the same way, I can't reach the SmartClient remotely, trough the router. It seems the name is assigned to the local host of the server only?
Could you please advise how to solve that.
I'm trying to connect SmartClient 2.3 remotely trough a router, form customer's office network.
The external connection to the client network trough the router seems to be OK, Windows RemoteDesktop is working fine. Also, I can open the user defined web page (usersite) on the server remotely trough the router, using the following syntax:
"http://172.16.4.11/usersite"
(172.16.4.11 is the IP address of the server from client network)
The server is Windows server 2016 with 800xA ver. 6.0.3.2. Currently the SmartClient is installed on the Aspect+Connect Server. The router is connected to the client network. There is no domain controller, the system is based on workgroup.
If I connect another node (PC) directly to the client network, I can reach the SmartClient from the server using the following syntax:
"https://ASCS1/SC?feature=SCPG2"
where ASCS1 is the name of the server. So I think certificate and firewall settings for the SmartClient are OK.
If I write "https://172.16.4.11/SC?feature=SCPG2" in IE, even on the server, the SmartClient doesn't want to open. In the same way, I can't reach the SmartClient remotely, trough the router. It seems the name is assigned to the local host of the server only?
Could you please advise how to solve that.
Voted best answer
2
Hi Kolyo
Likely ASCS1 in https request doesn't mean just IP address but contains also */directory of the SmartClient.
Unfortunately I can't tell you exact path. Try to search in IIS manager in Pools what is the directory extension of the SmartClient.
I hope it helps a bit until you get another more qualified answer.
Likely ASCS1 in https request doesn't mean just IP address but contains also */directory of the SmartClient.
Unfortunately I can't tell you exact path. Try to search in IIS manager in Pools what is the directory extension of the SmartClient.
I hope it helps a bit until you get another more qualified answer.
Answered 11 months ago
Answers
1
You write in one path "http" but in the other path "https". Is this correct or just a copy / paste error in your question ?
These use different ports ( 80 and 443 ). Check both ports are open on the Router. If http works, but https doesn't then its typically a problem either with the redirect from http to https or the security certificate ( assuming you have https enabled- otherwise you can redirect https back to http but its not really recommended ).
These use different ports ( 80 and 443 ). Check both ports are open on the Router. If http works, but https doesn't then its typically a problem either with the redirect from http to https or the security certificate ( assuming you have https enabled- otherwise you can redirect https back to http but its not really recommended ).
Answered 11 months ago
0
After half an year of trying, downgraded to SmartClient ver. 2.2 rev. D RU2 solved the problem.
It is working without certificate and using http.
My conclusion is that the server certificate, needed to open smart client, is looking exactly for the name of the server (alias like ASCS1) and don't want to accept IP address. That makes impossible connection to the smart client server trough a router - from outside, other network, than the client network. Inside the client network the alias is OK and it works.
Who knows, may be there is another way to create a certificate, which includes IP address of the server or some other solution.
It is working without certificate and using http.
My conclusion is that the server certificate, needed to open smart client, is looking exactly for the name of the server (alias like ASCS1) and don't want to accept IP address. That makes impossible connection to the smart client server trough a router - from outside, other network, than the client network. Inside the client network the alias is OK and it works.
Who knows, may be there is another way to create a certificate, which includes IP address of the server or some other solution.
Add new comment