Re: Telnet command question

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Tue, 15 Jan 2008 16:43:52 -0800

Message-ID:

<#hZsqi9VIHA.4712@TK2MSFTNGP04.phx.gbl>

That's still UTF-16 if UNICODE is defined for your project.
What you need is to get narrow strings, possibly by means of
WideCharToMultiByte (using UTF-8 encoding perhaps).

Using Ethereal you can record the session and see where
things begin to go wrong.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Vinoj" <Vinoj@discussions.microsoft.com> wrote in message
news:4A390860-CCB7-4F92-83B0-80040CAA6C4E@microsoft.com...

I'm casting CStrings as (LPCTSTR) and sending them. The part that I don't
get is that if I step through it, it "understands" all the commands. It's
only when it happens at normal speed, the remote end loses it. The remote
end is hardware and works fine if I use Hyperterminal.

"Ben Voigt [C++ MVP]" wrote:

"Vinoj" <Vinoj@discussions.microsoft.com> wrote in message
news:F1813B9A-2B7D-49A7-A724-898AB10F71B3@microsoft.com...

I'm using async sockets, and overriding the OnReceive, but it doesn't
receive
anything. I also tried introducing sleep timers, but that didn't help
it
either. Do you have to send it character by character? I'm sending
the
entire command as a string.

You should be sending byte arrays, not strings, over sockets. You need
the
right encoding as well. See Encoding.XYZ.GetBytes(string),
Encoding.XYZ.GetString(byte[])

I would venture a guess you may be sending unicode and the interspersed
NUL
characters are confusing the other node.

"William DePalo [MVP VC++]" wrote:

"Vinoj" <Vinoj@discussions.microsoft.com> wrote in message
news:C8834D44-FCC7-4B45-B372-24736F76AA5A@microsoft.com...

I'm writing a software app to connect to a Telnet server. I can get
past
all
the negotiations, but when the commands are sent, it does not
process
them
properly. It seems to only echo back the first character of the
command.
If
I am in debug mode and step through the commands, they work fine.
Ideas?
Thanks in advance...

On the basis of limited information it sounds like a timing problem.
In
debug mode you run slowly enough for there to be characters available
to
read, but in release mode you may be trying to receive before the
other
side
is in a position to send.

Of course, that's a guess and I could be wrong.

Regards,
Will