[comp.protocols.tcp-ip] Wollongon TCP/IP for AT&T 3B2

fedor@DEVVAX.TN.CORNELL.EDU (Mark Fedor) (08/03/87)

	Yeah, I run the same wollengong software on my 3b2/300 and
	the 513/udp port is the rwhod.

	I have a gateway (Proteon p4200) that picks these up all the
	time (since they are a broadcast) and reports
	"no server port 513" or some such and throws it away.

	Kill the rwhod if you don't want the port 513 annoyance.

	BTW, port 513/tcp is the rlogin port.

	Mark

	Also, my sendmail accepts "."'s I believe.....

	I have noticed that the wollongong telnet sometimes has difficulty
	establishing a connection with other telnet daemons.  Have you?

	Also, the routed program doesn't seem to work, but early versions of
	routed never worked anyways..... :^)

	This tcp/ip software really makes the 3b2 halfway useable!

hsu_f@osupyr.UUCP (Frank Hsu) (08/05/87)

I got your message.

Yes, our Physics Dept. told me that their CAD/CAM IBM 4341 always receive packets from the 3B2 looking for port 513.  I did not the reason.  Now I stopped
the RWHO daemon.

Our "mailx" really have problems with dots in the host names.  I reported
this problem to AT&T, a technical support person in AT&T information system
told me that "telnet" and "ftp" have no problem with dots.  But "mailx" just
can not take any dots in the host name.

I kept the mail message from AT&T, I will mail it to you later.

Our "telnet" on the 3B2/300 works fine.  It can login to Pyramid, IBM 3081,
iBM 4341, DEC VAX 11/780, Sun work stations, DEC-20.  I can not see any
difficulty in connecting to other hosts.

I never tried routed "mailx".  

						Frank C. Hsu
						IRCC, Ohio State Univ.
						Columbus, Ohio 43210