Maxim kovgan wrote:
> John Summerfield wrote:

>>> It's most probably tcpwrappers
>>
>> No. That allows a connexion, then rejects it. You don't get "no route" 
>> or "refused messages."
> 
> AFAIK tcpwrappers refuse too.

1. How is that possible? By the time it can get the IP address,  it's 
accepted the connexion.
2. I speak from experience of using tcpwrappers to shield ssh. Instead 
of "refused," it's "reset."



> but I somehow missed the no route to.. :)
> and you're right! it needs some investigation:
> 
> 1. ping to the host
> 2. traceroute to the host.

:-)
A decent firewall prevents standard traceroute, much to my sorrow. I 
must remember to use "-I."


-- 

Cheers
John

-- spambait
[log in to unmask]  [log in to unmask]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)