Path: utzoo!attcan!uunet!ccicpg!turnkey!stanton!donegan
From: donegan@stanton.TCC.COM (Steven P. Donegan)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: connecting Internets?
Summary: Request for clarification
Message-ID: <44@stanton.TCC.COM>
Date: 22 May 88 15:25:27 GMT
References: <8805210151.AA09745@ucbvax.Berkeley.EDU>
Organization: Stanton Public Domain Systems, Stanton, Ca.
Lines: 24


I hope this isn't a hopelessly stupid question but:

In the network I am attempting to build at my employer's site(s) we have a class
B primary address 129.253.x.x and many workstations from many diverse vendors.
The network backbone spans many buildings and countries via MAC level bridges.
Most of the TCP/IP devices (our network is primarily XNS and DECNET) are of the
SUN persuasion, one server with both MAU and thinwire interfaces, the thinwire
running to 5 or 6 workstations and the MAU connecting to the backbone. The
problem I have run into on a continuous basis is the situation where, even
though the packets are capable of being seen by all parties, a host rejects a
connection because (I think) the destination/source pair are in a different
'subnet' ie 129.253.001.x and 129.253.002.x. Is there any way under legal
TCP/IP to get these blasted devices to talk to each other without buying a
hardware device such as a gateway or router? I feel that the 'feature' of
subnetting in my particular network is really a major LIMITATION! I have NONE
of these types of problems with my XNS or DECNET devices. Help. Please, no
flames for stupidity, I've been networking systems for a living for quite a
while and am really interested in learning about this subject.
-- 
Steven P. Donegan
Sr. Telecommunications Analyst
Western Digital Corp.
donegan@stanton.TCC.COM