- This topic is empty.
-
Posts
-
The problem that I am having is I am trying to use the com1 port on a s10. I am connecting to 2003 terminal server via RDP. I have on the server port redirection enabled. I have talked to wyse and they where not much help. They have me using the net use command. net use com6 \tsclientcom1. I do that and it says it was succesful but when I type in net use again it shows up as unavailable. They say they have never seen this problem before, which makes me start to wonder 1. I totally screwed this thing up or 2. they don’t know what they are talking about. So I hope some one can help me with this problem. Thanks in advance.
Hi,
I just tested with
net use com3 \clientcom1
To map a serial PDA and it worked but you are right it said unavailable even though the device worked.
Tt is common to use a script to map com ports in RDP,
what device are you trying to use?Cheers,
-TTI am connecting to a CMM machine. It is a milling machine. It just uses simple serial communication. When we could not get it to work we just used a USRobotics modem to test with. Still could not get it to work though. I could not get windows to detect it when connect through RDP. If I started a HyperTerminal though and type in ATZ or ATX i would get a response. So to be honest with you I am not sure what is going on.
OK,
Windows will not detect the modem as a modem through a session, the AT command will work. Remember there are limits to the bi-directional abilities of RDP.
Question, does this setup work on a normal PC when you map the device via the com port in a RDP session? I always test in a PC/RDP setup first and then try a thin client. Can you test this and post the results?
Thanks,
-TT
- You must be logged in to reply to this topic.