On Sat, 08 Apr 2006 01:53:38 GMT, Greg Hackney <hackney@swbell.net>
wrote:

>gb_xxxx@verizon.net wrote:
>> I have the same problem.
>>
>> Step 1 -- Works with 127.0.0.1 or localhost
>> Does not work with actual IP address of the server
>> (Verizon)
>>
>> Step 2 -- Works as long as I give the assigned IP address (192.168..)
>>
>> telnet actualIP 25 -- hangs up. Same with the name
>
>Then port 25 probably isn't open from a networking standpoint. It's likely either in
>your system's firewall rules (such as iptables), or in your internet router.
>
>For example on my home system, I use internet connection sharing, where all my
>systems have their own 192.168 address, but appear as a single dynamic IP address on the Internet.
>I had to initially configure my connection sharing device to tell it to allow port 25 TCP, and
>to tell it which of the 192.168 addresses it should be routed to.

I use a LINKSYS router, and also have a dynamic IP address thru
Verizon. Similar to your config.

Let us say, I have 3 different machines in my home. They have been
assigned static IP addresses 192.1681.1.101, 192.168.1.102,
192.168.1.103. The mailserver is on 192.168.1.101

I can do telnet from 102 and 103 machines: telnet 192.169.1.101 25 --
successfully. I think that indicates that router is allowing port 25.

But even on the mailserver, if I do "telnet IPaddress 25" (I chec my
IPaddress thru nslookup). it will fail. However, I am able to
successfully do a SSH from any machine (even from my work). That uses
port 22. Does it mean Verizon is blocking port 25 (incoming).