• State Not Answered
  • Replies replies
    5
  • Subscribers subscribers
    10
  • Views views
    583
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DB Proxy

Georgio M

Dears,

Please note I am trying to configure Microsoft SQL Server inside PAM.

The below steps were done:

1, Created Database connector with default proxy 11521
2. Created rule inside cmdctrl for DBMSSQLAccess.

When trying to access in the SQL, I receive the attached error.

Any help is appreciated.
Best regards,
Georgio

 

 

  • 0  
    It looks like the server syntax for the client there is invalid:
    10.13.1.227,11521
    When I think it should look like:
    10.13.1.227:11521
    Otherwise, it would be good to verify network & port connectivity from the client to the pam manager db connector using telnet.
  • 0 in reply to   

    Dear,

    Thank you for your reply.

    Please note I tested both syntaxes, and same results as attached.

    As for telnet, I was able to telnet between the servers.

    Best regards,
    Georgio

  • 0   in reply to 
    Ah gotchya, well it does look like the syntax for specifying a non-default port is using the "," (sorry for misdirecting you there).
    I see with the latest screenshot you posted, you also updated the port from "11521" (default for Oracle) to "1433," so it'd be useful to try the comma syntax as well using that updated port "1433" :
    10.13.1.227,1433
    or maybe 10.13.1.227,11433

    Please verify the db connector details configured in PAM to ensure the DB Proxy Port is correct (the default is usually 11433 in this case). Would you please also provide a screenshot if possible?

    or if DB Proxy Port is indeed "1433," then just not specifying port would be good to try as well, since it is the default client port:
    10.13.1.227
  • 0 in reply to   

    Dear,

    I initially did the testing on port 11433 with the "," separator; then I tried the 11521.

    as for the connector setup, please find it attached.

    Best regards,

    Georgio

     

  • 0   in reply to 
    Please do go ahead and raise a Case with Support so they can help debug the issue with you and verify your DB Server info, connection string, port/network connectivity, etc.
    I was able to connect in my environment using "<pam-server>,<db-proxy-port>" (e.g. "pam-manager,11433") and it connected fine when providing it a "SQL Server Authentication" credential in the client.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.