Can't telnet into vxworks from pc client
CF
this.
There is a problem when I try to telnet into the target's telnetd. When I
try, I see the following three things happen:
1. Target: I get the correct output on the target shell
"telnetd: This system *IN USE* via telnet.
Shell restarted"
(ok, this is Good)
2. Host: My windows 2000 console (DOS prompt) screen goes blank, it appears
that the telnet client application shows nothing. (this is bad)
3. Both host and target: I have found the only way to get out of this
situation seems to be to reboot the vxworks target and kill the Windows 2000
telnet client process manually. (hmmmm, this is really bad)
I am wondering if anybody has seen this sort of thing before.
System Details:
Host: Windows 2000. Tornado 2.1.1. Telnetd is included in the project
through the project facility, workspace, Vxworks, network components,
networking protocols, network applications, Telnet Server...
General:
INCLUDE_TELNET
Params:
TELNETD_MAX_CLIENTS: 1
TELNETD_PARSER_HOOK: shellParserControl
TELNETD_PORT: 23
TELNETD_TASKFLAG: 3
(INCLUDE_TELNET and INCLUDE_SHELL are both defined)
Target: System: vxworks 5.4. Xscale processor.
The "i" command shows
NAME , ENTRY, TID, PRI, STATUS, PC, SP, ERRNO, DELAY
tTelentd, _telnetd, a4cfe044, 55, PEND, a0231a84, a4cfdef8, 0, 0
Ethernet sniff of a telnet transaction attempt:
(Target) (Host)
# Destination Source Protocol Summary
Size
1 10.10.3.221 10.10.3.30 Telnet TCP
(SYN) 62
2 Broadcast 10.10.3.221 ARP Request
60
3 10.10.3.221 10.10.3.30 ARP Reply
60
4 10.10.3.30 10.10.3.221 Telnet TCP
(ACK, SYN) 60 (I verified it is attempting to connect to port 23,
correct).
5 10.10.3.221 10.10.3.30 Telnet TCP
(ACK) 60
6 10.10.3.30 10.10.3.221 Telnet TCP
(ACK, PSH) 60
7 10.10.3.221 10.10.3.30 Telnet TCP
(ACK, PSH) 60
8 10.10.3.221 10.10.3.30 Telnet TCP
(ACK, PSH) 60
9 10.10.3.221 10.10.3.30 Telnet TCP
(ACK, PSH) 89
10 10.10.3.221 10.10.3.30 Telnet TCP
(ACK, PSH) 123 (I typed a bunch of chars, they did get sent)
11 10.10.3.221 10.10.3.30 Telnet TCP
(ACK, FIN) 60 (I killed the telnet client here)
Telnet session capture:
C:\WINNT> telnet
Microsoft (R) Windows 2000 (TM) Version 5.00 (Build 2195)
Welcome to Microsoft Telnet Client
Telnet Client Build 5.00.99206.1
Escape Character is 'CTRL+]'
Microsoft Telnet> display
Escape Character is 'CTRL+]'
WILL AUTH (NTLM Authentication)
LOCAL_ECHO off
Sending both CR & LF
WILL TERM TYPE
Preferred Term Type is ANSI
Microsoft Telnet> unset ntlm
Microsoft Telnet> display
Escape Character is 'CTRL+]'
WONT AUTH (NTLM Authentication)
LOCAL_ECHO off
Sending both CR & LF
WILL TERM TYPE
Preferred Term Type is ANSI
Microsoft Telnet> open 10.10.3.221
(at this point the screen goes blank, hitting keys *does* send the
characters to target over TCP but there is never any response from the
target's telenetd server, it seems)
It's probably something simple...
John
I would suggest getting a better telnet client and seeing if that
works - the MS telnet client is perhaps the worst I have ever seen. I
would strongly recommend this one (which is free):
http://www.chiark.greenend.org.uk/~sgtatham/putty/
It also has other stuff like rlogin, SSH, SCP in case you ever need
those for anything.
HTH,
John...
"CF" <ca...@notsoform.com> wrote in message news:<t4f9a.5150$aq6.4...@news3.news.adelphia.net>...
=====
Rate Corporate America at http://exec-ratings.bluedonkey.org
Roger
I tried the PuTTY telent client. It didn't seem to help.
-Carl
D.
client will do as good a job as any other and would not cause a connection
failure; network problems/settings and/or peer's problems would cause a
connection to fail.
"John" <john_...@yahoo.com> wrote in message
news:488e459a.03030...@posting.google.com...
D.
Trying pinging from one to the other and the other way around (if you have
icmp compiled in your kernel), and also try to telnet FROM vxWorks to the
PC, it might give you more info. on what's going on, but I would check the
routing tables first on both sides and make sure they're configured
correctly.
"CF" <ca...@notsoform.com> wrote in message
news:t4f9a.5150$aq6.4...@news3.news.adelphia.net...
msafar
socket?
What do you expect to see? (Have no experience with telnetd, we have
our own)
The sniff suggests that there is nothing reading tha data on the
server side, when you killed your client the FIN was sent (which is
correct, the OS cleaning up after the process), but no FIN from other
side. This could happen, when nobody reads the stream on the server
side and therefore nobody finds out that the tcp connection is about
to be closed (you have to read all available data first).
msafar
You may try to write to the socket on server side, while the
connection is established - telnetfd????
"CF" <ca...@notsoform.com> wrote in message news:<t4f9a.5150$aq6.4...@news3.news.adelphia.net>...
CF
news:kD7aa.14287$0W6.4...@ursa-nb00s0.nbnet.nb.ca...
> It looks like it might be an IP routing problem, check your routing
tables.
> Trying pinging from one to the other and the other way around (if you have
> icmp compiled in your kernel), and also try to telnet FROM vxWorks to the
> PC, it might give you more info. on what's going on, but I would check the
> routing tables first on both sides and make sure they're configured
> correctly.
>
Hi:
Ping works find both ways. No routing table problems as far as I can see.
Lynda
A few months ago I remember having a similar problem with the
VxWorks telnet server (telnetd). My memory is that adding it
to the VxWorks image does *not* automatically include the
target shell. When I went back and added the shell, the problem
was fixed.
Lynda
"CF" <ca...@notsoform.com> wrote in message news:<t4f9a.5150$aq6.4...@news3.news.adelphia.net>...
CF
I checked, and INCLUDE_SHELL is one of the macros included. I'll keep
trying. Thanks for the try.
"Lynda" <lynda...@att.net> wrote in message
news:3644fb5b.03031...@posting.google.com...
John
> > > LOCAL_ECHO off
Try turning this on - I seem to remember when playing with a demo
server we used as an example in VxWorks AE that MS telnet wouldn't
play ball unless the local echo was enabled.
Note to earlier poster who said that telnet clients are all alike:
they are not, and the MS one has a number of differences. My simple
telnet server demo application worked perfectly with all unix clients
we tried, but I had to change several settings in the MS one to make
it work on Windoze.
I didn't try PuTTY at that point partly because I hadn't discovered
it, and partly because the requirement was to work with MS telnet, so
I don't know if it would work out of the box with VxWorks - I do know
that it works much better when connecting to Unix servers than the MS
one, and it supports rsh/rlogin and ssh into the bargain.
Back to the problem... you could also try typing the following to see
what happens:
reboot^J
(where ^J is control key + J)
If the target reboots, then this could be part of the problem too:
> > > Sending both CR & LF
You probably want to send just LF rather than both. VxWorks is
unix-like in this respect, and I'm not sure whether the shell
interpreter will cope with the CR characters at the end of every line;
if I had to guess, I'd say it wouldn't.
> > > WILL TERM TYPE
This might also be a good thing to disable as I don't expect the
VxWorks end will respond to it - might be wrong on that, and I don't
have a target any more I can try it with. If you can disable the
automatic term type determination, and just force it to a vt100 like
setting, that'll probably be the safest option.
> > > It's probably something simple...
Have you checked the status of the network connection? You can use
netstat on Windoze from a command prompt to see the active connections
on that end, and if you add the network show routines to VxWorks,
inetstatShow will give a similar thing there (you'll need to use a
WindSh session of course ;-)
HTH,
John...
Randy Ryan
trying to get to it via a router from from another subnet on the VPN,
vxWorks claims I'm getting a connection (ipstatShow), but the client just
times out. Netmask for the interface is the standard 255.255.255.0 setting.
I know (or think I know...) the router works ok, as routing to my
development host with Telnet server enabled works fine.
I don't have access to a remote machine with tcpdump...
Randy Ryan
NovaSol, http://www.nova-sol.com
John
> I know (or think I know...) the router works ok, as routing to my
> development host with Telnet server enabled works fine.
>
> I don't have access to a remote machine with tcpdump...
Do you have a default route set on the target system? If not, try
setting one with routeAdd "0", "Gateway IP address" (you can add this
to the end of the init sequence on the target so that it will always
be there when you boot the target).
Bep Verberk
>I am able to telnet into VxWorks from my internal network fine.
> But in trying to get to it via a router from from another subnet
> on the VPN, vxWorks claims I'm getting a connection (ipstatShow),
> but the client just times out.
> Netmask for the interface is the standard 255.255.255.0 setting.
> I know (or think I know...) the router works ok, as routing to my
> development host with Telnet server enabled works fine.
Randy,
your vxworks machine probably does not have a route set up to respond back
to
you through the router.
Off hand I forget how to add one, its addroute() or some such thing..
Bep
Randy Ryan
why this works, but essentially have to delete the default route settings,
then mRouteAdd to the router, and then the "0" routeAdd to the router.
routeDelete("192.168.0.0","192.168.0.150")
mRouteAdd("192.168.0.1","192.168.0.150",0xffffff00,0,0)
routeAdd ("0","192.168.0.1")
Thanks for steering me to the right path.
Randy Ryan
NovaSol, http://www.nova-sol.com
> your vxworks machine probably does not have a route set up to respond back