- «Unable to contact settings server». help me please.
- varnie
- ericbsd
- varnie
- Beastie
- Ошибка «unable to connect to socket: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. (10061)» (РЕШЕНО)
- kex unable to connect to socket: connection refused(10061) #6675
- Replies
- mzfr Mar 15, 2021
- hoktophen Aug 31, 2021
- G3eKLAZy Sep 1, 2021
- HermanRas Oct 7, 2021
- SajjadToomari Oct 7, 2021
- gwd999 Oct 9, 2021
- Kali Linux gets a GUI desktop in Windows Subsystem for Linux
- Getting started with Win-Kex
- xorgxrdp doesn’t start on Kali Linux WSL #1101
- Comments
- Brandondqm commented Apr 12, 2018 •
- evanlinde commented Apr 13, 2018
- Brandondqm commented Apr 14, 2018 •
- metalefty commented Apr 17, 2018
«Unable to contact settings server». help me please.
varnie
Active Member
Reaction score: 2
Messages: 111
tomorrow i’ve installed FreeBSD 7.0 RELEASE from scratch and updated all the installed software (which have been auto-installed during installation) using porupgrade. everything goes fine. when i’ve been updating X server and its stuff i’ve chose NOT* to use «HAL» as default blablabla (switching off an appropriate checkbox on its options).
now when i run startxfce4 explicitly by hands in console it runs OKay, but when i’m trying to use SLIM login manager with
/.xinitrc
now when I try to log in, I am getting a popup with the following error:
Then the desktop is loaded but not my normal desktop with my background, icons and so on, (speak shortly, it gets completely broken).
How to fix that? many thanks for your suggestions and help!
ericbsd
Well-Known Member
Reaction score: 65
Messages: 375
varnie
Active Member
Reaction score: 2
Messages: 111
Beastie
Daemon
Reaction score: 542
Messages: 2,275
Why not use FreeBSD 7.2 and upgrade to the lastest version of Xorg, HAL, Xfce, etc?
If you use ports, you should have HAL support enabled in Xorg.
To enable D-Bus and HAL:
— add dbus_enable=»YES» and hald_enable=»YES» to /etc/rc.conf
— run them: /usr/local/etc/rc.d/dbus start ; /usr/local/etc/rc.d/hal start
However, I doubt your problem is caused by HAL itself. When HAL’s not running, Xfce still runs fine and everything is shown (desktop icons, panel, etc), but since it can’t use any hardware, it should crash when you move your mouse or press a key.
What parts of Xfce have you installed? Maybe there’s something missing.
Источник
Ошибка «unable to connect to socket: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. (10061)» (РЕШЕНО)
WSL2 — это подсистема Windows для Linux, которая позволяет запускать подобия дистрибутивов Linux прямо в Windows не используя виртуальные машины.
По умолчанию дистрибутивы запускаются с интерфейсом командной строки, но это ограничение можно обойти, запустив на Linux сервер RDP (удалённый рабочий стол) или VNC, а затем подключившись к нему используя соответствующий клиент.
Для Kali Linux этот процесс был значительно автоматизирован и упрощён, подробности описаны в статье «Как установить Kali Linux с Win-KeX (графический интерфейс) в WSL2 (подсистему Windows для Linux)».
После установки Win-KeX для запуска графического интерфейса достаточно запустить Kali Linuxв WSL2:
А затем внутри Kali Linux выполнить команду:
После этого должен открыться графический интерфейс.
Но иногда это не происходит и появляется ошибка:
В командной строке выводится:
Для исправления этой ошибки нажмите Ctrl+c.
Затем введите команду
Эта команда может вывести что-то вроде следующего:
Вновь попробуйте открыть графический интерфейс:
На этот раз всё должно заработать:
Причина ошибки до конца не ясна — возможно, дело в неудачном старте VNC сервера или процесса Win-KeX, на это указывает строка «Win-KeX process ID 1618… which was already dead», то есть процесс уже мёртвый.
Командой kex stop мы принудительно останавливаем Win-KeX, который при следующем запуске работает нормально.
Источник
kex unable to connect to socket: connection refused(10061) #6675
I have installed kali linux using wsl2. Then I followed this guide to install win-kex . It was working fine till this morning.
Now if I try to run kex I get the following error:
If I run kex stop or kex kill I get the following output:
I googled around to find various methods to fix this. Most of the articles/discussion suggest the following ways:
- Install dbus-x11
- Already installed still having the issue
- Running the following command:
- This is not working for me
In the 3rd method if I do all that and then start the vncserver by running:
And if I run kex after that I get error saying No Matching security Type
Replies
I don’t have and answer. I was just gonna say that it does the same for me
mzfr Mar 15, 2021
This is not the exact fix of the problem but if you want to you can use vcxsrv to run the GUI.
Basically install xfce4 and xfce4-goodies and kali-desktop-xfce . Also install vcxsrv (either download from Sourceforge or use choco). vcxsrv will be installed on your windows machine and not inside the kali VM.
Now run following command in kali terminal:
- if wsl1 then export DISPLAY=:0.0
- if wsl2 then export DISPLAY=$(grep -m 1 nameserver /etc/resolv.conf | awk ‘
‘):0.0
Once all this is done, run xfce4-session , if everything was done correctly you’ll see kali GUI.
After hours of searching to no avail, I have found that you need to:
- do sudo su (all the commands need to be performed by root user) ;
- delete the symlink in /tmp/.X11-unix ( just do rm /tmp/.X11-unix ) ;
- run vncserver (It will now be able to create the server) ;
- Run kex and everything should work.
Marked as answer
hoktophen Aug 31, 2021
@afonsofrancof It worked for me by using root. But I want to use kex —win (without root)
kex —win (not working)
sudo kex -win (work)
kex -esm (work)
I have reinstall the kali and wsl2 still like that.
G3eKLAZy Sep 1, 2021
After hours of searching to no avail, I have found that you need to:
- do sudo su (all the commands need to be performed by root user) ;
- delete the symlink in /tmp/.X11-unix ( just do rm /tmp/.X11-unix ) ;
- run vncserver (It will now be able to create the server) ;
- Run kex and everything should work.
help me a lot thanks
HermanRas Oct 7, 2021
Thanks this was the answer for me 2
SajjadToomari Oct 7, 2021
it worked, thanks!
gwd999 Oct 9, 2021
nope. following these tips did not cut it . still got the same error
BUT what did help was restarting the distro
Adding to the solution found by @afonsofrancof
I was able to recreate this. Following the logs from vncserver stating:
_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 11
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
Xvnc TigerVNC 1.11.0 — built 2021-03-22 21:21
Copyright (C) 1999-2020 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12010000, The X.Org Foundation
Sun Aug 1 21:05:56 2021
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: created VNC server for screen 0
Sun Aug 1 21:06:26 2021
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
_XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 11
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix
I haven’t done extensive testing, but I believe the issue resides in the way that the Standard User and associated permissions are created during initial setup through WSL2. As best I can tell, the only way to launch a KeX environment right now is to do so as root. However, this creates another potential issue: The KeX GUI environment’s login will be root.
Attempting to launch KeX using the user you create during initial setup causes the recurring error quoted above until KeX times out and throws
Error connecting to the KeX server.
Please try «kex start» to start the service.
If the server fails to start, please try «kex kill» or restart your WSL2 session and try again.
I recommend posting this discussion as a bug report to the Kali Community and/or appropriate KeX developers.
Источник
Kali Linux gets a GUI desktop in Windows Subsystem for Linux
Lawrence Abrams
The Kali Linux Team is harnessing the power of the Windows Subsystem for Linux 2 by spawning a graphic desktop environment that is shown directly within Windows.
When the Windows Subsystem for Linux was first released, it utilized a Linux-compatible kernel that translated Linux systems calls into system calls that could be executed by the Windows kernel.
With the release of Windows Subsystem for Linux 2 (WSL2), a real Linux kernel is now run on top of Microsoft’s Hyper-V virtualization architecture.
In addition to providing native compatibility and performance benefits, WSL2 also allows the launching of Windows executables directly from within an installed WSL Linux distribution.
Using this feature, Kali Linux created a package called ‘Win-Kex’ that spawns a Windows VNC client connected to an Xfce graphical desktop environment running within WSL.
Getting started with Win-Kex
Getting started with Win-Kex is super easy, but you first need to install the Windows Subsystem for Linux and be running on Windows 10 version 2004.
Once WSL is installed, install Kali Linux from the Microsoft Store, but do not launch it yet.
After installing Kali Linux, launch it and follow the initial setup prompts to create a new user and assign a password.
When done, open a command prompt and confirm that the Kali Linux distro is using WSL version 2 by entering the following command:
If the above command shows Kali Linux as version 1, you need to upgrade it first to version 2 using the following command:
When upgrading the distro to WSL2, you may be prompted to download and install the latest Linux Kernel, which you should do.
You can then enter the wsl -l -v command again to confirm that Kali Linux is now configured as a WSL2 distribution.
Now launch Kali Linux and run the following commands to prep the distribution with the latest updates and required files.
Once the latest updates are installed, run the following command to install the Win-Kex package.
The above command will install many packages, so please be patient while it performs the install.
When done, you should enter a final command to install all of the Kali Linux tools.
Once again, this command will install many packages, so please be patient.
Now that the system is prepped, you will have a new ‘ kex ‘ command that you can use to access the Kali Linux GUI desktop.
Win-Kex does this by launching a VNCServer with the Xfce desktop environment within the Kali Linux WSL instance. It then starts the TigerVNC Windows client and automatically passes the commands to connect to the VNC server.
To launch the VNCServer and automatically connect to it via TigerVNC, simply enter ‘ kex ,’ and the Kali Linux Desktop will automatically start in Windows.
From there, you can launch whatever penetration testing or research tools you wish, directly from the GUI desktop running within Windows.
Источник
xorgxrdp doesn’t start on Kali Linux WSL #1101
Comments
Brandondqm commented Apr 12, 2018 •
I am running a windows 10 desktop with the Kali linux (Windows App), i am trying to set up xrdp so that i can use the Kali GUI, however whenever I try login I get the a blue screen, then it times out saying the below:
connection problem, giving up
some problem
I have done heaps of troubleshooting and re-search on the web but unfortunately still no luck. Any advise would be grateful 🙂
Below is some logs from xrdp and xrdp-sesman.log
xrdp.log
xrdp-sesman.log
The text was updated successfully, but these errors were encountered:
evanlinde commented Apr 13, 2018
The last video on this page demonstrates installing xfce4 and xrdp and starting an RDP connection:
https://www.kali.org/news/kali-linux-in-the-windows-app-store/
If that doesn’t work, you might try creating a
/.xsession file. (Replace xterm with whatever program you want to start, e.g. xfce4-session .)
/.xsession chmod +x
If you’re still out of luck, try posting the .xorgxrdp.*.log file from your home directory. It may provide some clues.
Brandondqm commented Apr 14, 2018 •
@evanlinde, thank you for getting back to me. In regards to your first question I have followed that video step by step but still no luck unfortunately.
I also tried running the commands you mentioned but still no luck.
Below is the log for my .xorgxrdp.*.log file.
metalefty commented Apr 17, 2018
It seems the xorgxrdp driver is not loaded. According to my observation, you’re the first person who tries to use xrdp on Kali Linux on WSL. You’re a pioneer and you might need to learn by trial and error. It should help WSL friends.
Источник