Path: utzoo!attcan!uunet!crdgw1!sagittarius!dixon
From: dixon@sagittarius.crd.ge.com (walt dixon)
Newsgroups: comp.protocols.appletalk
Subject: Re: more MACtcp/telnet problems
Message-ID: <5255@crdgw1.crd.ge.com>
Date: 14 Feb 90 14:31:50 GMT
References: <ID4610.D900213.T121107.CJM@UNB.CA>
Sender: news@crdgw1.crd.ge.com
Reply-To: dixon@sagittarius.crd.ge.com (walt dixon)
Organization: General Electric Corp. R&D, Schenectady, NY
Lines: 28

> I am trying to use the MACTCP version of NCSA's Telnet in a setup where
>  my Gateway is not in the same Zone as my Telnet session. I am having
>  with this. My Gateway and Telnet session cannot seem to communicate.
>  I have investigated the problem and found that it seems to be
>  with MACTCP. When I first start a Telnet session it uses NBP to
>  try to tell the gateway about itself. Instead of sending this
>  to the gateway it stays in the current zone. ( instead of putting
>  the zone name at the end of the string it puts a * ). It does this
>  even though a have configured MACTCP with the Gateway address and
>  have selected the zone the gatway is in on the first configuration
>  panel.

We had a similar problem.  It's not really clear whether the gateway
or MacTCP is doing something wrong.  When MacTCP opens a session,  it
does a NBP request looking for gateways.  The gateway (kinetics in our
case) responds,  but it uses its backbone address rather than its 
local address.  MacTCP will only talk to gateways in its own zone.
We solved the problem (with the aid of a very helpful Apple MacTCP
developer) by changing the netmask in the MacTCP configuration to
ff000000.  This change solved our problem.

Walt Dixon	{arpa:		dixon@crd.ge.com	}
		{us mail:	ge crd			}
		{		po box 8		}
		{		schenectady,  ny 12301	}
		{phone:		518-387-5798		}

Walt Dixon dixon@crd.ge.com