Re: pgsql continuing network issues - Mailing list pgsql-general

From Magnus Hagander
Subject Re: pgsql continuing network issues
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0F8C6@algol.sollentuna.se
Whole thread Raw
In response to pgsql continuing network issues  ("David Bernal" <david.bernal@gmail.com>)
List pgsql-general
> > IF I change the listen_addresses directive to localhost, I
> can connect
> > fine and everything works EXCEPT I get the message "NOTICE:  Unknown
> > win32 socket error code: 10107" repeatedly anytime I do something.
> > This would be acceptable, except that I need to be able to
> access this
> > database at client sites.
>
> 10107 is WSASYSCALLFAILURE. A pretty generic message, but
> I've seen it when some broken software has inserted itself
> into the IP stack.

For those who prefer enlgish, the text for that message is "A system
call that should never fail has failed.". I'd say that indicates
something is not healthy about your machine :)

Usually when these things happen, I'd recommend looking at firewall,
antivirus or antispyware products. And try to actually remove them, not
just disable it. Failing that, look at virus or spyware - it is windows
after all :-)

> I CAN telnet to 192.168.0.100 5432.

That, however, makes it look like it might be something different.
*Might* - it cna still be a fw or such.

It could be an issue with DNS resolving, considering you definitly have
problems looking up "localhost" (which really should always work). Can
you ping to arbitrary dns names? Or specifically to the DNS name you're
trying to connect to?

//Magnus

pgsql-general by date:

Previous
From: "Bradley W. Dutton"
Date:
Subject: pg_hba.conf errors
Next
From: Ashley Moran
Date:
Subject: Re: How to use views&rules to dynamically choose which table to update