From: Rich D. <ri...@op...> - 2003-05-22 14:59:31
|
On 21 May 2003, Jonathan Kamens wrote: > I'm attempting to use rdesktop 1.2.0 on Linux to connect to terminal > services on Windows 2000 service pack 2. When I connect, a get a > black window for a while and then the window eventually disconnects > when I move my mouse over it after ten or fifteen seconds. We had a similar problem when connecting to a high encryption server. Switching the server to medium solved the problem. I think this was a problem with SP2 or SP3. I can't remember which, so it may or may not apply to you. You can also get a similar error when you've run out of TS licences. > I've never used rdesktop before, so I don't know whether this should > work or how to debug it. > > It may or may not be relevant that I'm doing this over a VPN > connection to a Microsoft VPN server after adding MPPE support to my > kernel and installing ppp and pptp-linux packages that support > Microsoft VPNs. The VPN seems to work just fine, e.g., I can VNC > successfully to another machine on the remote end of the VPN which is > running a VNC server rather than terminal services. > > When I connect to the machine from a Windows remote desktop client, I > see that it is configured for RDP 5.0. I believe that rdesktop > doesn't support RDP 5.0, so perhaps that's the problem; what I don't > know is whether the RDP 5.0 server in Windows 2000 is smart enough to > fall back on 4.0 if the client doesn't support 5.0. > > Unfortunately, the IS people at my company aren't particularly > cooperative about things like helping people work remotely from Linux > machines, so I don't expect them to be any help debugging this. > > I'd appreciate any suggestions anyone can offer on the questions of > (a) whether this should be work and (b) if so, how to debug the fact > that it doesn't. Can you get access to the W2K event log? Are there any messages on stdout/stderr when you run rdesktop? > Thanks, > > Jonathan Kamens - Rich Doughty |