Hi vijay,

thank you for posting in windows forums,

can you please tell us the source and destination you are trying to connect

a) operating system

b) network information

c) did this worked before ? , what has recently changed

d) are you able to ping to the destination server

e) are these on same domain or on different domain ?

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

Hi,

Whenever u face such an issue...goto ur domain controller machine. Open up services.msc
here u can check for two services :-

1.Computer browser and
2.Secondary logon.

Somehow these two services might have stopped. Just restart these services n u will be able to login :)

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

Hi,

Whenever u face such an issue...goto ur domain controller machine. Open up services.msc
here u can check for two services :-

1.Computer browser and
2.Secondary logon.

Somehow these two services might have stopped. Just restart these services n u will be able to login :)

Hi,

Whenever u face such an issue...goto ur domain controller machine. Open up services.msc
here u can check for two services :-

1.Computer browser and
2.Secondary logon.

Somehow these two services might have stopped. Just restart these services n u will be able to login :)

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

Hi,

Whenever u face such an issue...goto ur domain controller machine. Open up services.msc
here u can check for two services :-

1.Computer browser and
2.Secondary logon.

Somehow these two services might have stopped. Just restart these services n u will be able to login :)

• Marked as answer by Sainath IRP_MJ_CREATEMVP, Moderator Thursday, August 26, 2010 1:37 AM

Hi Michael,

Try putting this registry key in your regedit

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Create a new kwy selecting Dword and name it as IgnoreRegUserConfigErrors

now double click it and give a value as 1

Now try doing an RDP it should work for you .

It should work for you .

This issue is normally seen in 2003 servers and suggest using my fix only on 2003 servers.

• Proposed as answer by Brendon Cameron Sunday, May 12, 2013 2:55 AM

• Proposed as answer by Brendon Cameron Sunday, May 12, 2013 2:55 AM

• Proposed as answer by Brendon Cameron Sunday, May 12, 2013 2:55 AM

Hi Sam,

what is the error message you get when you try to login with domain account ?

Hi Singhpps

which one worked for you ?

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.

I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to the production environment without a problem.

I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their host server. Again, though, I CAN log into the DC without issue.

Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)

Any other thoughts about potential solutions?

Thanks!

Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains? Still no answer to why this happened in the first place, so I'd appreciate input.

Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much appreciated!

• Edited by Russell Edworthy Saturday, December 17, 2011 2:16 AM

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.

I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to the production environment without a problem.

I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their host server. Again, though, I CAN log into the DC without issue.

Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)

Any other thoughts about potential solutions?

Thanks!

Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains? Still no answer to why this happened in the first place, so I'd appreciate input.

Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much appreciated!

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.

I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to the production environment without a problem.

I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their host server. Again, though, I CAN log into the DC without issue.

Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)

Any other thoughts about potential solutions?

Thanks!

Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains? Still no answer to why this happened in the first place, so I'd appreciate input.

Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much appreciated!

• Edited by Russell Edworthy Saturday, December 17, 2011 2:16 AM

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.

I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to the production environment without a problem.

I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their host server. Again, though, I CAN log into the DC without issue.

Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)

Any other thoughts about potential solutions?

Thanks!

Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains? Still no answer to why this happened in the first place, so I'd appreciate input.

Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much appreciated!

• Edited by Russell Edworthy Saturday, December 17, 2011 2:16 AM

Thanks this worked for us.

(Editing the registry IgnoreRegUserConfigErrors)

• Edited by bobwheaties Wednesday, July 25, 2012 5:41 PM

Thanks this worked for us.

(Editing the registry IgnoreRegUserConfigErrors)

Thanks this worked for us.

(Editing the registry IgnoreRegUserConfigErrors)

• Edited by bobwheaties Wednesday, July 25, 2012 5:41 PM

Thanks this worked for us.

(Editing the registry IgnoreRegUserConfigErrors)

• Edited by bobwheaties Wednesday, July 25, 2012 5:41 PM

Hi Bobwheaties,

Please consider voting and selecting option of Propose As Answer , as this helps others too.

Thanks this worked for us.

(Editing the registry IgnoreRegUserConfigErrors)

Please consider voting and selecting option of Propose As Answer , as this helps other

• Proposed as answer by E.dez Monday, July 21, 2014 6:22 PM

Hi Michael,

Try putting this registry key in your regedit

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Create a new kwy selecting Dword and name it as IgnoreRegUserConfigErrors

now double click it and give a value as 1

Now try doing an RDP it should work for you .

It should work for you .

This issue is normally seen in 2003 servers and suggest using my fix only on 2003 servers.

Date: 7th Sep 2013

The following solution given in the mail thread worked for me:

========

ADD This reg. key on the remote server giving the error:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Create a new kwy selecting Dword and name it as IgnoreRegUserConfigErrors

now double click it and give a value as 1

Now try doing an RDP it should work for you .

It should work for you .

This issue is normally seen in 2003 servers and suggest using my fix only on 2003 servers.

========

• Edited by TVN Vijay Prakash Tuesday, January 07, 2014 5:59 AM

• Edited by TVN Vijay Prakash Tuesday, January 07, 2014 5:59 AM

• Edited by TVN Vijay Prakash Tuesday, January 07, 2014 5:59 AM

Thanks, that did really the trick!!

csilver

This worked Michael

Try putting this registry key in your regedit

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

Create a new kwy selecting Dword and name it as IgnoreRegUserConfigErrors

now double click it and give a value as 1

Now try doing an RDP it should work for you .

It should work for you .

This issue is normally seen in 2003 servers and suggest using my fix only on 2003 servers.

This works for me ~  but i feel this is just a temporary solution

Thanks @Dave07424

The solution given by you worked for me.

Thanks a Lot.

Now we are troubleshooting, why Server is not able to get the Group policies.

- Ashish K