I have recently spun up a new Ubuntu 12.04 instance in AWS. I had no issues connecting to and opening an SSH terminal to the server. Having connected to the instance, I was able to install the Ubuntu desktop and FreeNX without any problem, as well as enabling password authentication on the server instance.
I downloaded and installed the NX Client for Windows on a PC running Windows 8. After entering the user credentials I can connect to and authenticate into the server. I'm brand new to the Linux world, but at this point everything was going so smoothly I was about ready to throw my Windows licenses to the dogs - good thing I held off on that.
"Problem: At the client, the !M logo window appears, but after a few seconds that window just closes, even without showing any error message."
That problem statement is in quotes because it's precisely the issue described in FreeNX Ubuntu Community support documentation https://help.ubuntu.com/community/FreeNX#Troubleshooting.
So naturally I follow the solution in the guide:
"Solution: The issue is due custom VNC configuration. In the server, access your home directory and run these commands,"
sudo rm .Xauthority*
touch .Xauthority
chmod 600 .Xauthority
Unfortunately, this did absolutely nothing to resolve the issue. The problem would be easier to diagnose if I had an error message, but reference the Problem statement, there is no error message to be had. Several hours of googling yielded nothing, so wondering if anyone here has encountered this problem in the past, and if so, they would be willing to help.
Thanks!
Related
I have a problem since yesterday, I made the error of uninstalling Nodejs to put the latest version (14.17.2 LTS OR 16.4.1 Current) and since I have this error ... I do not understand, this is my personal pc and I am the admin (normally) I do not understand either how to solve this problem and in the meantime I can no longer work ...
I've been looking for solutions since yesterday but can't find what I need to do to fix it ..
(PS: excuse my English, I'm French)
I attach you the capture of my administrator account
Windows 10
Error Nodejs
administrator account
MAJ 06/july/2021:
I finally managed to cheat the thing, downloaded the Nodejs ZIP folder, and put it straight to my hard drive and it worked.
Open Command Prompt (cmd.exe) as administrator and type or copy/paste:
net localgroup /add "Authenticated Users"
Then click the "Retry" button or run the installation file again.
I'm previewing Azure Labs (managed) which is in preview at this moment. I've followed a tutorial from Microsoft on how to get started.
I've created a classroom lab with 3 virtual machines, based of a default Ubuntu image from the Marketplace. I've copied/pasted the default credentials of that template which is used for all virtual machines in that classroom lab.
Then I published it, added a user, got a registration link and used that to register as that user (a so called student). I can see the VM I expected to see. I can start it, wait some 30 seconds and then I can click on the connect button to get the ssh connection details. I open terminal, paste the ssh connection details and I get a password challenge. Excellent! So far it all works as expected. But when I enter the password I copied from the default template, permission is denied. So I try again, denied. So I wait a minute (maybe the VM needs some more time to fully boot up), but permission denied.
The tutorial looks very easy to me, I choose a default Ubuntu 18.04 LTS image to be used. I even tried to create a new classroom lab, but during creation of that template, I choose to start it, connect to it and install additional software before publishing it. That worked (as I expected). But when I publish that classroom lab, register a student account and try to login to a VM in that classroom with the correct default credentials I used to install additional software, I too get permission denied.
I'm confused.
Anyone?
Thanks to D43m0n for the feedback from Microsoft. I have been having the same issue but on CentOS images.
It appears the provisioning of the student machines after the template is published locks the default user account. Creating a new user is not such a great workaround because students will have to change the SSH or RDP settings to connect. The issue also affects more than just Ubuntu. I am seeing it on the newer version of CentOS (7.8 and greater it looks like). I think it is for any images that use cloudinit for the provisioning of the student machines. The older CentOS images use WALinuxAgent and don't seem to have this issue.
I have worked around it unlocking the default user account in /etc/rc.d/rc.local so that is executed on boot. The rc file differs on other systems so check what it is for your flavour of linux.
usermod -U default_username
This has fixed the issue for me until Microsoft fix their provisioning.
thanks for posting! Were you able to connect to the template machine (Ubuntu) and then you weren't able to connect to the student machine (Ubuntu)? Could you copy the exact error message you're seeing?
We are aware of an issue with Ubuntu images--when you connect, the VM tells you to reset the password but doesn't provide a way to do so. We're working on a feature that will resolve this issue.
Is this what you're seeing?
You can use other flavors of Linux fine.
Let us know!
In the template-vm create a new user:
sudo adduser newuser #follow the agent
sudo usermod -aG sudo newuser
after that you can start your course vm's an login with that user.
I had one client who could not connect to a samba share giving the error that the credentials where wrong while I was sure they where not.
This happened suddenly on a laptop with Windows 10 while other clients with Windows 10, Windows 7 and Ubuntu etc. all where able to connect.
At first I was suspecting the problem beeing a change in the hash or key for the share - and maybe it really was because Putty was saying so when I tried to SSH into the server.
But I could not find any saved connection to delete with net use.
The solution was to change a setting in secpol.msc which is accessible as administrator via the search even in Windows 10 Home.
I had to set LAN-Manager-Authenticationlevel to just send NTLMv2.
You will find this setting under Security settings -> local -> Security options -> Network Security: LAN-Manager-Authenticationlevel.
(I translated this from German. Feel free to edit with nativ english wording.)
I want to connect to my webserver, but the ssh is disabled, so decided to try using the webdisk service the server-provider suggested. My Nautilus though can't seem to be able to connect the davs server.
When I run it and ask to join it recognizes the davs address but when I press the "connect" button, it shows me an error saying: "unhandled error: cannot connect to destination (...)".
Whenever I try doing this as superuser though it doesn't even let me click on the connect button saying: "This file server type is not recognized."
I thought it might be due to some packages missing to handle davs connections. Can it be the problem? I'm using Nautilus 3.10.1 on Deepin Linux (which uses the ubuntu repositories). Can anyone tell me what packages do I need to install, or how do I get this working?
I'm quite sure you've found the answer yourself since Jan 2016, but for the sake of others who may search for the answer, I'll say it:
Make sure you have davfs2 package installed.
I have recently been receiving the following error whenever I am asked to supply the host username and password in Oracle DataGuard's Enterprise Manager (EM) tool: RemoteOperationException: Error reading error from command. Any configuration or management that needs to be performed and requires the host credentials is throwing this error. This is one of the most unhelpful errors I have seen in a long time. I have checked all of the log files I can think of and I can't find any error logs or indications to the problem. I verified that I can log into the servers with the credentials that I was trying in EM, I verified the connection configuration through EM using the built in test tools, and I verified that all of the saved passwords in EM were correct. This was working on the initial installation. Sometime over the last couple of weeks it stopped working and I'm not sure why. The hosts are running Linux Red Hat 4 Enterprise and Oracle 10g.
Reinstalling the OEM agents fixed this issue. Somehow, all of the agents seemed to be corrupt.