Windows XP x64 Terminal Server Patch part 2 (optional)

In part 1 I’ve showed how to get rid of some terminal server restrictions on Windows xp x64. But there are still some problems:

1) You cannot connect to the localhost (127.0.0.1) (but can to 127.a.b.c, where a,b,c in [0..255] (except 127.0.0.0 and 127.255.255.255)).

When you’re connecting to remote server, Remote Desktop Connection (mstsc.exe) checks through mtscax.dll that you’re connecting to your own address, connections are only allowed and you’re in the server mode. If this is not true, the connection is denied, usually with this message:. The logic of checking is the same: call gethostbyname for server name and check if it’s not equal to 127.0.0.1. So, we can use a very simple patch: find and replace 7F 00 00 01 (127.0.0.1) with, for example, some invalid network address, like FF FF FF FF (255.255.255.255).

It’s working for all known version of mstscax.dll (from 5.1 to Windows 7; version 5.0, which is shipped with Windows 2000 server, doesn’t have this restriction at all).

Mstscax.dll Universal Patch


( Read more )

Windows XP 64 Terminal Server patch part 1 (mandatory)

Windows XP X64 shares the same binaries with Windows 2003 X64, but Terminal Server has some restrictions on XP. This article shows you how to get rid of them and is based on cw2k ideas from the original Windows XP Terminal Server patch.

Version 1.1 contains bug#1 fix and is smaller (less bytes are changed).

( Read more )