lance@embassy.nsi.com (Lance N. Antrim) (10/21/90)
with tcp/ip 1.0.1 and my Macintosh running NCSA Telnet. When it works, it works great. It even gives me dial-in access to my files on te Mac via ftp. However, my ability to open a session from th Mac to the Xenix box is intermittent. There is always a connection, but sometimes it holds for a login and sometimes it doesn't. If it didn't connect at all, then I would have some ideas of wht to look for, but when it works 10% to 20% of the time I am at a loss. Has anyone had similar problems of intermittent connections for telnet sessions? Since I do get some of the connections, I know that the files (/etc/hosts and other related files) are all there and correct, so I am stumped. Suggestions will be appreciated as I am just learning to set up and administer tcp/ip and telnet. Thanks, Lance Antrim lance@nsi.com
cliffb@cjbsys.bdb.com (cliff bedore) (10/23/90)
In article <108@embassy.nsi.com> lance@embassy.nsi.com (Lance N. Antrim) writes: >with tcp/ip 1.0.1 and my Macintosh running NCSA Telnet. When it works, >it works great. It even gives me dial-in access to my files on te Mac >via ftp. However, my ability to open a session from th Mac to the Xenix >box is intermittent. There is always a connection, but sometimes it >holds for a login and sometimes it doesn't. If it didn't connect at >all, then I would have some ideas of wht to look for, but when it works >10% to 20% of the time I am at a loss. > >Has anyone had similar problems of intermittent connections for telnet >sessions? Since I do get some of the connections, I know that the files >(/etc/hosts and other related files) are all there and correct, so I am >stumped. Suggestions will be appreciated as I am just learning to set >up and administer tcp/ip and telnet. > >Thanks, >Lance Antrim >lance@nsi.com I have had similar problems with the MIT/CMU PCIP telnet protocols trying to log on to Xenix. It would occasionally work but when we went from 1.0.1d(c?) to 1.0.1h it seemed to get worse in that now it won't work at all. FTP software (the company) telnet and rlogin do work fine and since they are from the same obviosly, FTP made theirs more robust but I don't know what they did. It's been a low priority problem around here but if anyone does know why, I'd be delighted to hear about it. (The PCIP stuff works just fine logging into Ultrix on a VAX and Wollongong TCP/IP for VMS.) Cliff
romkey@asylum.SF.CA.US (John Romkey) (10/23/90)
In article <108@embassy.nsi.com> lance@embassy.nsi.com (Lance N.
Antrim) writes about problems using Macintosh NCSA Telnet with SCO TCP 1.0.1
There are problems with how the SCO telnetd deals with certain Telnet
terminal type option negotiations; NCSA Telnet seems to especially
aggravate this problem. I believe SCO is readying a 1.0.2 release of
SCO TCP which I hope will solve this bug. I have no idea when it will
be out, though.
--
- john romkey Epilogue Technology
USENET/UUCP/Internet: romkey@asylum.sf.ca.us FAX: 415 594-1141romkey@asylum.SF.CA.US (John Romkey) (10/24/90)
In article <1990Oct22.214503.2167@cjbsys.bdb.com> cliffb@cjbsys.bdb.com (cliff bedore) writes: >FTP software >(the company) telnet and rlogin do work fine and since they are from the same (as PC/IP) >obviosly, FTP made theirs more robust but I don't know what they did. Actually, FTP's telnet is very different from PC/IP's. The TCP and the telnet are complete reimplementations from the ground up. The telnet handles many more options, and does option processing differently. PC/TCP was based on PC/IP, and the version 1 series of the product did substantially resemble PC/IP, but the version 2 code is very different. -- - john romkey Epilogue Technology USENET/UUCP/Internet: romkey@asylum.sf.ca.us FAX: 415 594-1141