> OK - it's good to simplify :-) > You should not need to INPUT rule for 8080. I´t´s commented, it´s an old rule for something I used to have in that server > The delay in finding the default route is route's attempt at reverse > name resolution. Use route -n instead. Indeed, this is what I get in server2 -------- [root@linserv root]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 -------- > Our next step is to trace. From what address are you attempting to > telnet and where does that address live? I´m using a completly different address to try to access the server from the outside, to be more specific, I'm doing this at work and I'm using the computers in my house to do this test and nothing happens. If I telnet port 80 server2 directly from server1 I get this -to make sure it's working-: -------- root@mail:~# telnet 192.168.0.2 80 Trying 192.168.0.2... Connected to 192.168.0.2. Escape character is '^]'. ^] telnet> -------- Thanks dude Peace Juan Programmin' Python is like sugar... Sweet! ;)
