|
From: <pm...@wi...> - 2016-07-29 20:27:54
|
Hi John, Thanks for the replies. I did try changing the HOSTNAME to the IP address but that did not help. Actually I just got it to work. I kept googling and found this solution: In the ALIAS I modified the URL value where after the DB name I added: ?sslmode=require That allowed me to access the DB on the remote vendor server without issue since I cannot make any modifications to that server. This did the trick. Hopefully if someone else runs into this same issue this may help. Thanks and have a great weekend. On Friday, July 29, 2016 3:04 PM, John Hardin <jh...@im...> wrote: ============= On Fri, 29 Jul 2016, pm...@wi... wrote: > I forgot to mention that I'm on Windows 10. > > The Postgresql box is a VENDOR box and I cannot make any changes there. > > I got this same error in pgAdmin III but there was another setting under > the ADVANCED tab called Host Address where I entered the IP address and > then I was able to access the server without issue. ...does it work if you use the IP address (vs. the hostname) in the JDBC connect string? -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jh...@im... FALaholic #11174 pgpk -a jh...@im... key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- You are in a maze of twisty little protocols, all written by Microsoft. ---------------------------------------------------------------------- 7 days until the 281st anniversary of John Peter Zenger's acquittal |
