From: <Pet...@ha...> - 2003-03-11 11:06:48
|
Hi Darryn, to make it clear: the Metaframe server still does support the RDP = protocol, as it is running on top of Windows2000 Server with Terminal Services in Application Mode. We set a restriction to who can connect using an RDP Client (namely to Admin users), but this should make no difference for rdesktop, hopefully.=20 The reason why we want and need to connect to this server is: the ICA client is not working, suffers probably from the same problem. One common step in troubleshooting ICA connectivity is to check that = RDP connectivity is working, so I have to use an RDP client, therefore we = try to connect to this server using rdesktop. When we connect to the "unavailable" server (with rdesktop compiled --with-debug, latest source from cvs, updated this morning), we see: freyp@linux:~> rdesktop -g 1024x768 -k de -f <ip_bad_server> server bpp 8 client bpp 16 depth 16 40-bit encryption enabled Sending encrypted packet: 0000 00 00 00 00 33 00 00 00 00 00 0a 00 00 00 00 00 ....3........... 0010 00 00 00 00 66 00 72 00 65 00 79 00 70 00 00 00 ....f.r.e.y.p... 0020 00 00 00 00 00 00 ...... Connection successful. ERROR: recv: Connection reset by peer Disconnecting... the same thing, with the same client but an other "good" server should = be: freyp@linux:~> rdesktop -g 1024x768 -k de -f <ip_good_server) server bpp 8 client bpp 16 depth 16 40-bit encryption enabled Sending encrypted packet: 0000 00 00 00 00 33 00 00 00 00 00 0a 00 00 00 00 00 ....3........... 0010 00 00 00 00 66 00 72 00 65 00 79 00 70 00 00 00 ....f.r.e.y.p... 0020 00 00 00 00 00 00 ...... Connection successful. RDP packet #1, (type 1): 0000 24 01 11 00 ea 03 ea 03 01 00 04 00 0e 01 52 44 $.............RD 0010 50 00 09 00 00 00 09 00 08 00 ea 03 af e4 01 00 P............... 0020 18 00 01 00 03 00 00 02 00 00 00 00 11 04 00 00 ................ ... (hopefully the first, partially shown RDP packet does not contain = passwords) What we wonder is: we get first the message "Connection successful." But just after that a "Connection reset". Could anybody give me a hint how to troubleshoot this problem? As to the SP3 issue:=20 both terminal servers are SP3, and they are very similar configured, security on RDP is set to medium on both servers. The rdesktop did not get a pre SP3 client license issued as the Linux machine does not yet exist long enough (I set it up last week). Peter -----Urspr=FCngliche Nachricht----- Von: Darryn Capes-Davis [mailto:dca...@cm...]=20 Gesendet: Dienstag, 11. M=E4rz 2003 08:24 An: 'Pet...@ha...'; Darryn Capes-Davis Cc: rde...@li...; rde...@li... Betreff: RE: [rdesktop-users] Strange problem with rdesktop that = previousl y worked... Peter, Not knowing any details I would say that your problem is with Metaframe = and the way it integrates with licencing in W2K terminal server. Check out = for Metaframe updates, espcially with regards to W2K SP3. The licence code in rdesktop was finalised before 1.2 but is only = active at the moment with SAVE_LICENCE defined. I think there is a push to make = it default in the next release. Not sure there. Developers? The save spot is in the dir '.rdesktop'. The licence save file is 'licence.<clientname>'. Your current plain terminal servers may be working for now as any = client connected before SP3 applied will keep a non expiring licence. But you = will run into trouble with new clients or if you change the name of your = clients. Check out the KB article I mentioned and then review your licences on = the server. It is good to be sure how your licences are being handled at = the moment so you don't get caught out with this problem at the wrong time. Cheers Darryn |