Re: Problem with Remote Telnet to the 400

First the warning, you are opening the AS/400 up to everyone not just you,
and all services not just telnet.

go cfgtcp
2. Work with TCP/IP routes
1=Add
Route            Subnet           Next             Preferred
Destination      Mask             Hop              Interface

*DFTROUTE        *NONE           the.routers.ip.address     *NONE

If that works I would at least remove the *DFTROUTE and try your ISP's ip
address here to limit it to just the people who use your ISP and not the
world. I have not tried this I have always used default route.

John Ross


At 12:48 PM 9/11/02 -0400, you wrote:

Hi again everybody -

I recently had a problem trying to telnet into a 400 from my home and here
are the details:

the 400 resides on a small LAN at a client...there are NO FIREWALLS in front
of anything. The IP address to which it is identified is a public one, not
private. There are other web server units attached to the LAN. When I tried
to Telnet the address, the connection window displayed but never completed,
timing out. When I tried to Ping, it timed out. When I tried to Ping one of
the web servers though, IT WORKED! When I ran a TRACERT for both 400 and
server, the exact same hop count existed except the web server extended 1
past to complete the connection: the 400 couldn't.

Are there TCPIP configuration issues here? Help?

Gracias,

Rick Rayburn



_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.