Jiwa

Hi team,
We're encountering an issue with Jiwa when connecting through a VPN. One of our clients uses Jiwa and attempts to access it from home via VPN, but they receive a network error.
I tested the connection by pinging the server, and it responds successfully. Additionally, they can access the server via RDP without issues.
Is there any specific configuration required to enable remote access to Jiwa? Do certain ports need to be open for it to function properly?
Thanks!

deepak@ALLA wrote:but they receive a network error.

You should really disclose the details of the error - it's kind of important.

deepak@ALLA wrote:Is there any specific configuration required to enable remote access to Jiwa?

No.

deepak@ALLA wrote:Do certain ports need to be open for it to function properly?

Typically, no if you are VPN'd. I've connected to remote Jiwa databases via VPN plenty of times and had no issue.

It may be that your SQL Server has whitelisted only certain IP addresses to be able to communicate via TCP/IP on the configured port - the default for SQL Server is port 1433. You can test this by trying to connect to the SQL database using SSMS from a machine which is VPN'd - if you cannot connect and issue SQL queries using SSMS, then it's a firewall or networking issue. I would hope you had already performed that basic troubleshooting already, however.

Attached are screenshots from the client's computer. They are unable to access DD, but they can successfully ping the server and access the port.

Your Test-NetConnection command and ping was using an IP Address - they both succeeded. Your SQL Server SSMS test, whilst not showing the server address as it is obscured in the screenshot, the error shows us the response was an error connecting to "GTSERVER\SQLEXPRESS" - which is not an IP address.

So, this looks like a DNS issue to me - best to reach out to your Network / IT people and get them to ensure DNS names are resolvable when connected via the VPN - or you could side-step that and try connecting via the IP address instead (in either SSMS or Jiwa).

I'd like to help more, but this is not a Jiwa issue - it's just networking.