You are not logged in.
Pages: 1
Hello guys,
My jobs requires me to deal with Windows Servers sometime, I have been using rdesktop to remotely access to Windows machines (including Windows XP, Windows Server 2003) without any problems. However, lately when there's a Windows Server 2008 R2 installed and I need to do remote access to that server. rdesktop doesn't seem to work well with Windows 2k8, the first try always works flawlessly, then whether I logged off or just closed the remote window, then the second time onwards, I always get "internal licensing error" message.
But the problem is, if I use another linux PC (I have several linux OS running in virtual and physical machines, like Mint, Arch, Slackware, even PC-BSD) that I have never "rdesktop" to that Win2k8 before, then the first try always works and problem continues from the second try.
This problem doesn't seem to happen while I borrow a Windows machine and test many times. So I think there's something that "rdesktop" just doesn't like about Win2k8
Has anyone experienced this before and do you know a solution for this?
Thank you very much in advance
Last edited by Himari (2010-08-05 13:56:36)
Offline
Well, the only difference that I notice is that when accessing Win2k8 remotely, it pops up a message saying something about certificate and ask do you want to trust/process anyway, whilst with rdesktop, it never asks me that kind of question. So I presume after the first time successful login, it fails from the second time onwards.
However, is there a solution to overcome this problem?
Thanks
Offline
I'd say that you should rm the rdesktop dotfiles for every time you run it. I'm not sure where rdesktop stores it configs, but its somewhere in /home
Those who give up their liberty for security,
neither deserve liberty nor freedom,
and they will lose both.
- Benjamin Franklin
Offline
Run "rm -rf ~/.rdesktop" before or after every rdesktop session, this is a known problem (Sorry, too lazy to look up my references atm).
Offline
Thank you very much for your answers
Offline
You can also remove the ~/.rdesktop folder and then touch ~/.rdesktop so it creates a file. Rdesktop will complain that .rdesktop is a file and not a folder, but runs flawless.
Offline
Pages: 1