okay, have indead some probles getting it to work on Win7
firs of all: i downloaded latest version and i noticed something during workstation setup: intially is says v.2.5.1. but along the way and after install it says 2.5 When checking for version it says : current v. 2.5 new version v. 2.5.1 but download fails : unable to retrieve
btw : server (w2003) is running 2.5.1
then after starting workstation, it shows: Generic RNDIS: ms Windows Mobile Remote Adapter but on server, nothings happens, only says: - Term.Server -> Connection ID:4642
start 'redirect' on workstation does not change anything. i did several (re)installs and reboots, but without any luck
Ok, thanks for pointing this out for us. It looks like this happens on separate machines only, because before saying that it works on Win7 I personally tested the program on a Win7 machine, and it worked correctly.
We're going to release a new version 2.6 very soon, approximately within this week, this bug, as well as some others, will be fixed in the new build.
i'm currently trying this software. I useVersion 2.6 on Client: Win7 32Bit and TermServ is a Win2008 64Bit.
When I open up the Client it lists my Scanner, (and after it showed a yellow "!" and "Problem..." multible times), says Ready for redirection, but Server doesnt seem to be ready for recieving ... at least it doesnt change its status.
Doesnt work with the new mstsc and with an older ( 5.1.2600 in my case )
Server looks like this: http://img200.imageshack.us/img200/734/fabuusb.png
If there are any logs, I can ad them here, if you say me where I find them
Greets Ben
[EDIT] When I use Win2k3 Server 32 Bit it works ... mostly It recognizes the scanner, lets me install the driver, and the Kodak "Scan Validation Tool" ( using TWAIN or ISIS ) scans just fine. But as windows doesnt recognize the Scanner as a Scanning device itself ( it does normally, when installing as a "standard" USB device), my Software ( ELOProfessional ) doesnt recognize it too.
unf. i stll did not manage to get it to work. I justed downloaded latest version 2.6.1
* On server i got : Winserver 2003 UK (latest updates) and USB srv 2.6.1 after reboot in RD window it shows: o terminalserver > conn ID 1135
* On Desktop W7 ultimate and USB ws 2.6.1 My usb devices (HTC touch diamond p3700) is 'seen' by windows. after reboot in RD windos it shows: - Generic RNDOS Win Mobile Rem Adapter - Optical mouse
When i do a 'Redirect USB' on mobile i see following: - icon in menu turns from green into gray - in windows HTC dissappears (under item Computer) - the icon becomes green again - HTC re-appears in windows (under item Computer)
But on the server notings happens, still showing: o terminalserver > conn ID 1135
any ideas, do i need to uninstall stuff (sync centre?) on Win7? or turn stuff of? any help would me great, Thanks
I'd like to ask you to test another product (to make sure your device can really work with our USB virtualization solutions).
Please download usb over network: http://www.fabulatech.com/usb-over-network-download.html
It is similar to USB for RDP. You need to install USB over Network Server on the PC where USB devices are plugged in. USB over Network Client must be installed on the PCs you want to give access to those very USB devices you've already plugged in. That's all.
We need to make sure that your device can work with this very product. And may be you like it better. It gives you the same functionality as USB for RDP.
* On server i got : Winserver 2003 UK (latest updates) and USB srv 2.6.2
* On Desktop W7 ultimate (64bit) and USB ws 2.6.2 My usb devices (HTC touch diamond p3700) is'seen' by windows, amoing other devices: - Generic RNDOS Win Mobile Rem Adapter - Optical mouse - Fingerprint sensor
But now on server it does not show a connectionID, it only shows: o terminalserver
i checked user sessions, did severall reboots, updates windows, but no luck sofar. any suggestions?
It's great that you tested the latest version but it's a pity id doesn't work. I wonder if you managed to test USB over network (I asked you to do so http://www.fabulatech.com/usb-over-network-download.html). We need to make sure that your device can work with our virtualization tools. And in any case (even if you do not like USB over Network) we will need it to do the remote debugging. USB over network Server will serve as the tool for accessing your device for we could resolve this issue.
i did not test yet, because at this point it looks like its not related to my device because other/normal devices (like mouse) do not work either. so, there must be something else wrong.
Ok, but nevertheless you need to try USB over Network because of two reasons: 1. It may work with no problem and may be you will stay with this product; 2. We need it to do the remote debugging in case you decide that you really need USB for RDP.
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Posts: 6
Quote
Modify
IP Logged
