I restarted my PC, and it started working. I made a bunch of changes in the management portal, so I’m not sure which one did the trick. I had trouble connecting with my internal IPv4, but it worked fine with localhost before restarting. I think enabling some services and restarting PC did the Job. I’ll double-check the settings and post the exact configurations(if needed) here.
Thanks!

I am using Windows 11 and trying to connect to a SuperServer on port 1972. I have confirmed that the port is enabled by successfully establishing a Telnet connection to port 1972. However, I am facing issues when attempting to add a Data Source Name (DSN) using the ODBC driver.

Key Details:

• OS: Windows 11
• Port: 1972 (Telnet test successful)
• ODBC Driver:
  • Path: C:\Program Files (x86)\Common Files\InterSystems\Cache\CacheODBC64.dll
  • Version: 2013.1.6.950.1.14259
• DSN Name: Silk
• Cache Namespace: Silk
• Host IP: (IPv4)
• User: sa (authentication via password)
• Connection Success: When using localhost
• Connection Failure: When using IPv4 address

Error Message:

When using the IPv4 address for the host, I receive the following error:

Driver = C:\Program Files (x86)\Common Files\InterSystems\Cache\CacheODBC64.dll
Driver Version = 2013.1.6.950.1.14259

Data Source Name = Silk
Host (IP Address) = [IPv4 address]
Port = 1972
Caché Namespace = Silk
Authentication Method = 0 - Password
User Name = sa
Description = 
Cache ODBC Logging = No
Use Locale Decimal symbol = No
Disable Query Timeout = 0
Static Cursors Support = 0
Unicode SQLTypes = 0

Connect Error: See CacheODBC.log for details
[Cache ODBC][State : S1000][Native Code 417]
[C:\WINDOWS\system32\odbcad32.exe]
Access Denied

The logs don’t provide any clear information as to the cause of the issue., In SQL Server, remote connections typically need to be explicitly enabled. It is possible that a similar setting or configuration might be required in this case to allow connections via IPv4.