Cannot connect to Win NT 4 TS via RDP

[happy dude]

Just incase the title wasn't clear enough, I cannot connect to a Windows NT 4 Terminal Server that I have set up using RDP clients on Win7 or OS X. Don't forget that Terminal Services and RDP are the same thing, just different names

The problem is, when I try to connect over RDP, it fails every time. On Windows 7 using Remote Desktop Connection, I first get an error message that the identity of the remote computer cannot be identified - to be expected. Once I hit yes, I'm quickly greeted with "<i>Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.</i>

On OS X, the RDC client crashes. Using a third party app (cannot remember the name right now), the screen goes black (its connected) but doesn't go any further. No login pop up, nothing.


Suggestions? Its NT4 TS, SP6. If I use the NT4 Terminal Server Client on it, it can RDP into itself. Suggests a compatibility issue, wondering if it can be fixed

[louisw3]

Just incase the title wasn't clear enough, I cannot connect to a Windows NT 4 Terminal Server that I have set up using RDP clients on Win7 or OS X. Don't forget that Terminal Services and RDP are the same thing, just different names

The problem is, when I try to connect over RDP, it fails every time. On Windows 7 using Remote Desktop Connection, I first get an error message that the identity of the remote computer cannot be identified - to be expected. Once I hit yes, I'm quickly greeted with "<i>Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.</i>

On OS X, the RDC client crashes. Using a third party app (cannot remember the name right now), the screen goes black (its connected) but doesn't go any further. No login pop up, nothing.


Suggestions? Its NT4 TS, SP6. If I use the NT4 Terminal Server Client on it, it can RDP into itself. Suggests a compatibility issue, wondering if it can be fixed

On the win32/win64 side, I use the terminal server client from Windows XP SP0, just grab mstsc.exe & mstscax.dll and that is enough to run it..

I don't have a good solution for OS X though.

If you can run PowerPC apps, the old terminal server client will work, but since rosetta is no more, you are out of luck on OS X, I guess you could install NT on OS X in vmware and go that way..

[roytam1]

does rdesktop work?
http://www.rdesktop.org/

[EPPM]

No modern clients support the old NT 4 TS, I use the original client that came with it. The setup is 16 bit but the app itself it's 32 bit so it should run fine on 64 bit versions.

[Chartreuse]

I'd second roytam's suggestion to try the Open Source rdesktop.

If you have X11 installed for OS X it should be fairly trivial to complie it. Its website claims to support NT4 Terminal Server so it should work for you:

rdesktop is known to work with Windows versions such as NT 4 Terminal Server, 2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2.

Another alternative to try would be CoRD which is a native OS X port of rdesktop (it doesn't explicitly claim NT4 TS, but since it's a port of rdesktop it might): http://cord.sourceforge.net/

[louisw3]

sadly cord doesn't work...

[happy dude]

louisw3, EPPM: Ah okay. Guessing it comes down to simply being incompatible with modern clients. And I'm guessing there's no fix for it unless using something completely different like VNC or an old RDP client

roytam1, Chartreuse: CoRD is the other program I used on OS X. It connects but the screen stays black and doesn't go any further

Bit of a shame but its not important. Bothered I can't RDP in from my iPad though