Usb redirector client cant connect
Yes, tried switch off firewall on home computer. Some home WX 2004 do work, some not, some 19 work, some not etc. Home computers vary, of course, also by WX version. Work computers is mostly same conf, all WX 2004. Some home computers, as I wrote, using RDP accessing work computers from home, not suffer by this problem. So, yes, seems to ID card is in some aspects seeable from Home on Work. What interesting, for me, when ID card not recognized by ID soft, some sites, using for authentication ID card PIN, is still accessible (twice is asked PIN1), but sites needed proper (certificates) access (banks etc.), not (this is expected as ID card not recognized, certs not retrieved). Meaning, trying RDP from local another work computer to same Work computer in question. OK – WorkX > Work, ID-card identified using ID card soft (DigiDoc4). OK – Home > Work2 and Work3, ID-card identified using ID card soft (DigiDoc4). Not – Home > Work, ID-card not identified using ID card soft (DigiDoc4), used another user domain account. Not – Home > Work, ID-card not identified using ID card soft (DigiDoc4), used local account.
Not working – Home > Work, ID-card not identified using ID card soft (DigiDoc4), used domain account. Trying RDP from Home computer to Work computers. The first match for any devices is considered final. When the user tries to redirect USB device to Virtual Desktop, it is checked against each USB policy rules in turn until a match is found. Home (source, Lenovo Tiny) computer, let’s say – Home, target (destination) computer, let’s say – Work (also Work2, ordinary desktop, and Work3, also Lenovo Tiny). Click Add on Client USB device redirection. (No Answer, just a reply, too long for fitting as reply.) Windows-10-general remote-desktop-services remote-desktop-client Sure, there is thousands of details involved, absolutely. Even all (I’m aware of) services used is running under system account, related to use (redirection) of smartcard. yes, there is some options to test out more – using on remote side local user, to try remove and create new domain user (on work computer) for same person etc., but … seems to it narrows down to user-something.
USB REDIRECTOR CLIENT CANT CONNECT WINDOWS
Something related to particular (Windows domain) user!? What could it be? Started to happen after applying Windows 2004. Then we tried RDP from home to another computer (for same user) and … surprisingly smartcard was identified. Then we tried RDP to computer which didn’t work (as descripted before) from another local computer, fine, redirection did work as expected. Yes, services running, yes, smartcard redirection selected on host etc. Anyway, there wasn’t obvious connections between Windows exact versions on both ends for getting redirection to work. Sure, testing is for us (IT) complicated as we don’t have overlook over home computers.
USB REDIRECTOR CLIENT CANT CONNECT WINDOWS 10
Host (at home) computers vary – Windows 2004, Windows 1909, even older Windows 10 computers, at work all now W2004. On some computers, in other hand, no change, smartcard redirection does work as usual. usual error when card is not inserted pops up. But “some” was many enough to start to investigate what is going on. Till applying Windows 2004 (Windows 10 April 2020 feature Update) everything seems to work ok, but after we upgraded computers at work to 2004 … this approach didn’t work anymore on some of computers. For identification and signing etc., very convenient. So, user enters at home computer smartcard (Estonian ID Card) and need to use it at work. One of these is using smartcard redirection. As people start to work more and more at home, we (IT staff from trenches) start to have RDP-related problems. On the thin client we are prompted for credentials but upon entering these it returns an credential error - the credentials are 100% correct ! Connecting from a windows machine connects no problem, so this is looks like a setting mismatch between the thin client and the RDS Server. One thing noticed on the non working server was : Network Security: LAN Manager authentication level had been amended, but have now since removed the reg key and this is now showing as undefined (Same as working server) but still not connecting. I have compared working and non working server settings (Security Layer, NLA, Encryption level etc) and these are identical.
We are able to connect to other servers with the same OS - so believe it is something to do with this particular server, more so a particular setting that is preventing connection. We are encountering an issue connecting to a Server 2012 R2 RDS Server using a HP T530 Thin Client.