On Fri, 16 Jun 2006, Kwan Lowe wrote:
>>> In that case there might be more to this. You can telnet to port 25
>>> on the external interface of your router to be sure it's dropped or
>>> rejected.
>>
>> eben@pc:~$ telnet royalty.no-ip.org 25
>> Trying 72.64.xxx.xxx...
>> (long pause)
>> telnet: Unable to connect to remote host: Connection timed out
>
> BTW, if you do this from within a LAN behind that public address (i.e.,
> using some sort of commodity router/firewall) then be aware that most do
> not let you attach to the public IP from inside the network. If you're
> port forwarding to a private address then you don't need to check the
> public IP (that's on the firewall) so checking the port on the private
> will be fine.
Like this?
root@pc:~# telnet 192.168.1.11 25
Trying 192.168.1.11...
telnet: Unable to connect to remote host: Connection refused
-- -eben QebWenE01R@vTerYizUonI.nOetP http://royalty.no-ip.org:81"You're one of those condescending Unix computer users!" "Here's a nickel, kid. Get yourself a better computer" - Dilbert ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:10:57 EDT