Win srv 2003, maddening com port redirect problem Tags: Comm Port Windows Last response: June 4, 2009 7:46 PM in Windows 2000/NT Share Bob August 15, 2005 3:10:04 AM Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?) I'm hoping someone has seen this before, its driving me crazy. I have 4 servers runnning win2003, 2 of them cannot map com ports correctly inside of terminal services. I cannot find any noteworthy differences between them. When opening up Windows explorer, the local server c-drive will be shown as " Com1 on 'tsclient' (C " as if it keeps trying to map a local SATA drive as a com port. A NET USE command reflects this as LOCAL= C: REMOTE= \\tsclient\com1 Troubleshooting via Hyperterminal and a couple other apps give random errors indicating that either the port is unavailable, or in use by another app. Has anyone seen anything remotely close that could point me in any direction? thx, bob. More about : win srv 2003 maddening port redirect problem dugrchevy2 June 4, 2009 7:46:59 PM I am having the same problem. Did you ever find a resolution to this issue? Thanks! Can't find your answer ? Ask ! Publish Related resources Com port redirection problem Forum More resources !