[NTLUG:Discuss] port 22 "filtered"

Thomas Cameron thomas.cameron at camerontech.com
Sun Mar 14 11:11:38 CST 2004


> I tried
> service iptables stop
> but have yet to try:
> service ipchains stop
>
> Thanks for that tip.
>
> But, I may have been barking up the wrong tree all the time, I now see
> that traceroute hangs after the 6th hop:
>   6  sl-bb22-fw-8-0.sprintlink.net (144.232.19.213)  15.403 ms  16.487
> ms  15.288                                             ms
>   7  sl-bb27-fw-12-0.sprintlink.net (144.232.11.33)  16.866 ms  18.097
> ms  17.195                                             ms
>   8  sl-st20-dal-1-0.sprintlink.net (144.232.9.136)  23.167 ms  21.523
> ms  15.170                                             ms
>   9  sl-sbcint-3-0.sprintlink.net (144.228.250.110)  16.690 ms  17.306
> ms  16.067                                             ms
> 10  bb2-p15-0.rcsntx.sbcglobal.net (151.164.191.230)  36.799 ms  23.611
> ms  23.6                                            71 ms
> 11  dist1-vlan32.rcsntx.swbell.net (151.164.253.211)  21.589 ms  22.137
> ms  17.2                                            24 ms
> 12  bras4-g12-0.rcsntx.sbcglobal.net (151.164.162.134)  24.020 ms
> 24.198 ms  24                                            .993 ms
> 13  * * *
> 14  * * *
> 15  * * *
> etc. till it times out.

OK, let me see if I have a firm understanding of the scenario:

This is a remote machine, right?  You are trying to ssh from somewhere
(home, maybe) to a machine that is somewhere else (like at a datacenter
somewhere).  You can't ping or ssh to that machine.

So how are you able to log in and check firewall rules and the like?

Where did you run your nmap from?  Is it possible that there is a firewall
between your source and destination that you are not aware of?  If you ran
'service iptables stop' then 'service ipchains stop' will likely result in
nothing but some kernel module error messages (iptables and ipchains are
mutually exclusive).

Thomas




More information about the Discuss mailing list