I can telnet locally without any problems. Telnetting from a remote host
tries to connect however, it keeps trying forever that is, "trying
'xx.xxx.xx.xx' (my ip address), and stops there until I hit <control-c>. I
can also telnet from a remote host to my machine (not to port 25). The
web server, ftp server..both running ok (funny because I thought @home
also blocked httpd port). I gues they do this against spammers. Really
sucks for users that only want to use a linux box to its full
capability. I only need they block web services (http ftp etc) and I
would not have any reason to run linux anymore (and that won't be cool...).
another person mentioned tcp_wrappers. you can test this
too, if you telnet to port 25 on your machine does it
say connection refused? does it say no route to host? does
it accept the connection then drop it? i run my MTAs
as standalone(not through inetd). typical responses -
connection refused - service not running, not bound to IP,
or firewalled at some point between client and server
no route to host - service blocked at router at some
point between client and server. or your connecting
to the wrong system, or system is down.
connect then drops - server may be running from inetd and
may be misconfigured, server may be running from inetd
and tcp_wrappers is not allowing your host to connect.
nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
