I followed the instructions to network 2 computers. It said to go in and add a line to 2 files - pg_hba.conf and postgresql.conf. However, when I make these changes and then try to save the files, it says I don't have permission to save files in this location. I'm using Vista 8.3 and I'm guessing that's the problem. Is there a known solution to this problem?

The networking instructions I'm using are at: http://www.pokertracker.com/forums/v...hp?f=45&t=4638

You need to edit the file as administrator, like you run PT3 as administrator.
You should be able to do that by right clicking the shortcut in the Start menu to edit the file.

Okay I figured out how to chagne those files as administrator. Actually I turned off User Account Control.

So I went ahead and installed PT on my laptop (it was not already on there) and I did not install PostGresSQL there. Instead I want to use the database already on my desktop PC. Now I'm stumped cause PT on the laptop still can't find the database. What do I do now?

Have a look at the tutorials linked from the Database / PostgreSQL FAQ.

That's where I began. I feel like I'm going in circles. I can't find anything in there that tells me how to initially install the database on the second computer. Do I install PostGreSQL there? Or just point it to the version already resident on the desktop. If the latter, how do I point it there?

If you've got the version on your desktop networked properly (as your link from the first post would indicate), then you don't need to install PostgreSQL on your second computer at all; all you need to do is when you open PT3, use the IP address of your other computer as the server. Port is still 5432, user is still postgres, password is still dbpass. If you've followed that tutorial that you linked in your first post properly everything should work from there.

Okay on the ipconfig on my desktop I found the IP address "IPv4 Address (192.168.x.xxx). On the laptop in the postgresql screen I put...
Server: 192.168.x.xxx
Port 5432
DB User: postgres
Password: dbpass

It says "Unable to connect to this database. Please check the configuration."

Do I need to do something on the desktop to make the postgresql directories shared? If so, how do I do this and which directories?

Usually if I access anything on my desktop from the laptop, I have to put in my desktop user name and password. It's not asking me for those, so I don't think it knows to look at the desktop.

One more thing I discovered. I went through the windows explorer on my laptop, where I can access directories on my desktop. However, when I try to access the PostGreSQL directory in this way, it says "...refers to a location that is unavailable..." I tried specifically setting that directory to "Shared" and that didn't solve it. I'm stumped.

When you're following the above tutorial you're not sharing a directory what you're doing is getting PostgreSQL to recognize and allow access from other IP addresses.

Could you paste the contents of your pg_hba.conf here? Also, make certain you set listen_addresses = '*' in the postgresql.con and that the line does NOT have a # sign in front of it.

# 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.1.0/24 md5

You checked that the 1 is correct, using ipconfig?

Have you also added the:
listen_addresses = '*'
..line to postgresql.conf?

Have you restarted the PostgreSQL service on your desktop since you changed the files?

The 1 is correct. I did add the listen_addresses line. I had not restarted the service but now I did and restarted the pc, but still it's not working.

In ipconfig, I used the "IPv4 Address" (192.168.1.100) as that's the only one that looks right. There is also a Default Gateway 192.168.1.1. Also there is a IPv6 Address but its in a strange format "2001:0:4137:9e50 etc etc etc". Also a Link-local IPv6 Address which is also in that strange format.

Anyway I must be missing something. I'm stumped.

Honestly at this point the easiest thing at this point is probably to schedule a remote session and we'll get things sorted for you - it's probably something silly but it'll be much faster to see it directly rather than continue this back and forth.

I will do that. Thanks!