Re: Anydesk For Windows Server 2003 Free Download
Beat Przybylski
Hello everyone
I have strange problem with DNS serwer on Win2019 with AD, IP6-off
in general all working well, but dont resolving just one domain (anydesk.com)
I try flush cache, change forwarders, main servers, etc
I dont have any idea whats wrong. it look like just this name don't send out...
Did you try create a conditional forwarder for impacted DNS zone anydesk.com to specify the correct forwarder for this zone.
Check if the network flow are already opened between local DNS server and the DNS forwarder.
Every other name is translate to adres IP corectly, but this one don't. 2 weeks ago it worked well.
Every computer with other dns server (eg. 8.8.8.8) in this network find anydesk.com without problem.
Another possible issue is that for some reason the upstream server is taking longer to respond and nslookup is timing out before the server responds, you can increase the timeout by using set timeout=10 and see if get a result.
I run an "energy saving computer" with Garuda - XFCE as a download server without a screen, without keyboard and mouse. I operate the computer via anydesk. The following problem arises: When I connect a screen, I set the resolution to the correct 1920x1080. If I remove the screen, the computer goes back to a 1024 * 768. I cannot change this with "Settings" "Display" because no monitor is connected.
The "Download PC" is in the technical room and is on the network. I work on another PC (my desktop in the office) and I operate the Download PC from the Office PC via Remote Software (Anydesk).
I add a picture from the workplace. On the left is the download PC on screen 2 and on the right is my work screen 1. Both screens are connected to the work computer in the office
With the logon formats. both are valid User Principal Name ( with the @) and Down-Level Login Name (with the ). Maybe the backslash is not right and is not working since it is a forward slash from the example you typed.
I see, if it is not working, it is because the second workstation is a windows server. Regular users are not able to RDP to windows servers. Try adding it as part of the domain admins and try again. If it works, the connection to the server is ok, and you want to modify the Allow logon locally and/or the Allow log on through Remote Desktop Services User Rights Assignment accordingly, either through the Local Security Policy or through Group Policy to allow a regular user connect to a windows server.
I am fighting with some remote control applications such as teamviewer or anydesk. In each case I can not get my laptops to be a server. I would like to be able to get a remote display (or control) to any other linux machine or android smartphone.
I got too much issues on my system with teamviewer and am now trying hard to get anydesk working.
some precisions:
- I observed this behavior on 2 different machine with same system
- anydesk works well as a server on an other machine with manjaro, so I guess I am missing a package or have a different config somewhere
- I installed and started the xrdp.service, no change
Indeed, anydesk run perfectly with Manjaro (KDE) and not on my system, so I guess a DE or something like this makes it working.
Do you have some advices on how I can find what is wrong with my session type?
Regarding the Manjaro part. No the actual DE is irrelevant, it matters whether your session is properly populated, if you use a display manager they will usually invoke relevant integrations with systemd themselves.
Hi 2ManyDogs,
Sorry for doing that. I have already searched during many days and am pretty sure there is a solution somewhere and you guys can help me. So, what am I supposed to do? (it's a real question)
Then I performed lots of tests. I do have the same issue with a new fresh user.
I tested another DE and a display manager.
KDE Plasma works fine but still have the same issues (remote control issue, xrandr, notify-send no effect with sudo)
V1del suggested me a DM, I enabled sddm.service and removed the autologin on systemd.
Then, I got a black screen at boot with the booting messages on the consol and a mouse that can move. But I can not do anything.
There is the Xorg.0.log corresponding at this attempt:
Yes you are not supposed to be able to use these commands with sudo plainly like that, they will not have the dbus session of your user available, nor the X environment of your users xorg server. In case this is actually relevant, you should not try to sledgehammer problems by prepending sudo to commands willy nilly, that will often not lead to success. Are you trying to run the standard anydesk client as root despite not needing to? Then just don't and this also would explain your issues.
I'm not familiar with anydesk, but e.g. in the case of teamviewer there is a systemd service for starting the background daemon, once that is started the actual teamspeaker client has to be launched as your normal user..
About anydesk, I run it as my user on my normal seesion, I precise that I can connect to another device from my system but I can not in the opposit way, e.g. I can connect to my android smartphone, but not the opposit.
Just got stuck with the exactly same problem: Installed anydesk on my Arch desktop and Manjaro laptop. Manjaro is preconfigured somehow, Arch starts via xinitrc somehow (at least it starts directly into the desktop without asking me for my password, also no DM is installed). My .xinitrc is rather simple
Actually, Teamviewer versions newer than 12 also fail to work with a DE launched with a plain startx so I suspect the issue somewhere there. I wouldn't mind to install something like lightdm on my Arch machine but to be honest, since my Arch install is - I don't know, maybe 8 or 10 years old? - I completely forgot how I configured the startup process back than and don't really know how to switch to lightdm without breaking things. I guess, I got lazy and dumb since my main machine's Arch just runs smoothly and I got too comfortable with Manjaro on other machines...
Oh well, I'm not surprised about what you are saying. The install is very old and as people say, never touch a running system. The dbus-launch didn't lead to any noticeable problems so far, neither did the missing if block described in the wiki, and you don't usually check on your .xinitrc daily, right?
Hi! Any progress here? I have the same problem. When log system with lightdm no problem to connect using anydesk. Howerver when use startx from tty anydesk cant connect with error "Remote display server is not supported". I have cloned all diff variables in lightdm session but problem persists. I dont know what anydesk is checking when connect, but one interesting thing is that if try to connect when no user is logged and lightdm is on screen the window for confirm connection appears in login screen.
I tried everything posted here, but without success, I can't have anydesk functional; I installed and ran archlinux with enlightenment, without login manager, everything is perfect but anydesk does not work; the moment I install xfce / kde / gnome, keeping the enlightenment, under xfce / kde / gnome it works without problems, but the moment I log out and log in enlightenment, ready, anydesk no longer works it crashes.
I also tried installing the entrance, but without success.
If you have any advice on what I could try, what I could do ....
27.04.21
I noticed that if I launch anydesk with a random number, anydesk with error message is launched, recipient that does not exist, and from the keyboard I can enter a real address, it connects, but no I have no control over the computer, nothing works neither mouse nor keyboard and I am forced to restart the computer. I have no idea why it doesn't work ....
Never tried installing windows but my software GitHub - turtle0x1/LxdMosaic: Web interface to manage multiple instance of lxd has a spice viewer built into the web interface so you should be able to access & install windows!
In either case, once your client machine (desktop) can access the remote LXD server, then you can do lxc remote add my-server IP-ADDRESS:PORT to add your server to your local client and finally do lxc console my-server:VmNAME --console=vga to get to the VGA console.
d3342ee215