I am getting a "An address incompatible with the requested protocol was used" when trying to to do a domain build with Postgres. The environment : Windows 7 32 bit. Visual Studio 2008 Postgres 8.4 As well as my application i have tried the consol sample and that gives the same error. I have diabled the firewall with the same result. Both pgAdmin and the command line sql utility can connect and work without errors. I did the same thing with the consol sample on an xp machine and it works fine. Any ideas.
Updated at 11.11.2009 11:43:48Great thanks for the reply, I had googled before I submitted the request, but missed the solution that you replied with. When I get it working I'll post the solution as other people may have the same problem. On a separate issue, I am changing from SqlServer 2008 which I used for DO3 to Postgres for DO4 (mainly due to cost) have you done any performance comparisons between Postgres and SQLServer 2008 for DO4. tony Updated at 11.11.2009 15:24:31Thanks I'll give that provider a go. I did notice two days a go when I was investigating my postgres there was a later version of the provider available then the one bundled with the DO4 install, I tried it but it did not make any difference. I don't know if this version contains your fix. This thread was imported from our support forum. The original discussion may contain more detailed answer. |
Alex (Xtensive) wrote:Since the original error is "System.Net.Sockets.SocketException: An address incompatible with the requested protocol was used", I suspect the problem isn't related to DO4. Try to Google it. Dmitri Maximov (Xtensive) wrote:Hello Tony, The problem might be in the following: Windows XP has IPv4 protocol stack only whereas Windows 7 has both IPv4 & IPv6 stacks and it seems that your PostgreSql 8.4 server listens to IPv6 address by default while you are trying to connect to IPv4-based address. Hope this helps. Dmitri Maximov (Xtensive) wrote:
We had developed the patch for npgsql project with much more efficient algorithm (http://pgfoundry.org/tracker/index.php? ... 0&atid=592) and it was immediately approved but unfortunately updated version of npgsql provider is not released yet. I'd recommend you to to use the fixed version of npgsql provider, so you can rather download the source code from PgFoundry (http://pgfoundry.org/scm/?group_id=1000140) and build it by yourself or I could send ready to use npgsql assembly by e-mail. But anyway, this fix is highly recommended. Alex (Xtensive) wrote:
More precise info:
|