Jade incorrectly resolving a server with a VPN

[torrie]

We've setup a site with a Jade installation and are specifing the fully qualified name of their server in the INI file. e.g. server.domain.co.nz. The internal thin clients resolve this to the internal IP address of the server (192.168.0.1) and connect OK.

If we're connected to the internet on another network the same fully qualified name resolves to an external IP address (203.97.175.XXX.) When connected to the site on a VPN it resolves to the internal IP address and we can ping the server correctly. That is pinging "server.domain.co.nz" has the following output

C:\Users\torrie>ping server.domain.co.nz
Pinging server.domain.co.nz [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=730ms TTL=127
Reply from 192.168.0.1: bytes=32 time=91ms TTL=127
Reply from 192.168.0.1: bytes=32 time=92ms TTL=127
Reply from 192.168.0.1: bytes=32 time=94ms TTL=127

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 730ms, Average = 251ms

However when connected to the VPN and we start the Jade client, it appears that Jade is resolving the server name to the external IP address. e.g. from the client's jommsg.log

2009/11/19 11:13:26.520 0068c-1d98 LHOTSE: (jade) Version 6.3.04 - ANSI, OS Version: NT 6.00 build 6002 (Service Pack 2), Wow64: false, Architecture: i686-msoft-win32-ansi
2009/11/19 11:13:26.520 0068c-1d98 LHOTSE: Invocation: "C:\Program Files\Concept Engineering LTD\CSMUVCDEM\c_bin\jade.exe" ini="C:\ProgramData\Concept Engineering Ltd\CSMUVCDEM\c_config\CSMUVCDEM_ThinClient.ini" app=VCare schema=VCareFormSchemaNZ
2009/11/19 11:13:26.518 0068c-1d98 JadeExe: Connect failed for app server tcp address: 203.97.175.XXX error 10060
2009/11/19 11:13:30.092 0068c-1d98 JadeExe: App Server: server.domain.co.nz Application: VCare Error = 14140 : Thin Client Tcp connection failed
2009/11/19 11:13:30.160 0068c-1eb0 LHOTSE: (jade) Finished: exit code 0

In the Advance Network setup, we've moved the Remote Access Connections to the top of the list and it has the lowest metric in the routing table.

Has anyone struck this or a similar problem. We can change the INI file to use the internal IP address to work around the issue, but I'm curious to know why a Ping resolves the server name to a different IP address than Jade.exe does.

[Chris Holmes]

Hi Torrie,

Does your external user access the internet via a proxy?
If so the Jade Thinclient may be trying to go through the proxy server specified either in Internet Explorer or in the thinclient ini file itself.

If it is going via the proxy, the proxy will not know about the VPN and will probably use the external IP address.

Have a look in your thinclient ini file for any proxy related entries such as:

SSLProxyDetect=true
SSLProxyHost=<proxy server>

Thanks,
Chris.

[Chris Holmes]

Hi Torrie,

My colleague also has the following suggestion:

If it turns out not to be a proxy issue it might also be worthwhile performing an nslookup with the VPN up, rather than a ping. Ping tends to use WINS and the host file first for name resolution whereas nslookup doesn't.

Also, flushing the local DNS cache might be required.

Cheers,
Chris.