WTware Technical Support

...Well, yeah this is true apparently for Windows and most other OS's. However some, such as WTware do not play well. I had to add the second DHCP server into my Extreme Summit switch config. Once that was done, WTware started working with DHCP properly again. Could you return it back and make me n...

The log is showing the below. The part that interests me is Skip 'psk='. It is not log but small part of log. I need full log. 'psk=' is a wifi poassword. We do not publish it into log. "wpa_state=COMPLETED" - wifi password is right, it connects to wifi access point. Later it should ask D...

We can only redirect mass storage devices. Some phones can emulate mass storage. We can not redirect PTP or MTP devices.

Is there a way to a) ignore this error No. It's wrong situation where two servers offer different addresses for one client. WTware have no reason to choose one of them. b) manually set a static DHCP - Server it should obtain the IP from? Only one DHCP should offer IP for client. If there are severa...

Send us one device if you have a lot of similar and we will try to support it. Or try more recent card reader. It's better to try device that works with raspbian on raspberry.

It's an old version. New version should have needed features. Send me terminal log to support@wtware.com for the latest version: http://wtware.com/logs.html

Please, send me to support@wtware.com terminal log file: http://wtware.com/logs.html

What application do you use to edit wtware.pxe? Sorry, not wtware.pxe. wtware.pxe is a binary executable. pxe.cfg is a config for wtware.pxe, and linux kernel command line for PXE boot lives in pxe.cfg. syslinux.cfg on boot USB stick for USB boot. It's a usual text file, use Notepad to edit. Add so...

Update bios if possible. Right solution is to pass some magic word to kernel command line, but it's too high magic. Kernel command line lives in wtware.pxe file, options are listed here: https://github.com/torvalds/linux/blob/ ... meters.txt

We add device to supported after some user reports it works. This reader was added years ago. Perhaps something was changed in driver or in kernel usb code. Or manufacturer sells another device with the same name. I've just added "some devices are not supported" to list. In general, "...

https://wtware.com/docs5/logs.html
Send log to support@wtware.com if you think there is sensitive information.

With current version such config should work:

connection
server=192.169.1.1
connection
application=shutdown

It adds "shutdown" to menu.

If we make reboot in the same way as shutdown, will it be ok for you?

1. Azure manual tells to use the same network addresses? Show me it.
2. Will "ping 192.168.10.4" go from windows computer in "Local User Devices"?

It's wrong network design. Different networks splitted by routers can not have the same network address 192.168.10.0.

Connect to the same server with the same username using mstsc.exe. If prompt appear, it's not related to wtware. Then ask google for solution for mstsc. Looks like some weird application in startup. Never saw this before.