Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Remote connections end with cdm.exe error 1
- Thread starter Damien111
- Start date
longlivegoku
IS-IT--Management
Are you connection your local printers and local hard disks when using the remote desktop connection?
Ed
Ed
- Thread starter
- #3
No. It does it on pc's without local printers and with. they are not mapping to local drives either. This happens with Citrix and Remote Desktop. I can't find anything unusual like a mapped drive that isn't there anymore. Nothing like that.
Jeff, MCP
Jeff, MCP
-
1
- #4
How about a little detail here...
What is the CMD.exe error? Listing the actual error might help the diagnosis. Any event viewer errors?
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
What is the CMD.exe error? Listing the actual error might help the diagnosis. Any event viewer errors?
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
- Thread starter
- #5
Event viewer says "The CDM redirector has timed out a request". This only happens on our Citrix server so I'm leaning towards Citrix. There is a metaframe error in Event Viewer that states "An error occurred retreiving client printer properties. Default printer properties will be used instead". This CDm error just started. No change has been made to the server, printers or clients. Besides, it doesn't matter which client box you log on with. Citrix or Remote Desktop. Remote Desktop leans me away from the Citrix contradicting what I said earlier in the post.
Jeff, MCP
Jeff, MCP
(In the future, it is also important to list Event Viewer ID Numbers and Sources)
How about this article for the solution:
or this one:
Citrix states in their article: CTX207308
CTX207308 - CDM Redirector Timeout Event ID 70 in MetaFrame 1.8
This document was published at:
Document ID: CTX207308, Created on: Aug 1, 2000, Updated: Jun 10, 2003
Products: Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000
In the Events Viewer, one might find a varied number of Event ID 70 in Source: CDM Redirector. This occurs when the CDM Redirector timed out on a request to access a client device.
This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear. The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers). Enable them one at a time and monitor the client's logon process.
If you find that you are receiving these timeouts due to network latency, you can modify the timeout values in the registry key shown below:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Make sure you back up the registry before you edit it. If you are running Windows NT, be sure to update your Emergency Repair Disk (ERD).
The registry key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters
Increase the settings for the following:
RequestTimeout: Default is 60 (in seconds)
DirCacheTimeout Default is 30 seconds
CacheTimeout is 60 seconds
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
How about this article for the solution:
or this one:
Citrix states in their article: CTX207308
CTX207308 - CDM Redirector Timeout Event ID 70 in MetaFrame 1.8
This document was published at:
Document ID: CTX207308, Created on: Aug 1, 2000, Updated: Jun 10, 2003
Products: Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000
In the Events Viewer, one might find a varied number of Event ID 70 in Source: CDM Redirector. This occurs when the CDM Redirector timed out on a request to access a client device.
This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear. The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers). Enable them one at a time and monitor the client's logon process.
If you find that you are receiving these timeouts due to network latency, you can modify the timeout values in the registry key shown below:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Make sure you back up the registry before you edit it. If you are running Windows NT, be sure to update your Emergency Repair Disk (ERD).
The registry key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters
Increase the settings for the following:
RequestTimeout: Default is 60 (in seconds)
DirCacheTimeout Default is 30 seconds
CacheTimeout is 60 seconds
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
- Thread starter
- #7
Did you do this (mentioned in the Citrix Article) in order to troubleshoot the problem:
"This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear. The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers). Enable them one at a time and monitor the client's logon process."
The Reg hack is only for problems related to Slow Network problems.
I think your guess is right...this seems to be Citrix problem. You may consider calling Citrix to help you out on this problem or jump into a Citrix thread...probably get better advice...
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
"This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear. The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers). Enable them one at a time and monitor the client's logon process."
The Reg hack is only for problems related to Slow Network problems.
I think your guess is right...this seems to be Citrix problem. You may consider calling Citrix to help you out on this problem or jump into a Citrix thread...probably get better advice...
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question
- Locked
- Question