× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Can PCs with working telnet sessions ping the i? Yes - full
connectivity as always before. No changes have been made to anything on
our network in Years. Makes you wonder if/when this will happen again?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, July 08, 2010 11:48 AM
To: Midrange Systems Technical Discussion
Subject: RE: Telnet snafu ???

Can PCs with working telnet sessions ping the i?

By cannot ping the i do you mean it resolves the name of the i to an IP
address and tries to ping that IP address and fails? For example, if I
try to ping asfd9dkd98f878fsadd813.com I may ping request could not find
the host. But if I try ibm.com it may then say Pinging ibm.com
[129.42.38.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 129.42.38.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), This doesn't
necessarily mean that all of ibm.com is down. It means that the network
people block pings. The uninitiated often do this because they read
somewhere that pings can be used to mount a Denial Of Service attack and
haven't read all the methods of still allowing ping without being
exposed to DOS attacks.
See also C:tracert ibm.com


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 07/08/2010 12:27 PM
Subject: RE: Telnet snafu ???
Sent by: midrange-l-bounces@xxxxxxxxxxxx



The ISeries cannot ping these certain PCs on our network. Those same
PCs CAN ping all the Windows servers around the network, but they CANNOT
ping the IP address of the ISeries ??

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, July 08, 2010 10:05 AM
To: Midrange Systems Technical Discussion
Subject: Re: Telnet snafu ???

I'd start here
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzaiw/rzai
wdetprobtelnet.htm


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Date: 07/08/2010 10:50 AM
Subject: Telnet snafu ???
Sent by: midrange-l-bounces@xxxxxxxxxxxx



HELP

Experiencing really strange conditions. From our local as well as
remote locations, our Mochasoft telnet client will NOT CONNECT. Yet,
this is NOT on all PCs. There are some at the local site, and some at
the remote site which remain connected and working!

In addition, I am able to ping to and connect to these PCs (both local
and remote) which are NO LONGER able to get the telnet connection to the
ISeries.

TIA

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.