Re: Conexion

No uses el formato CIDR para la red, probá usando la máscara de red
directamente.
en vez de [host all all 200.100.5.66/16 md5] usa [host all
all 200.100.5.66 255.255.0.0 md5]
Creo que en una oportunidad lo solucione así.
Saludos.

GABRIEL COLINA escribió:

> Lamentablemente no tengo la respuesta de por que no te anda, pero
> te mando un ejemplo de uno que si funciona.
>
> Espero te sirva
>
> # PostgreSQL Client Authentication Configuration File
> # ===================================================
> #
> # Refer to the PostgreSQL Administrator's Guide, chapter "Client
> # Authentication" for a complete description. 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", "samegroup", 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 (IPv6) 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",
> # "krb4", "krb5", "ident", or "pam". 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
> # "samegroup" 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 192.168.1.8 255.255.255.0 trust
>
>
> */Mauricio Delgado Pino <mauriciodelgadopino(at)yahoo(dot)es>/* escribió:
>
> Instale PostgreSQL 8.2 en un windows 2000 server / trate de que
> mis jefes cambiaran a linux pero con suerte me dejaron usar postgres
> si
> que con calma
>
> para conexiones remotas modifique el archivo pg_hba.conf de la
> sigente manera
>
> host all all 127.0.0.1/32 md5
> host all all 200.100.5.66/16 md5
>
> pero al tratar de cambiar el 127.0.0.1 por 200.100.5.66 que es la
> ip local de la maquina despues no me deja entrar via pgadmin III
> y cuando trato de acceder desde mi aplicacion al servidor no me deja
>
> ¿Que estoy haciendo mal?
>
> el lissten_addres del postgres.conf lo cambie por la direccion
> local y sige el mismo problema
>
> ¿A que se debe?
>
>
>
> __________________________________________________
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
> Regístrate ya - http://correo.espanol.yahoo.com/
>