Hi Brothers ,I have a big problem , I have a HP Server Model ML570 , it is running Windows Server 2003 , I'm a member of Domain Admin Group Also I'm a member of Administrators group , this server is a domain controller , Suddenlly I'm not able to connect to the server via RDP also some of my friends on who share with me in the same groups can't logon to the server via RDP .Can any body explain what is happening !!!!???Thanks in Advance .

Hello Mohammed, Its bit hard to guess and tell you the root cause of the problem, will you please let us know the exact error message.I am posting some of the most common troubleshoots.Please see the following link http://technet.microsoft.com/en-us/library/cc780927.aspx Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. Cause:Data encryption provides security for data traveling over network connections. A data encryption error can end a session for security reasons. Solution:Try connecting to the remote computer again. Encryption policies can vary between systems and domains. If you continue to see this error message, contact the server administrator. The remote connection has timed out. Please try connecting to the remote computer again. Cause:The terminal server disconnected your session because you did not send a response within the time limit set for responses. Solution:Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator. Cause:A slow network connection, caused by excessive network traffic, has delayed your response to the terminal server. Solution:Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator. The remote session was disconnected because the total logon time limit was reached. This limit is set by the server administrator or by network policies. Cause:Your connection to the terminal server exceeded the time limit. Solution:Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator. The specified computer name contains invalid characters. Please verify the name and try again. Cause:The name of the remote computer is incorrect. This might be a typing error. Solution:Try typing the name of the remote computer again. If you receive the same message, contact the server administrator to be sure you are using the correct name for the remote computer. The specified remote computer could not be found. Verify that you have typed the correct computer name or IP address, and then try connecting again. Cause:The name or IP address of the remote computer is incorrect. This might be a typing error. Solution:Try typing the name or IP address of the remote computer again. If you receive the same message, contact the server administrator to be sure you are using the correct name or IP address for the remote computer. The remote session to the remote computer was ended by means of an administration tool. Your administrator might have ended your connection. Cause:The most common cause of this error is that the server administrator needed to perform maintenance tasks on the terminal server. These tasks can be performed only when there are no remote connections to the terminal server. Solution:Try to reconnect at a later time. If you receive the same message, contact the server administrator. The remote session was disconnected because your session was logged off at the remote computer. Your administrator or another user might have ended your session. Cause:The most common cause of this error is that the server administrator needed to perform maintenance tasks on the terminal server. These tasks can be performed only when there are no remote connections to the terminal server. Solution:Try to reconnect at a later time. If you receive the same message, contact the server administrator. The remote session was disconnected because another user has connected to the session. Cause:The most common cause of this error is that the server administrator needed to perform maintenance tasks on the terminal server. These tasks can be performed only when there are no remote connections to the terminal server. Solution:Try to reconnect at a later time. If you receive the same message, contact the server administrator. The remote session was disconnected because the total logon time limit was reached. This limit is set by the server administrator or by network policies. Cause:Your connection to the terminal server exceeded the time limit set. Solution:Try connecting to the remote computer again. If you receive the same message, try to reconnect at a later time. If you still have problems connecting, contact the server administrator. The local computer is low on memory. Close some programs, and then connect to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. The connection was ended because of a network error. Please try connecting to the remote computer again. Cause:A network error prevented your computer from communicating with the terminal server. Solution:Try connecting to the remote computer again. If you receive the same message, be sure that your computer is connected to the network. If you are still unable to connect to the remote computer, contact the server administrator. The client could not connect. You cannot connect to the console from a console session of the same computer. Cause:You are logged on to a computer and you are trying to connect to that same computer. Solution:If you are not on the same computer, contact the server administrator. The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try your connection again later. If the problem continues to occur, contact your administrator. Cause:The remote computer might not be set up to accept remote connections. Solution:Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator. Cause:The remote computer might already have the maximum number of remote connections it is set up to accept. Solution:Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator. Cause:Network problems might be preventing the connection. Solution:Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator. Error: Out of memory. The remote session will be disconnected. Close some programs on the local computer, and then try connecting to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. An internal state error has occurred. The remote session will be disconnected. Your local computer might be low on memory. Close some programs, and then try connecting to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again. Cause:A protocol specifies the way a computer communicates with other computers. A protocol error prevents your computer from communicating with the terminal server to which you were connected. Solution:Try connecting to the remote computer again. If you receive the same message, contact the server administrator. Because of a protocol error (error_code), the remote session will be disconnected. Please try connecting to the remote computer again. Cause:A protocol specifies the way a computer communicates with other computers. A protocol error prevents your computer from communicating with the terminal server to which you were connected. Solution:Try connecting to the remote computer again. If you receive the same message, contact the server administrator, and provide the error code that was displayed in the message. Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. Cause:The most common causes are network errors or slowdowns. Solution:Be sure your computer is connected to the network. Try to reconnect at a later time. If you cannot connect, contact the server administrator. The remote session was disconnected because the remote computer is low on memory. Cause:Memory errors have a variety of causes, but the result is the same. The remote computer does not have enough memory to start and maintain the connection you are attempting to make. Solution:Contact the server administrator. Because of an unknown error, the remote session will be disconnected. The local computer might be low on memory. Close some programs, and then try connecting to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. An unrecoverable error occurred while the client was attempting to connect. Close some programs, and then try connecting to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. An error occurred when the client attempted to connect to the remote computer. Check your system memory and then try the connection again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. Unable to allocate window resources. The remote session will be disconnected. Close some programs on the local computer, and then try connecting to the remote computer again. Cause:Not enough RAM available on your computer. If your computer has too little RAM available, it cannot free enough processing capacity to start new functions, such as applications or connections. Solution:Close all unnecessary programs, and try your connection again. Cause:Not enough disk space available on your hard drive. If the hard drive on your computer is full, there might not be enough space available to allow the swap file to operate correctly. The swap file allows your computer to perform some RAM functions even when there is not enough RAM space available. Solution:Free some space on your hard drive by: Emptying your recycle bin. Deleting temporary Internet files. Moving documents and other data files to a different drive. Removing programs that you rarely use. Deleting old temporary files from your hard disk. Temporary files have a .tmp file name extension, or names that begin with a tilde (~), and are usually found in the C:\Temp or C:\Windows\Temp folder. Emptying your recycle bin after you delete files. Syed Khairuddin

If your DC is running Service Pack 2 and has a Broadcom Netxtreme II nic, check out the following KB, 950224. I have seen nic's become non-responsive and rdp have timeout issues as well. Have you had a change to see if there are any rdp related events in the system log? I would also verify that if your server is using a broadcom netxtreme II nic, the lastest driversare being used. Not sure about HP, butDell addressed the issue with the lastestdriverrelease.Chad

The NIC is Proliant 1020 and not Broadcome Netxtreme II , also there is a strange thing happening , for me I can login using RDP but my friends who are in the same OU with me and in the same Administrators group can't login and it give them a message informing them that they don't have a sufficient privilages to login using RDP and they have to be a member of remote desktop users group to login - although they are a member of Domain Admins and administrators groups .I don't know how to solve !!M.ElBlasy

can you post the EXACT message please ?

the message is :-"To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop Users Group or another group that has these permissions, or if the Remote Desktop Users group does not have these permissions, you must be granted these permissions manually."I get this message although I'm a member of Domain Admin Group and Administrators Group in the DC.M.ElBlasy

Mohamed ElBlasy said:"To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop Users Group or another group that has these permissions, or if the Remote Desktop Users group does not have these permissions, you must be granted these permissions manually." First, add the user to the "Remote Desktop Users" group, and retry. If that does not solve it, try this, adding the "Remote Desktop Users" group to the permission tab of TS Configuration: -From Administrative Tools, select Terminal Services Configuration. -Click on the Connections folder. -Right-click on RDP-Tcp connection, -select properties and click on the Permission tab. -Add the "Remote Desktop Users" group and click OK. let us know if this solves it

yes , it did work .but I note something , the remote desktop users alreadyexist in the RDP-Tcp connection Properties tab , and the users who face problems already included in the remote desktop users , however they can't login using RDP , but when I added them individually user by user inRDP-Tcp connection Properties tab then the user can login using RDP - isn't a strange case !!anyway , your idea is worked successfully , thanks very much .M.ElBlasyM.ElBlasy