Telnet into a Windows XP box
chill
Posts: 186
I have a piece of gear to control via telnet. It's a Vista X20 Spyder, but it's really Windows XP Embedded underneath. I need to be able to telnet into it from my NI-4100. I've set up the Spyder to allow this.
The issue is that when I telnet from Netlinx, it sends a string of hex gibberish. The specific string I get back is "$FF$FD%$FF$FB$01$FF$FB$03$FF$FD'$FF$FD$1F$FF$FD. I get the expected behavior (prompt for username and password) from three different telnet clients on my laptop, and I've gotten the bad behavior on two different Windows 'server' boxes when connecting from Netlinx. AMX tech support was able to reproduce the bad behavior, even to the point of getting that same string of hex back from the server on connection. They've put in an RFI, but we know where that will lead.
Any ideas?
Thanks!
.
The issue is that when I telnet from Netlinx, it sends a string of hex gibberish. The specific string I get back is "$FF$FD%$FF$FB$01$FF$FB$03$FF$FD'$FF$FD$1F$FF$FD. I get the expected behavior (prompt for username and password) from three different telnet clients on my laptop, and I've gotten the bad behavior on two different Windows 'server' boxes when connecting from Netlinx. AMX tech support was able to reproduce the bad behavior, even to the point of getting that same string of hex back from the server on connection. They've put in an RFI, but we know where that will lead.
Any ideas?
Thanks!
.
0
Comments
Telnet isn't what most use it as - that being a raw client. Telnet does have some commands but a telnet client is supposed to understand them.
What client(s) are you using to connect?
Without problems: TeraTerm, Hyperterm, Windows telnet from the prompt. With problems: Netlinx ip_client_open, which has worked for me for many years for everything else.
I didn't really expect that sequence from the daemon, because such things don't appear when telnetting to, e.g., an Accordent capture station (another Windows-based appliance), or an Extron switch, or a Biamp, or a Polycom codec, all of which I've controlled via IP from Netlinx in the past.
Thanks for the reply, and for the hint; I'll see what Mister Google has to say about this.
.
Search for RFC854... Goes into the Telnet protocol.
This is what I normally do to config a telnet client from a server perspective.
This is not a "bad" response. The server is negotiating the telnet options. See http://www.networksorcery.com/enp/protocol/telnet.htm for an explanation of telnet options.
I believe this is saying:
$FF$FD% = IAC DO Authentication
$FF$FB$01 = IAC WILL Echo
$FF$FB$03 = IAC WILL Suppress-go-ahead
$FF$FD' = IAC DO New Environment Option
$FF$FD$1F = IAC DO Negotiate About Window Size
and not sure about the last since you only seem to have $FF$FD.
Thanks again!
.
and the applicable parts in my rx string function:
Hopefully the info others gave you fills you in on what TELNET is and why, while many of us use TELNET clients as raw character clients, a TELNET connection is different from just a raw data / character connection. You are not actually 'telnetting' into your other servers (Biamp, Extron, etc), just using a TELNET client to swap characters and such around as there is no TELNET negotiation.