RE: TCP2617 Reason Code 2 and Reason Code 3 -- MIDRANGE-L

Subject: RE: TCP2617 Reason Code 2 and Reason Code 3
From: Bryce Martin <BMartin@xxxxxxxxxxxx>
Date: Thu, 25 Mar 2010 13:23:18 -0400
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>

We've tossed around the idea of a crossover cable, but this *SHOULD* work.
Know what I mean?

Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777

"Musselman, Paul" <pmusselman@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/25/2010 12:24 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: TCP2617 Reason Code 2 and Reason Code 3

Bryce--

We have a similar configuration-- 2 machines, 1 room, Ethernet between
them.

Only our Ethernet connection is a crossover cable-- no switch, no
router, just copper.

Knock on wood, it's been a very reliable configuration for several
years...

Paul E Musselman

Follow-Ups:

RE: TCP2617 Reason Code 2 and Reason Code 3 , Musselman, Paul

This mailing list archive is Copyright 1997-2026 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.