RE: TCP/IP Route Question

IS should have been IP but you understood me even with my horrible
typing. 


Christopher Bipes

IS Director

CrossCheck, Inc. 

707.586.0551, ext. 1102

707.585.5700  FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com



Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Thursday, November 24, 2005 11:53 AM
To: Midrange Systems Technical Discussion
Subject: RE: TCP/IP Route Question

That explains it.  Thanks!

Brian.

-----Original Message-----
From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
Sent: Thursday, November 24, 2005 2:46 PM
To: Midrange Systems Technical Discussion
Subject: RE: TCP/IP Route Question

That IS 192.168.0.20 is on the same subnet as your system, therefore you
do not need a route to it.  Any IP on 192.160.0.xxx is direct and does
not need a route.  You should be able to ping that with out needing a
route.