sparkie@picard.cs.wisc.edu (Mark Horn) (06/21/91)
Hello, I've been trying to telnet from my IBM PS/2 running DOS3.3 with NCSA TN3270 and the Clarkson Packet Drivers to my '030 NeXT running NS2.0. I remember a few months ago that this topic came up, but must have missed the resolution. I try telneting to the NeXT and it looks like I've established a connection, but the login prompt never comes up. It just sits there. When I do an Alt-M in NCSA to get the diagnostic messages that NCSA gives, I get: --begin Host machine not in configuration file Domain looking for uhura.cs.wisc.edu Querying the DOMAIN name server DOMAIN lookup OK for: uhura.cs.wisc.edu Trying to open TCP connection to: uhura.cs.wisc.edu DO Option TERMINAL TYPE (WILL) DO Option TSPEED (WONT) DO Option Unknown Option (WONT) DO Option Unknown Option (WONT) --end It looks like the NeXT is giving out two options that NCSA doesn't know about. The strange thing, is that I don't experience this problem when telneting to ANY other machine. I can go to DECstations, HP Bobcats, IBM RT's & IBM Mainframes. It seems to just be the NeXT that I can't talk to. Has anyone run across a fix to this problem? How about those unknown options - anyone know 'em? Thanks for any help, - sparkie -- sparkie@uhura.cs.wisc.edu (Mark Horn) NeXT Campus Consultant @ U. of Wisconsin, Madison
eps@toaster.SFSU.EDU (Eric P. Scott) (06/22/91)
In article <1991Jun21.161121.3163@daffy.cs.wisc.edu> sparkie@uhura.cs.wisc.edu writes: >I've been trying to telnet from my IBM PS/2 running DOS3.3 with NCSA TN3270 You don't mention which version of TN3270 you have, but odds are it's something ancient--some old/obsolete/buggy versions won't talk to the NeXT. The reason you don't see the problem with other machines is because they're running ancient software too! In any case, if you pick up the CURRENT versions of the NCSA or Clarkson software, you should have no problem. (Note the the problems only cropped up in the PC versions of these programs.) -=EPS=-