Re: Ping/etc. Problems

Neil:

As with my question to Jim, I have to say that this is not what I've 
experienced. When I've seen duplicates on an AS/400, they have always been 
exactly that -- duplicate responses, the original always showed up as well. In 
every case I've seen, they were caused by misconfiguration either of TCP/IP on 
the AS/400 or of the network itself. Working over various comm connections in 
Alaska, I saw numerous timeouts, but never one reported as a duplicate.

It looks like I'm actually going to have read about TCP/IP. Was hoping I could 
avoid it.  <g>

Tom Liotta

On Fri, 13 July 2001, Neil Palmer wrote:

> When you get a reply after the wait interval (default 1 second) the 400 
> will identify them as (Duplicate) as in this example:
> 
> ping someplace
> Verifying connection to host system someplace at address 999.999.0.240.  
> No response from host within 1 seconds for connection verification 1.
> No response from host within 1 seconds for connection verification 2.
> PING reply 1 from 999.999.0.240 took 2142 ms. 256 bytes. TTL 236. 
>   (Duplicate) 

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---