Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!ysub!temngt23
From: TEMNGT23@ysub.ysu.edu (Lou Anschuetz)
Newsgroups: comp.sys.ncr
Subject: Another dumb TCP/IP Question
Message-ID: <90285.171552TEMNGT23@ysub.ysu.edu>
Date: 12 Oct 90 21:15:52 GMT
Organization: Youngstown State University VM system (YSUB)
Lines: 20

We are now successfully running the newest release of WINS TCP/IP
and the nameserver code works quite nicely thank you (and thanks
to all who have helped us get this far).  We are able to
successfully resolve any name into its real address.  Unfortunately,
having the address is not enough, and a connection cannot be made
if the route is not already present in our router.  netstats -r
does reveal that our system knows about all the routes stored
in the router, but we seem unable to get the system to dynamically
create a new path.  That is, if we try to connect somewhere that
our router doesn't already have a route defined for, we will simply
get a timeout.  Mail fails for the same reason since a two
way path cannot be created.  In most systems we have seen a
statement of the form DEFAULTROUTE, but can find no such mechanism
on our system.  We can use the "route add" command and things
will work, but this is obviously not a permanent solution.  If
there is something buried in the manual or in the menus for 4.01.00
I apologize for missing it, but can't seem to find it anywhere.

Any help would be appreciated!
temngt23@ysub.ysu.edu