Telnet server prob. 1

[Noip]

Hi guyz,

I was having difficulties telneting my win2k server from my linux box with NTLM error message. After setting NTLM to 0 on my server, I was then able to see the welcome message on my linux box. But after that the login prompts me to enter the user name, the characters that I type on my keyboard does not appear on the screen. I have to press enter and the characters that I have just previously typed appears and nothing could be done after.

Am using Redhat 7.3

 

[fluid11]

Are you telnetting to Linux from Windows, or to Windows from Linux?

 

[fluid11]

If your going from Windows to Linux, do this. Open a command prompt window on the Windows machine and type 'telnet'. Then type "set local_echo on" so that you can see your keystrokes in a telnet session.


ChrisP

 

[Noip]

Sorry...

I'm telneting the 2kserver from my linux box. And the error message appears only on the Linux box

 

[krale]

Why would you want to telnet to a Windows NT 5.0 machine? There's not much you can do there... Terminal Server would seem to be mach a wiser choice when dealing with Windows boxen. Or at least VNC if you dont have Win2k Server.

 

[Noip]

Can I install Term. Server on the linux box?????

By the way, what is VNC...

 

[krale]

There isn't any "Remote Desktop" servers for Linux (as in the windows protocol). There is the Client for Linux called RDesktop. I can't remember where I got it, but just search google.

As for VNC, It's a Remote Desktop connection for ANY OS. There's even a client for Java (so you can control Windows from a browser ;-) AT&T made it, so here's the site:

http://www.uk.research.att.com/vnc/

Below's an image of it working under Unix to a Windows computer.

 

[krale]

Also, I found a good link to RDesktop, along with a basic command list.

http://www.sunbelt-software.com/stu/rdesktop.htm

Hope you enjoy VNC and RDesktop.


All the best, Krale

 

[krale]

I should explain what each are...

VNC uses a bitmap transfer to display the desktop. Usually, it transfers only the window you have focus on, but can be told to redraw the screen x times a second. On a dialup, the nearly only way to use this is by using 8 bit color at 640x480 with window focus transfer only. The higher you go, the much less performance you get. This protocol is the least efficent of all three, and will have the least response of them.

Windows Remote Desktop is a much faster protocol in that it transfers API (like giving coords of boxes, instead of sending pictures like VNC). It does have sufficent performance increases than all three on the same media. This on a 100 Mbit lan is almost indistuinguishable from the real computer you're setting at. It also maps the remote computer's drives locally, along with transferring sound. Windows to Windows, it's fairly impressive.

The third choice is if you're using a Unix/Linux network. You could use X to connect to each other's server. YOu'd have to use XDM to set up the connections, but you'd be able to log into any amount of machines that had XDMCP OK'ed for remote connectons and that put out broadcasts. This also uses a API commandset, so it's faster than VNC. However, you'd have to make scripts that auto-mount remote home directories to the local computer. It may be a longshot, but I believe aRts (in kde packages) can send sound input and output to a client. Like everything else, just takes a lil' scripting.

 

[Noip]

Thanks Krale you solved my problem, but I can't digest the fact that I can't telnet my win2k. I would really like to do it just for knowledge. It could help in the future for all the viewers of this topic and myself....


thanx again....

 

[krale]

I've never tried setting up a Win2k telnet server, as what is there to do in console on WinAnything? MMC is is about the most helpful set of tools when it comes to remote anything on Win setups. Course, MMC is a windows tool that mounts the ADMIN$ shard to allow control over the computer.

Still, I dont have Telnetd on my servers anyways. I use SSHD and SFP for control/file_transfer protocols. I also use SSH X connection redirecting over my school network. I'd rather not have people hijacking my window sessiosn.

One neat thing about VNC and Remote Desktop is that VNC, by default uses 1 desktop per 1 user. VNC on Windows makes 1 desktop for all users. Remote desktop makes 1 desktop per 1 user, but Linux RDesktop'l get past the license request ;-)

Still.. I think there's something fishy about WinTelnetd not working. Then again, do you really NEED it working (with MMC and all)?

All the best, Krale