I want to submit a problem that sounds like a bug.
Here's my situation:
The Windows 2000 Server with RDP is behind a Linux firewall with no DNAT
entries. The only way to reach it is to dial in with PPTP.
I tried from a Linux box to dial in (connection is ok, I can ping the
Windows 2000 Server), then run rdesktop with the private address and... The
window rises, the blue screen appears (almost always: sometimes it fails
displaying the background, but the connection is still on and data goes
across the connection when I move the mouse over), but no authentication
dialog. It happened I've reached the authentication dialog just 2 times
over 40-50 tries and anyway after putting username/password the screen has
freezed on the next dialog box. Everytime the connection is still on, and
data goes through when I move the mouse over.
So, I tried with a Windows XP machine. Dialed into with PPTP, and the
remote desktop is perfect.
Next try: I've put a DNAT entry into the firewall that protects the Windows
2000 Server to forward inside the TCP port 3398. I've tried again with
Linux (without issuing a PPTP connection, of course), and this time
everything worked with rdesktop.
So the question is: why? Could it be a timing problem? May be the PPTP
connection is adding an async delay...
So, some other info:
for PPTP I use on the server side pptpd 1.1.2 and on the client side
pptp-linux 1.1.0 with MPPE patch (encryption) on both sides. As
connections, the firewall and the Windows 2000 server are linked via ADSL
640/128. The client is linked with an ISDN 128kbit/s.
Thanks for help.
Nhan NGO DINH
System Administration and Development