Results 1 to 5 of 5
  1. #1
    Join Date
    Jun 2010
    Posts
    3

    Red face Unanswered: Unable to connect Postgresql on client computer

    I have developed application in Visual Basic 6 using postgresql and it is working very good on main/server computer. I have done settings in pg_hba.conf and postgresql.conf too for all remote connections and ip address settings. That is why I can able to run the application on main server through using ip address or computer name in connection string.

    Now the problem is when I try to connect main server computer from client computer it shows error that Could not connect...timeout occurred.

    The application is developed using Microsoft Visual Basic 6.
    Please kindly show me how to resolve this.

  2. #2
    Join Date
    Aug 2009
    Location
    Olympia, WA
    Posts
    337
    It could be a bunch of things. Is it on the same subnet? Is the router allowing that traffic? Is postgres configured properly? We don't know. Post the relevant sections of pg_hba.conf and postgresql.conf and we may be able to help a bit.

  3. #3
    Join Date
    Jun 2010
    Posts
    3

    Shall I send you the postgre files

    I have configured the postgresql as per the given on net for allow access through other ip address
    Yet this is in same subnet.

    If you allow then I can able to send you the postgresql conf files.

    please give me your email ID.

  4. #4
    Join Date
    Jun 2010
    Posts
    3

    pg_hba.conf file

    # PostgreSQL Client Authentication Configuration File
    # ================================================== =
    #
    # Refer to the "Client Authentication" section in the
    # PostgreSQL documentation for a complete description
    # of this file. A short synopsis follows.
    #
    # This file controls: which hosts are allowed to connect, how clients
    # are authenticated, which PostgreSQL user names they can use, which
    # databases they can access. Records take one of these forms:
    #
    # local DATABASE USER METHOD [OPTION]
    # host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
    # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
    # hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
    #
    # (The uppercase items must be replaced by actual values.)
    #
    # The first field is the connection type: "local" is a Unix-domain socket,
    # "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
    # SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
    #
    # DATABASE can be "all", "sameuser", "samerole", a database name, or
    # a comma-separated list thereof.
    #
    # USER can be "all", a user name, a group name prefixed with "+", or
    # a comma-separated list thereof. In both the DATABASE and USER fields
    # you can also write a file name prefixed with "@" to include names from
    # a separate file.
    #
    # CIDR-ADDRESS specifies the set of hosts the record matches.
    # It is made up of an IP address and a CIDR mask that is an integer
    # (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
    # the number of significant bits in the mask. Alternatively, you can write
    # an IP address and netmask in separate columns to specify the set of hosts.
    #
    # METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
    # "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
    # in clear text; "md5" is preferred since it sends encrypted passwords.
    #
    # OPTION is the ident map or the name of the PAM service, depending on METHOD.
    #
    # Database and user names containing spaces, commas, quotes and other special
    # characters must be quoted. Quoting one of the keywords "all", "sameuser" or
    # "samerole" makes the name lose its special character, and just match a
    # database or username with that name.
    #
    # This file is read on server startup and when the postmaster receives
    # a SIGHUP signal. If you edit the file on a running system, you have
    # to SIGHUP the postmaster for the changes to take effect. You can use
    # "pg_ctl reload" to do that.

    # Put your actual configuration here
    # ----------------------------------
    #
    # If you want to allow non-local connections, you need to add more
    # "host" records. In that case you will also need to make PostgreSQL listen
    # on a non-local interface via the listen_addresses configuration parameter,
    # or via the -i or -h command line switches.
    #



    # TYPE DATABASE USER CIDR-ADDRESS METHOD

    # IPv4 local connections:
    host all all 127.0.0.1/32 md5
    # IPv6 local connections:
    #host all all ::1/128 md5
    host all all 192.168.0.1/24 md5
    host all all 0.0.0.0/0 md5

  5. #5
    Join Date
    Nov 2006
    Posts
    82
    Does client ping server? Can you telnet to server port 5432 (I think it is the port postgres is listening to)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •