I have the server and workstation installed and running (version 1.1.5). I selected the USB device I wanted to redirect and connected to the server using remote desktop. At this point the "USB for RD (Server)" app shows no connections. How can I diagnose this problem?
Here are some instructions on how to redirect USB-device to RDP-session.
1) Please plug your device to Local PC (Workstation) 2) Enter RDP-session 3) Open USB For Remote Desktop Server interface on your Remote PC 4) Open USB For Remote Desktop Client interface on your Local PC 5) Redirect your device
Your device will appear in you USB For Remote Desktop Server interface as connected one.
If the problem repeats please reply this message with detailed description of your scenario (steps to reproduce, exact text of error messages, etc.).
When I tried the software, I did all the steps you listed except that step 2 (entering the RDP session) was last. I did this because your documentation states:
"Redirect USB Device Select USB device you want to redirect and click button.
From now, as soon as used opens remote desktop session, the redirected devices appears on the remote PC."
If it is necessary to enter the RDP session before running your software, please update your documentation.
I'll try the steps in the order listed tonight and see if it makes a difference.
I followed the steps in the order you listed. On the workstation, the device shows up as "ready for redirection" and has a red circle by the icon. On the server, there are no connections listed (it says "available connections: 3 of 3"). Do I need to open up any ports on my firewall?
I asked my network administrator to do this, and he said he needs to know the port number to open on the firewall. What port does USB for Remote Desktop use?
Just to clarify, I'm not running a software firewall on either PC. On the server-side, there is a hardware firewall that filters port traffic. On the client side, my DSL modem acts as a firewall.
Keith, by default, Terminal Server (For Windows 2000 and Windows Server 2003) and Remote Desktop Protocol (for Windows XP and Windows Server 2003) listens on TCP port 3389.
Well, I know that port is open because I can use remote desktop. If your application uses the same port, or communicates through remote desktop somehow, then I know that the firewall is not the problem. Any other suggestions? I'm eager to use your product - and if it works for me I will almost certainly buy it (through the company I work for).
Here's my server info, in case it helps. I'll post my client info tonight.
OS NameMicrosoft Windows XP Professional Version5.1.2600 Service Pack 3 Build 2600 OS ManufacturerMicrosoft Corporation System NameKEITH06 System ManufacturerDell Inc. System ModelDell DXP051 System TypeX86-based PC Processorx86 Family 15 Model 4 Stepping 4 GenuineIntel ~2793 Mhz BIOS Version/DateDell Inc. A03, 1/3/2006 SMBIOS Version2.3 Windows DirectoryC:\WINDOWS System DirectoryC:\WINDOWS\system32 Boot Device\Device\HarddiskVolume1 LocaleUnited States Hardware Abstraction LayerVersion = "5.1.2600.5512 (xpsp.080413-2111)" User Name3NET\walton_keith Time ZonePacific Standard Time Total Physical Memory2,048.00 MB Available Physical Memory744.54 MB Total Virtual Memory2.00 GB Available Virtual Memory1.96 GB Page File Space3.85 GB Page FileC:\pagefile.sys
I updated to the newest version, but it did not fix the problem. I was able to connect from a different client, however. Now I know the problem is not the server or the firewall. The client that was able to connect is an AMD Sempron 3200 desktop PC running Vista.
Do you think the problem with my tablet PC is it's Transmeta processor? It's Intel-compatible, but I have encountered 1 other product that wouldn't run on it (Microsoft Silverlight).
You can reach me through email at Keith-at-Walton.net
Using the client that I got working, I redirected a USB headset microphone to my server. It appeared to work (the server reported "Found new hardware" and installed the appropriate drivers), but Windows would not list this device as available for recording or playback. The only sound device listed is "Microsoft RDC Sound Driver", which is the standard driver used through Remote Desktop. It only supports playback and not recording. Do you know how I can use my USB device to record and play back sound?
Keith, we have released a special solution for sound devices redirection - Sound Over RDP. We would like you to pay your attention to this product http://fabulatech.com/sound-over-rdp.html
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged
Posts: 61