Can't access login screen :2222 on new CentOS 5.3 install

[blaszlo]

Hey guys,

I have installed DA on probably 20 CentOS machines older than 5.0 with no problem, I decide to give CentOS 5.3 a try, and now after the install I can't access the login on :2222 externally. When typing the IP:2222 from the machine itself, it works fine. Any ideas? Maybe I'm overlooking something in my firewall. Here is the result of netstat -at:

tcp        0      0 localhost.localdomain:2208  *:*                         LISTEN
tcp        0      0 *:imaps                     *:*                         LISTEN
tcp        0      0 *:pop3s                     *:*                         LISTEN
tcp        0      0 *:mysql                     *:*                         LISTEN
tcp        0      0 *:submission                *:*                         LISTEN
tcp        0      0 *:rockwell-csp2             *:*                         LISTEN
tcp        0      0 *:pop3                      *:*                         LISTEN
tcp        0      0 *:imap                      *:*                         LISTEN
tcp        0      0 *:sunrpc                    *:*                         LISTEN
tcp        0      0 *:16851                     *:*                         LISTEN
tcp        0      0 *:ftp                       *:*                         LISTEN
tcp        0      0 72.236.153.56:domain        *:*                         LISTEN
tcp        0      0 host.ptihosting.com:domain  *:*                         LISTEN
tcp        0      0 localhost.localdomai:domain *:*                         LISTEN
tcp        0      0 192.168.122.1:domain        *:*                         LISTEN
tcp        0      0 *:nlogin                    *:*                         LISTEN
tcp        0      0 localhost.localdomain:ipp   *:*                         LISTEN
tcp        0      0 localhost.localdomain:rndc  *:*                         LISTEN
tcp        0      0 *:smtp                      *:*                         LISTEN
tcp        0      0 localhost.localdomain:2207  *:*                         LISTEN
tcp        0      0 *:http                      *:*                         LISTEN
tcp        0      0 *:ssh                       *:*                         LISTEN
tcp        0      0 *:https                     *:*                         LISTEN
tcp        0   2772 host.ptihosting.com:ssh     ::ffff:72.236.153.249:4275  ESTABLISHED

 

[nobaloney]

Have you tried shutting off the firewall?

# service iptables stop

Jeff

 

[blaszlo]

Sorry, forgot to post back - I have turned IPtables off and am able to access it now - I guess what I am puzzled about is all of the rules in teh firewall should allow access to the server, and it doesnt (except for SSH). Here is the result of iptables -L -v...

[root@host ~]# iptables -L -v
Chain INPUT (policy DROP 99 packets, 13771 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- lo any anywhere anywhere
129 14814 ACCEPT all -- any any anywhere anywhere state RELATED,ESTABLISHED
2 96 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh

Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 195 packets, 16714 bytes)
pkts bytes target prot opt in out source destination

Chain RH-Firewall-1-INPUT (0 references)
pkts bytes target prot opt in out source destination

Do you guys see any reason why anything should be blocked, besides routing?