Question
-
0Sign in to vote
Hello !
TheRemote Desktop on my VISTA 32machine was connection to my 2008 64 bit PDC via Remote Desktop ever since installed and configured in the Firwall correctly, it recently started to fail.
I first thought there might be a time difference between my PDC and the Workstation, but it is not.
Can anybody tell me how to configure things to get connection again?
Please reply to ...
Regards, Clemens
Thursday, October 2, 2008 10:53 AM -
0Sign in to vote
Hi Clemens, on the server computer, have you tried this setting:
1. Click start, type sysdm.cpl in start search, and press Enter.
2. Under Remote tab, choose "Allow connections from computers running any versions of Remote Desktop"
3. Click OK.
4. Then, please try again.
Meanwhile, can you connect to other computers via RDP?
Monday, October 6, 2008 6:21 AMModerator -
0Sign in to vote
Hi!
Just returned from Boston, MAto Europe ... Thanks for the answer meanwhile.
The computer is a PDC, so the 'Allow Connections from Computers running any version of Remote Desktop' isnot selectable.
Yes, I can connect to other Servers using RDP without problems. As I say'd the problem occurs suddenly, it did work before.
Regards, Clemens
Saturday, October 11, 2008 10:32 AMModerator -
0Sign in to vote
Hello!
I just did another verification. Settings on PDC and Workstation are identical. Time settings and Regional Settings. I do fear that there is something wrong with the Certification Administration but I see no way to find out how to verify the current status. However the whole story is strange.
Connecting the the PDC using Remotely Anywhere over https works fine. Does RA not use the same certification methods?
ClemensTuesday, October 14, 2008 7:13 AM -
0Sign in to voteI am having the same issue as everyone else. I've confirmed that both domain controllers and the client machine all have the EXACT same time, but I still can't login. There must be another way to fix this.Thursday, October 23, 2008 8:41 PM
-
0Sign in to voteThis worked for me. The problem was that the BIOS battery is dead so when the machine was created it had a date of October 22, 2002 so the certificate was set to expire in 2004. When the date was properly set to June 2009 the certificate was expired.Thursday, June 18, 2009 1:05 AM
-
0Sign in to voteHello Tamer
Tried yoursuggestionnr 2 and it solved my problem.
ThanksFriday, February 5, 2010 2:24 PM -
0Sign in to vote
Thanks Dear
it was highly helpful God Bless You
Tuesday, September 4, 2012 2:41 PMChủ Đề