Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!drutx!cac
From: cac@drutx.ATT.COM (ConkeyCA)
Newsgroups: comp.sys.att
Subject: Re: WIN TCP/IP
Message-ID: <5178@drutx.ATT.COM>
Date: Wed, 2-Sep-87 12:39:00 EDT
Article-I.D.: drutx.5178
Posted: Wed Sep  2 12:39:00 1987
Date-Received: Sat, 5-Sep-87 06:43:09 EDT
Distribution: comp
Organization: AT&T, Denver, CO
Lines: 31
Keywords: ATT WIN TCP/IP


in article <417@udiego.UUCP>, stokes@udiego.UUCP (David M. Stokes) says:
> Anyone else using AT&T WIN TCP/IP? Supposedly (one passage in small
> print) the TCP/IP and 3bnet are compatable and will run at the same time
> (but you end up with 8,432.5 daemons running).
> 
> This isthe first software that AT&T is marketing that really impresses
> me!
> 
> 
> -- 
> David Stokes                   "USD where the future is tomorrow
> Academic Computing Department   and today is slightly behind schedule"
> University of San Diego

We have a network of 10 3b2's (plus several Sun's, H.P's, ect and a Vax 11/780) 
all running on top of AT&T WIN TCP/IP. 
We also have set up our print operations using the remsh and rcp commands
to our Computer Center Vax. This gives us access to the Comp. Center printers.
For Text format jobs on the Vax, we set it up as follows:

		rcp Text.job vax:/tmp/text.job
		remsh vax formatter /tmp/text.job      (formatter = troff, nroff, ect)
		rcp vax rm /tmp/text.job


We've had 100% reliability so far.

Curtis Conkey 
AT&T Information Systems 
Denver, Colorado