By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,926 Members | 1,806 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,926 IT Pros & Developers. It's quick & easy.

Create web based custom telnet client to communicate with remote destinations

P: n/a

i need to do telnet via a web server please give me a idia to initiate
the project following requirements are needed

1 Create web based custom telnet client to communicate with remote
destinations.
must provide login security before make communication
2 telnet communication should not be a direct 1 to 1 communication and
that must be as follows
Web telnet client - Web server (telnet client) - destination (see
figure 01)

3 Actual telnet client (dos prompt or other telnet client) must be
residing on the web server.
The responses should show on the web client.
4 Continues communication will be implemented until web client stops.
Standard GUI with good look and feel will be better for web client.
Secure communication will be required.

May 31 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
For the most simple commands you might be able to get this work but I can
ssure you that you will not get this to work with say a curses interface
over telnet (without leaving regular browser operations) think about an
interface like vi whic selectively updates the screen .. even going through
webservices in ajax would force your broswer interface to crawl..

If you are just doing send command-> receive data, that should be pretty
straight forward (i.e. ls<enter>then receive data for ls). Unfortunately you
do not generally do this in a telnet connection (generally you have local
echo turned off and the server handles char by char your data input (for
instance in many unix prompts when you hit <tab> it will try populating
filenames as you type (etc) , which would be next to impossible (unless you
wanted to do something like host a winform control in the browser which then
telneted to a relay server on your webserver)) but even a design like this
is full of holes.

Perhaps a bit more information on what you are trying to accomplish? Is it
only a very small cross section of the telnet spec?

Cheers,

Greg Young
MVP - C#
<th**********@gmail.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...

i need to do telnet via a web server please give me a idia to initiate
the project following requirements are needed

1 Create web based custom telnet client to communicate with remote
destinations.
must provide login security before make communication
2 telnet communication should not be a direct 1 to 1 communication and
that must be as follows
Web telnet client - Web server (telnet client) - destination (see
figure 01)

3 Actual telnet client (dos prompt or other telnet client) must be
residing on the web server.
The responses should show on the web client.
4 Continues communication will be implemented until web client stops.
Standard GUI with good look and feel will be better for web client.
Secure communication will be required.
May 31 '06 #2

P: n/a
Dear sir
thanks for idia that you have given can you help me to design the case
diagrams for building c# telnet librarry i'm looking forword to hearing
from you

regards thilan
th**********@gmail.com wrote:
i need to do telnet via a web server please give me a idia to initiate
the project following requirements are needed

1 Create web based custom telnet client to communicate with remote
destinations.
must provide login security before make communication
2 telnet communication should not be a direct 1 to 1 communication and
that must be as follows
Web telnet client - Web server (telnet client) - destination (see
figure 01)

3 Actual telnet client (dos prompt or other telnet client) must be
residing on the web server.
The responses should show on the web client.
4 Continues communication will be implemented until web client stops.
Standard GUI with good look and feel will be better for web client.
Secure communication will be required.


Jun 3 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.