Back to Blog
Wsl2 kali6/16/2023 ![]() This appears to be a bug in Kali for WSL in general. Previously it was an incorrect firewall issue (fixed after editing firewall rules) and windows X-server config issue (solved by installing a diff x-server app as i had no idea what is wrong) I did not make any other changes before this - only read through various proposed resolution steps on the net, regarding log file permissions & exe's etc - so I expect this should work for others.įYI this is the 3rd install of kali win kex (on different machines) when some kex mode has given an error while other 2 work. This is probably required as -esm brings up a VNC client to connect to Kali while the -win & the -sl modes bring up RDP client and an X-Server (client) resp. Since I had already set a password for the "kex -win -s" which was also working with kex -sl -s so it never occurred to me that esm needs a password set again. Don't know why error doesn't mention pwd. Same problem, here's what finally worked for me:įirst run the following, and set a password: sudo kex -esmįrom then on it just starts working. However, a situation arose where I had no option but to reinstall windows and set everything up again. Note: I have used kali-win-kex on this very machine before with no issues. In addition, simply starting Kali using the kali or wsl commands gives me the following error message: -bash. with cmdkey producing terminal output and mstsc opening the RDP client when executed through Win+R Run dialog usr/bin/kex: line 371: mstsc.exe: command not foundīoth cmdkey.exe and mstsc.exe are valid windows programs on my machine. Please enter ESM password for user jralphw: usr/bin/kex: line 291: cmdkey.exe: command not found On attempting to run kex -esm -s I get the following error: ┌──(jralphw㉿jralphw). ![]() I followed instructions for win kex step-by-step as shown on .(Note that I have carried out this process multiple times before with no issues) I am having issues using kali-win-kex in ESM mode on Kali Linux.
0 Comments
Read More
Leave a Reply. |