telnet from win98 to win2k?

I tried to telnet from win98 to win2k pro. The error message was "Server allows NTLM authentication only ". win98 has telnet.exe and fictional Deamon( a telnet server ), win2k has telent.exe and tlntsvr.exe( as a service).

Telnet from win2k to win98 worked fine.

 

Take a look at How to Enable NTLM 2 Authentication for Windows 95/98/2000/NT [Q239869]

 

re: ntlm 2

The doc suggested to edit the lsa key of the registry of win9x:

......
Value Name: LMCompatibility
Data Type: REG_DWORD
Value: 3
Valid Range: 0,3
Description: This parameter specifies the mode of authentication and session security to be used for network logons. It does not affect interactive logons.
.....

It appeares strange, but I couldn't find those values anywhere in the edit tab of regedit.

 

You need a telnet client that supports NTLM authentication. Better to install a ssh daemon on Win2k and a ssh client on Win98.

It is possible to change Win2k's telnet server authentication method if on a secure LAN using Q233069 . You have to stop/start the telnet service after making changes.

 

re: telnet in win98

1. win98 telnet supports ntlm, but not ntlm 2 which is the form the win2k's tlntsvr.exe supports. So win98's tenet has problem when connecting to winNT's servers.

2. the method in the doc above is do enable ntlm 2. But as I explained, it has problem...

3. I had tried absolute telnet and putty, both are telnet/ssh and both asked for ntlm auth. So the problem probably resides in the form of ntlm of win2k.

4. I would think that most window servers use built in telnet server(tlntsvr), so updating the ntlm in win98 is the only solution. Because I want to connect to other people's servers.

 

telnet???

Bluesky, I would Strongly urge you not to use telnet. It is incredibly unsecure. stick with Unixfan's suggustion and find an ssh client.

If you are wanting to log into other 2k boxes, convince them to use ssh. If you use telnet, it will be transmitting your username/password in plain text.

-Brad

 

I dunno. Sorta assumed he was on a small, secure LAN. If not, ssh daemon's got some gaping security holes in it as well.

Bluesky - I guess the best question at this point is one that I should have asked up front. What are you wanting to do? There are probably some much better tools available for PC-PC connections. Also, are you happy with the security of your LAN so those issues won't need to be considered.