Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxd.cso.uiuc.edu!uxe.cso.uiuc.edu!melanie
From: melanie@uxe.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: RT's and TCP.  HELP!!! (long-ish :-
Message-ID: <221600003@uxe.cso.uiuc.edu>
Date: 21 Mar 89 18:28:00 GMT
References: <8949@netnews.upenn.edu>
Lines: 32
Nf-ID: #R:netnews.upenn.edu:8949:uxe.cso.uiuc.edu:221600003:000:1673
Nf-From: uxe.cso.uiuc.edu!melanie    Mar 21 12:28:00 1989


um, in reference to your first problem, you do have the correct
netmask entered in /etc/net? if youre a class b network but youre
subnetting, your netmask should be 255.255.255.0 or 0xffffff00

>2) With TCP/IP v. 2.2 I could do use dotted decimal format, i.e.
>   telnet 128.91.11.1, but not nameserving, i.e. telnet wharton.  Now with
>   this "updated" version, names work and (get this)  numbers don't!  What
>   I would like to do is use remote nameserver on our site, only resorting
>   to a local file if there is no entry upstream.  Can I do this?

dotted decmial works on my rt, but i am not a slave nameserver, just 
a lowly client. all i have is a resolv.conf file that lists a
couple of nameservers.

>3) Finally, even when things work and I can telnet to remote hosts, full
>   screen stuff (like editors, etc.) doesn't work.  Is this due to not
>   running X-windows?  I mean, the stuff works, but the keys are all
>   screwed up and don't behave properly even though the thing is supposed 
>   to be emulating a VT100.  Is keyboard remapping the answer?  Can I do
>   that?

no, the vt100 emulator in ibm aix telnet is hopelessly wrong. everyone i know 
running aix has this same problem. my local ibm software person even
admitted it was a basically bad implementation. your best bet is to find 
someone who has typed in a termcap entry for the 5151. (dont look at me!)
the good news is, their 3270 emulator is great.

>p.s. When we got this working at first (ver. 2.1) it took me and *two* 
>IBM tech refs *and* a very knowledgeable friend over three days to get
>it working.  And this update is a nightmare.  I say again, it shouldn't 
>be *this* hard!!!