RE: able to TELNET not able to socket connect thru program -- MIDRANGE-L

Subject: RE: able to TELNET not able to socket connect thru program
From: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
Date: Thu, 16 Nov 2006 11:16:39 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Depends on the source of the port.  Ping was probably not ported from
Unix where Telnet was?  Just a guess. 


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: Thursday, November 16, 2006 11:11 AM
To: Midrange Systems Technical Discussion
Subject: RE: able to TELNET not able to socket connect thru program

Ping from iseries gives you a different result.
Ping 010.010.011.001
Verifying connection to host system 010.010.011.001.  

Seems like ping in iseries does not treat leading 0 number as octal.
But it will treat it as octal when uses telnet.

As an Amazon Associate we earn from qualifying purchases.

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.