From: | "David Bernal" <david(dot)bernal(at)gmail(dot)com> |
---|---|
To: | "Steve Atkins" <steve(at)blighty(dot)com> |
Cc: | "pgsql general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgsql continuing network issues |
Date: | 2006-03-31 18:53:54 |
Message-ID: | ba93bd50603311053o1b405c63s2ec8e01e0ba1b36f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> What IP address are you trying to connect to? If you're trying to
> connect to 127.0.0.1 and it's listening on 192.168.0.100 then
> that won't work.
I'm trying to connect to 192.168.0.100
> 10107 is WSASYSCALLFAILURE. A pretty generic message, but I've
> seen it when some broken software has inserted itself into the IP
> stack.
Right, I ran a program to check the stack, and it actually didn't find anything.
> Can you connect to TCP port 5432 using telnet, or somesuch? If
> not, are you running any sort of crapware on the windows box that
> will break your network stack ("personal firewall" or "antivirus" are
> some of the buzzwords there - I'd look at your "personal firewall"
> settings first).
I CAN telnet to 192.168.0.100 5432.
From | Date | Subject | |
---|---|---|---|
Next Message | David Bernal | 2006-03-31 18:56:16 | Re: pgsql continuing network issues |
Previous Message | Ed L. | 2006-03-31 18:51:20 | Re: pg 8.1.2 performance issue |