Alright, I ran into this yesterday when trying to connect to my postgresql
server, I used my normal rutine of loading up 'bitvise tunnelier: SSH2
TCP/IP connection forwarder' so that I could run a secure connection.
forwarded with the following settings:
On? Yes
Listen IP: 127.0.0.1
Listen Port: 5432
Destination IP: localhost
Destination Port 5432
These settings have worked in the past. We took down the upgraded database
(I had used PgAdmin though tunnelier on both the old db and the new one) to
bring up the old one, since one of the databases diddn't make it though the
conversion. Dumped the db on the old copy of PostgreSQL. And then brought
the upgraded PostgreSQL back online and inserted the db in though psql.
Any ideas?
Thanks,
Will Robertson
will@demonkarma.net
P.S. Below is cut and copied from the Log View on PgAdmin II if that is of
any help.
======= Debug Log View =======
4/12/2002 12:48:21 PM - Entering pgAdmin II:frmConnect.cmdConnect_Click()
4/12/2002 12:48:21 PM - Connecting to localhost...
4/12/2002 12:48:21 PM - Entering pgAdmin II:basRegistry.RegRead(-2147483647,
"Software\pgAdmin II", "Master DB")
4/12/2002 12:48:21 PM - Entering pgSchema:pgServer.Property Let
MasterDB("parallax")
4/12/2002 12:48:21 PM - Entering pgSchema:pgServer.Connect("localhost",
5432, "will", "********")
4/12/2002 12:48:21 PM - Opening cnPostgreSQL:
SERVER=localhost;PORT=5432;UID=will;PWD=********;DATABASE=parallax;DRIVER={P
ostgreSQL};READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSION
ING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;FETCH=100;SOCKET=4096;UNKNOWNSIZES=0;
MAXVARCHARSIZE=254;MAXLONGVARCHARSIZE=65536;OPTIMIZER=1;KSQO=1;USEDECLAREFET
CH=0;TEXTASLONGVARCHAR=1;UNKNOWNSASLONGVARCHAR=1;BOOLSASCHAR=1;PARSE=0;CANCE
LASFREESTMT=0;EXTRASYSTABLEPREFIXES=dd_;COMMLOG=1;DEBUG=1;
4/12/2002 12:48:22 PM - Done - 0.27 Secs.
4/12/2002 12:48:22 PM - Error in pgAdmin
II:frmConnect.cmdConnect_Click: -2147217843 - Unexpected protocol character
during authentication; Socket has been closed.
