Xref: utzoo comp.protocols.tcp-ip:4811 comp.protocols.nfs:8
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!genrad!decvax!eagle_snax!geoff
From: geoff@eagle_snax.UUCP ( R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.nfs
Subject: Re: Telnet to a tcp port other than 23
Message-ID: <369@eagle_snax.UUCP>
Date: 6 Oct 88 13:47:52 GMT
References: <282@pbseps.UUCP> <23648@hi.unm.edu> <284@pbseps.UUCP> <732@mailrus.cc.umich.edu>
Reply-To: geoff@eagle_snax.UUCP (Geoff Arnold @ Sun ECD - R.H. coast near the top)
Organization: Sun Microsystems - East Coast Division
Lines: 19

I've posted a bug on the failure of PC-NFS Telnet to use \nfs\services
to determine the port to be used. However there is a workaround for now.
Instead of invoking the TELNET frontend, you can run the EMTELNET
program directly, using the following syntax:

	emtelnet IPADDR -p PORT -h HOST -e EMUL -d NFSDRIVE

for example

	emtelnet 192.9.215.185 -p 23 -h cookie -e VT100 -d C

The IPADDR and HOST refer to the same system: the HOST name is
used only for display purposes. (The objective here is to keep
the name resolution code out of the potentially TSRable Telnet runtime.)
-- 
Geoff Arnold, Sun Microsystems Inc.+------------------------------------------+ 
PC Distrib. Sys. (home of PC-NFS)  |If you do nothing, you will automatically |
UUCP:{hplabs,decwrl...}!sun!garnold|receive our Disclaimer of the Month choice|
ARPA:garnold@sun.com               +------------------------------------------+