Page 1 of 1

Windows client does not remote

Published: April 29, 2016 - 4:09 PM
by izhocell
Hello,

I'd like to test the wapt solution, so I installed the server on a 2012 R2 machine. All my test clients connect after installing waptagent.exe, except for my PC. evil:

I've tried almost everything: uninstalling and reinstalling multiple times, disabling the firewall, antivirus, and rebuilding the agent, but nothing works. The worst part is that I have a VM on my machine that connects just fine.

I found the command `wapt-get register`, which, if I understand correctly, allows me to manually connect the client.
It gives me this:

`C:\wapt>wapt-get register`
About to speak to waptservice...
Waptservice User(): administrator
Password: *********
Inform the server of this machine's inventory
.......TypeError: coercing to Unicode: need string or buffer, int found`



Do you know why this is happening?

Have you ever encountered this problem?

Izhocell

Re: Windows client not working remotely

Published: May 9, 2016 - 6:21 PM
by dcardon
Hello izhocell,

Could you please return the result of

Code: Select all

wapt-get register -l debug
Your problem may be related to this bug:
https://roundup.tranquil.it/wapt/issue620

with the patch
https://github.com/tranquilit/WAPT/comm...b29613e8a6

Sincerely,

Denis

Re: Windows client not working remotely

Published: May 9, 2016 - 6:26 PM
by dcardon
(Continuing from my message above)

To see if this is indeed the bug mentioned above, you can test the command line
: `c:\wapt\dmidecode.exe > out.txt
dir out.txt`

and check the file size. Normally, it shouldn't be much more than a few tens of kilobytes. If the file is very large, it's likely that you have the manufacturer's logo encoded in the BIOS, and dmidecode (which retrieves the machine's hardware information) is returning a large bitmap that can't be uploaded...

Sincerely,

Denis Cardon

Re: Windows client not working remotely

Published: May 11, 2016 - 09:04
by izhocell
Good morning,

Thank you for your answers.

I ran the `wapt-get register` command in debug mode and here is the command output

Code: Select all

C:\wapt>wapt-get register -l debug
Current loglevel : DEBUG
About to speak to waptservice...
Connecting to Waptservice event queue...
Connected to Waptservice event queue
Call register URL...
Waptservice User () :administrateur
Password: ************
Task 5 added to queue
Informer le serveur de l'inventaire de cette machine
.......TypeError: coercing to Unicode: need string or buffer, int found
.Leaving Waptservice event queue
dcardon wrote:Hello izhocell,

Could you please return the result of

Code: Select all

wapt-get register -l debug

Re: Windows client not working remotely

Published: May 11, 2016 - 09:42
by izhocell
I just followed your instructions and as you can see, my out.txt file weighs approximately 30KB.

Code: Select all

C:\wapt>dmidecode.exe > out.txt

C:\wapt>dir out.txt
 Le volume dans le lecteur C n’a pas de nom.
 Le numéro de série du volume est F1CF-152A

 Répertoire de C:\wapt

11/05/2016  09:04            30 532 out.txt
               1 fichier(s)           30 532 octets
               0 Rép(s)  95 178 678 272 octets libres
I find your story about the manufacturer's logo being encoded in the BIOS strange, because my colleague has the same PC as me and it works perfectly for him. But I'll still try the suggested fix.

THANKS
dcardon wrote:(continuing my message above)

To see if this is indeed the bug mentioned above, you can test the command line
: c:\wapt\dmidecode.exe > out.txt
dir out.txt

and check the file size. Normally, it shouldn't be much more than a few tens of kilobytes. If the file is very large, it's likely that you have the manufacturer's logo encoded in the BIOS, and dmidecode (which retrieves the machine's hardware information) is returning a large bitmap that can't be uploaded...

Best regards,

Denis Cardon

Re: Windows client not working remotely

Published: May 11, 2016 - 09:56
by izhocell
I downloaded the patch and then replaced it in the wapt install folder on my machine, but when I run the command wapt-get register I still get the same error message.

Is this the correct procedure to follow?
dcardon wrote: It's possible your problem is related to this bug:
https://roundup.tranquil.it/wapt/issue620

with the patch
https://github.com/tranquilit/WAPT/comm ... b29613e8a6

Regards,

Denis

Re: Windows client not working remotely

Published: May 19, 2016 - 4:49 PM
by izhocell
Can't anyone help me?