I have now isolated the problem to the firewall as suspected. I found that when I disabled Kaspersky firewall the bloody Windows firewall would kick in unbeknown to me. Once that was disabled as well then I could connect from another machine on the LAN. So the next step is easy, configure Kaspersky to let it through. Chris, Thank you very much for your help it is really appreciated. I guess I would have got there in the end but it always helps when someone else throws ideas at you. Thanks again, Alan. -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Alan Deane Sent: 30 July 2009 03:15 To: alan@xxxxxxxxxxxxx; 'Chris' Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: V8.3 fails to start after unremming hba_file = 'ConfigDir/pg_hba.conf' Ok, I have just had a look at the firewall network monitor (Open Ports) and the following is showing. 5432 TCP POSTGRES.EXE -D "G:/PROGRAM FILES/POSTGRESQL/8.3/DATA" 127.0.0.1 02:11:46 4141 UDP POSTGRES.EXE -D "G:/PROGRAM FILES/POSTGRESQL/8.3/DATA" 127.0.0.1 02:12:56 Which looks OK to me. I uses more investigation is required Alan -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Alan Deane Sent: 30 July 2009 03:00 To: 'Chris' Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: V8.3 fails to start after unremming hba_file = 'ConfigDir/pg_hba.conf' Hi Chris, I can connect to the server locally with PgAdmin using localhost: 5432 192.168.2.99: 5432 127.0.0.1 : 5432 As for the Windows event logs they are all fine. The server logs. Look OK except for %LOG: invalid length of startup packet which could have been when I was trying to telnet in. What is very interesting is the following from the Status log I have three connections now, all from my local machine, local host, 127.0.0.1 and 192.168.2.99 and what is very interesting is the following from the Status log is the client column. 192.168.2.99:3321 127.0.0.1:3237 127.0.0.1:3223 Which is telling me that it is using different outgoing ports. Which means it will probably be a problem with the firewall as I think I set both incoming and outgoing to 5432. Will have to go and see if changing the outgoing to any makes a difference. Will reports back soon. Thanks, Alan. -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Chris Sent: 30 July 2009 02:23 To: alan@xxxxxxxxxxxxx Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: V8.3 fails to start after unremming hba_file = 'ConfigDir/pg_hba.conf' Alan Deane wrote: > Sorry, yes the error, Doh!. > > Standard Server doesn't Listen (sounds like my ex :)) > > Here it is in full. > > Server doesn't listen > > could not connect to server; Connection timed out (0x0000274C/10060) Is the > server running on host 192.168.2.99 and accepting TCP/IP connection on port > 5432? Anything in the postgres logs or windows event logger? Can you manually telnet to that? Try - from the postgres server back to itself (127.0.0.1 5432) - from the postgres server to it's ip (2.99) - from another machine It still sounds like it's firewall related. -- Postgresql & php tutorials http://www.designmagick.com/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
