Hi Andy/Joris, This is what my /sbin/iptables -L looks like: Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ftp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:smtp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:postgres REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Thanks. George [EMAIL PROTECTED] wrote: Hi George, As Joris said, we need you to try what he has suggested. The fact you can now connect via SSH proves PostgreSQL is set up and configured correctly, which would point to a firewall or intermediate router blocking your connections. On the server (as root), do "iptables -L" or "/usr/local/sbin/iptables -L" if the previous doesn't work, and post the full output so we can see if a software firewall is blocking. And please try and get some information about your network - who set the server up, is there a hardware firewall or router firewall in between you and the server, etc. Thanks Andy. George Heller wrote: > Hi, > > Ok, I have reached to the point where the SSH tunelling works, and I am able > to connect using it to PgAdmin. But I still want to know what exactly is wrong > with the other setup. > > I just came across this in the postgres documentation, about starting the > postmaster with an -i option, if you want your server to accept TCP/IP > connections. > http://www.postgresql.org/docs/7.4/static/postmaster-start.html > > I just used the -D option as specified, to start the server. Is it necessary > to use the -i option so that my server can listen, or is the documentation just > too old? If yes, what is the syntax for the same? > > Thanks. > George. > > Joris Dobbelsteen wrote: > >-----Original Message----- > >From: Andy Shellam [mailto:[EMAIL PROTECTED] > >Sent: woensdag 25 april 2007 21:25 > >To: Joris Dobbelsteen > >Cc: George Heller; pgadmin-support@postgresql.org > >Subject: Re: [pgadmin-support] Server not listening > > > >I concur, but just so you know I suggested SSH so George can > >get up and running quickly while diagnosing the problems later > >as it requires a lot of information he doesn't seem to have. > >We've already established he has SSH access so it seemed an > >obvious way to connect so he could actually begin to use PostgreSQL. > > Hopefully you took no offence while I took this a sharp turn. > > I agree that this would be probably a good idea to get it working. > Alternatively it might seem easier to have a temporary set up on the > local computer, if feasable. > > [snip] > > - Joris Dobbelsteen > > > > > --------------------------------- > Ahhh...imagining that irresistible "new car" smell? > Check outnew cars at Yahoo! Autos. > > !DSPAM:37,4636eb7689291063614559! > _________________________________________________________ DISCLAIMER This e-mail was sent through a Mail Network server. The Mail Network accepts no liability for it's content. --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.
