stebbins@spahn.ucr.edu (john stebbins) (07/22/90)
I just installed WIN/TCP 5.1 and am having a problem getting to one
particular node on the inet. I've tried several other nodes and have
been successful on all of them. Here's the particulars. Our node accesses
the outside world through a gateway. I have run route:
route add default <gateway> 1
That seems to get me everywhere but where I want to go. I'm trying to
reach ucrmath.ucr.edu (192.31.146.1). It uses a gateway at ucsd.edu
(128.54.16.1). What I get when I try to telnet in is:
Connected to 192.31.146.1
escape sequence is ^]
Then no login prompt. It just sits there until my end times out.
I believe that the ucrmath end of things is functioning properly
because other people I know say that they have had no problem using
it. If it is a routing problem, the next question is, is there
some list of routes available somewhere so that I can do this once
and be done with it forever? Is there some other piece of software
I should be running that takes care of this problem for me?
The extent of my knowledge is only what I've been able to cram into
my head in the last 3 days, so assume I'm a novice and explain things
carefully if you respond to this. Thanks in advance.
John Stebbins
stebbins@ucrmath.ucr.edu (school)
stebbins@137.67.5.1 (work {this is where I am most of the time})mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett) (07/22/90)
John: It appears that the Sun system (ucrmath.ucr.edu) requires you to provide a <CR> or two before it provides the login in prompt. At least its required when connecting from a 4.3BSD system. Merton
stebbins@gibson.ucr.edu (john stebbins) (07/23/90)
In article <9007221321.AA06463@WLV.IMSD.CONTEL.COM>, mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett) writes: |> John: |> |> It appears that the Sun system (ucrmath.ucr.edu) requires you to provide a |> <CR> or two before it provides the login in prompt. At least its required |> when connecting from a 4.3BSD system. |> |> Merton I tried the above and still got no response. I did try this before, but I thought I'd recheck since someone else thought of it too. Thanks for the effort. John stebbins stebbins@ucrmath.ucr.edu (school) stebbins@137.67.5.1 (work)
rbn@umd5.umd.edu (Ron Natalie) (07/23/90)
This is probably one of those implementations that insists on looking up you IP address and resolving it to a name before going any farther. You're new machine probably is not in the IN-ADDR domain tree or the servers are placed such that the name is not easily resolvable. It just wastes time trying to figure it out. -Ron
MURAKAMI@NTT-20.NTT.JP (ken-ichiro murakami) (07/24/90)
John, TELNET negotiation failure may cause such problem. If your TELNET client(WIN?) has TELNET negotiation debug option, you could see what's going on. Hope this helps. -Ken Ken-ichiro Murakami NTT Laboratories Tokyo, Japan -------