Unable to connect to SOAPware Server

    Table of contents
    No headers

    There are two settings in PostgreSQL's configuration files that can affect SOAPware running on client computers. If you are not able to run SOAPware on your clients and connect to the server, it is possible that you need to make the proper changes in your PostgreSQL configuration files located on the server.

    There are two places to look to make sure PostgreSQL is configured to allow connections from client computers. On your server computer, perform the following steps:

    1. Check the pg_hba config file.
      1. Click on Start, then All Programs, PostgreSQL 8.x,Configuration Files and Edit pg_hba.conf.
      2. Scroll to the bottom of the file. You should see two lines under # IPv4 local connections that appears as below:

        host       all                all             127.0.0.1/32                  md5
        host       all                all              0.0.0.0/0                      password

        If you do not see the second line, type it in just like it is above.
      3. Click on File, Save. You can close the file now.
    2. Check the postgresql config file.
      1. Click on Start, All Programs, PostgreSQL 8.x, Configuration Files and Edit postgresql.conf.
      2. Scroll down just a little bit until you see:

        # - Connection Settings -

        listen_addresses = '*'

        Make sure the listen_addresses line looks just as that. If it has a pound sign (#) in front of it, remove the pound sign. If an asterisk (*) is not inbetween the two single quotes on the right side, change it to an asterisk.
      3. Click on File, Save. You can close the file now.
    3. If you made changes to either file, then you must restart the PostgreSQL Database Server to force the changes into effect. Click on Start, All Programs, PostgreSQL 8.x, Stop Service. Now after that window goes away, click on Start, All Programs, PostgreSQL 8.x, Start Service.

     

    Now try running SOAPware on your clients.

    If SOAPware still doesn't connect or these configuration files were already correct when you checked them, it is possible that a firewall could be preventing a successful connection. A firewall on your server or your client computers can both prevent a connection, so make sure and check each computer. For SOAPware to function, it needs to communicate over port 5432. Make sure this port is open in your firewall settings.

    Page last modified 19:09, 17 Apr 2009 by rpetty
    Page Tags:
    • No tags
    Comments
    Copyright © 2008 SOAPware, Inc. All rights reserved. Contact UsNews Blog RSS Feed