WTware RDP client

Thank you, it's our error. Will be fixed in the next version.

Not a problem but a lot of coding. Replace hardcoded boolean variables "main monitor" (true for first, false for second monitor) with list of monitors everywhere. We'll do it after three monitor outputs will be common for thin client hardware.

Not with wtware until devices with three regular video outputs hit the mass market.

In theory, you can connect 5 displays to a Raspberry. In practice, third HDMI display is not possible at a reasonable price.

It should work. "Alt Gr" key used in "Alt Gr + Q" should make Euro with "Alt Gr + E" in recent wtware version.

Please, show me terminal log after "Alt Gr + E" : http://wtware.com/logs.html
And photo of the screen with wtware interface you try to enter Euro sign in.

Mail it to support@wtware.com

No way, sorry. We are focused on network boot and don't want to make wtware so big.

Win + E is redirected now. It took only year and a half

Windows TFTP client is easier to reproduce for me.

Do I understand correctly, on the same virtual machine, with the same network environment, no other changes, only:

1. Turn off SolarWinds TFTP, start WTware TFTP service, and Windows TFTP client tftp.exe from another windows machine won't download ...

When a Thin Client is starting, I can see that it obtained an IP, I can also see in Wireshark that the read request packets are incoming on port 69/udp. WTware doesn't bother to reply to those requests or even to log anything.

Firewall. Or broken IP stack on Windows. WTware TFTP service logs ...

I attempted to network boot. THe DHCP options are all set correctly (verified with test software) but every client gets a DHCP IP address and then shows a TFTP timeout. Testing locally on the WTware server the TFTP file can be obtained with a test client. Remotely from any different PC the TFTP ...

VirtualHere: https://forum.wtware.com/viewforum.php?f=27

Install device software on Windows. Connect device and look into Device Manager. Will you see virtual COM ports here? If so, serial redirection in WTware may (if com-usb bridge is standard) work too:

config=com77(usb)
http://wtware.com ...

Does it work from text config?

In Microsoft world, Windows DNS updated by Windows DHCP server, and it works. WTware report hostname from clienthostname= to DHCP.

There is no minimalistic nsupdate in busybox. In my Debian, /usr/bin/nsupdate binary requires about 15 megabytes of libraries to run. Sorry, I don't want to increase ...

is correct right syntax. Please, read logging manual and make log as described:

http://wtware.com/logs.html

I'm sure it does not write "not accepted by wtware" text on screen.

What exactly you do and what exactly goes wrong?

Also, show me the log: http://wtware.com/logs.html

I always have to free unused IP manually.

Why?

If new device can not obtain IP, please show me DHCP service log. After problem and before you delete IP manually. Wtcenter > Button with wrench in top left corner - Open DHCP Service screen - reboot client and reproduce problem with no IP - Save ...