regular telnet fails on XP?

[Alan Bergim]

I have a question related to VLC and telnet.

Under Windows XP, in a DOS window, I did the 3 following commands:

> vlc --ttl 12 -vvv --color -I telnet --telnet-password admin --rtsp-host 127.0.0.1:5554
> netstat -an
Connexions actives
Proto Adresse locale Adresse distante Etat
TCP 0.0.0.0:4212 0.0.0.0:0 LISTENING
> telnet 127.0.0.1:4212
password:
Connection closed by remote host (a.k.a. in french "perte de la connexion à l'hôte")

The regular telnet with cmd.exe fails just after displaying "password:" without giving time to enter the password.
A regular telnet with the Putty tool also fails similarly.
When I try the telnet with a tool like "Socket Workbench", the telnet works fine.
The question is: what is the reason the regular telnet can not be used?

Thanks,
Alan

[tonsofpcs]

For telnet on a command line, the syntax is

Code: Select all

telnet host [port]

, not

Code: Select all

telnet host[:port]

.

[Xanatos]

I have exactly the same Problem.
It's definitely no typo in the telnet call. You wouldn't ge the password promt and the message "Connection closed by remote host" but rather something like "connection refused"

The funny thing is everything works fine if I start the telnet interface out of the VLC player window, or if I configure it to start as extended interface.

However if I try to start the VLC with a specific config file with the "--vlm-conf" command line option it won't work either. The config file seems to be ignored and the VLC is started with its settings as stored in the Application Data of the user.

[dionoea]

This is a known problem with no known solution. Use another program like putty to get it to work correctly.

[ftoomsh]

PuTTy ends the same,
for an elegant solution specify also:
--control=telnet

This would be much like setting permission to allow control by a particular interface, whereas otherwise VLC would reject requests by telnet.

Now we have pure command line bliss.

From "vlc-help.txt"
--control=<string> Control interfaces
You can select control interfaces for VLC.

[fpostma]

Oh? I use "vlc -I dummy --dummy-quiet --extraintf telnet" to get it to work, would using '--control=telnet' be better?

It's not just xp telnet that fails btw. Any telnet fails, not letting you specify a password at all but disconnecting immediatly after 'Password:'.

Curious since on linux the '-I telnet' syntax works exactly as you would expect.

[sonix]

Hello,

I have the same problem.
I am trying to build a wrapper app in Delphi to control VLC.
In my opinion the problem resides in the telnet commands formatting for the EOL and LF through windows sockets.
I'm still working on this and hopefully I'll find a solution (I'll post it here).

Actually after "Password:" I get "ÿû" chars and I believe that those are causing the windows socket to throw "ERROR: 10053" (Software caused connection abort).
A temporary workaround for this would be to set your putty terminal to use "RAW" rather than "telnet" for connection type. this way you will be able to control VLC.

Regards,
SoniX
http://blog.coding.ro

[leland]

I have encounter the same problem.
When I use
"vlc.exe -I telnet"
to start a vlc process, i can't telnet to the default 4212 port as the connection lost problem occurs.

But when is use telnet as an extra-interface, it's work correctly.
"vlc.exe --extraintf telnet"

Also I can raise the telnet control interface in the "setting" field.

I guess there must be a bug in starting vlc only use telnet control in windows. Under my Ubuntu, use telnet to control vlc is working correctly.

[leland]

I update to 0.9.8a today, then I found that when use telnet as an extra-interface, telnet won't work correctly...

[VLC_help]

There was fix applied to VLC 1.0.0 that hopefully makes telnet work again in Win32.

[Chachi]

As of March 05, 2009 the latest release of VLC is 0.9.8a.

Windows built-in telnet client fails to connect to the VLC telnet server. The windows telnet client closes the connection at the password prompt.

However, the PuTTY telnet client works perfectly....ONLY if the PuTTY connection type is set to RAW!

To do this, run PuTTY. You should see the PuTTY Configuration window. In the settings tree, choose Session. In the window pane on the right side, under "Basic options for your PuTTY session", under host name....there are radio buttons for Connection Type. Choose Raw. Fill in the host IP and port. Click Open button.

Hope this helps....