I'm experiencing a problem when trying to connect to a remote linux server using tramp and putty on windows.
I'm using the following function to call and connect to the remote server
(defun server-connect ()
"Tramp-connect to remote system home folder"
(interactive)
(find-file "/plink:myusername#server_address:~")
)
And by using it I can successfully open a dired buffer to the remote server home folder (although sometimes I experience an authentication problem at this point as well).
The problem is after I open a remote file, make edits, and try to save those edits, tramp asks for my password again. At this point I type my password and tramp doesn't seem to be able to authenticate it, because it continues to ask me my password until the remote server blocks me out due to too many failed attempts.
The same thing happens if I try to open a remote REPL through ESS for example.
I don't have much experience with tramp, and debugging this has been really hard, because any time I'm locked out of the remote server I have to wait for 24h.
Thank you,
Related
I log into my work pc from home via VPN + Remote Desktop Connection.
When I log into my work PC, do the monitors invoke at work or stay locked and inactive?
In other words, when I working from home on my work pc, do others standing near my pc can see what I'm doing?
No, RDP takes over the console of the computer.
They however will be able to see on your monitor that You are logged in remotely to that specific computer.
They will see this for example:
http://msblog.blob.core.windows.net/wordpress/2010/11/17a043334c6bd9a1d37194f78df0af21.png
I need to understand a fundamental concept about terminal multiplexers yet I can't seem to find the answer.
As I understand these programs need to be installed on server but not necessarily on clients. It's not a problem with gnu-screen as it is already installed on most systems but it's not the case for tmux and byobu. The problem is that I don't have permission to install software on the server. Is there a way I can run byobu from my client to show statistics about the server I connect?
Also what exactly is the effect of 'byobu-enable' option?
I think there is a misunderstanding here. When you connect to the server and run a command (byobu in this case), you are running the command on the server. Statistics reported are for the server. It's possible to open a byobu session on your own desktop of course, but if you're ssh'd into a machine, you're very likely to be executing commands on that machine.
byobu-enable sets byobu to launch automatically when you open a terminal. I don't do this since you can have confusion if you have byobu running locally and on the remote end you have connected to, which causes problems when you try to interact with byobu itself.
I have written an application using ALSA (snd_pcm_open, snd_pcm_readi, etc). The application works perfect locally on my machine. However, when I SSH to another machine and run it through the SSH connection, all calls to snd_pcm_open fails with a message "Device does not exist" or similar. The remote machine has a soundcard just as my local machine has.
What could be the problem here?
Thanks!
EDIT: If I run the application using the console on the remote computer (walk to the computer, login, run the application), the application runs fine.
The problem might be with /dev/snd/* access rights.
Be sure the user is in the audio group.
In my case, I had to do adduser $USER audio, disconnect and then reconnect.
Just to check for the obvious: Are the drivers for the sound card on the remote machine loaded and working correctly? Check /proc/asound/cards and see so that the card is listed.
Just to confirm...you have the application installed on the remote machine and the remote machine has otherwise working aplay etc? The remote machine must be set up so that if you were to login from the console and run the application, it would work
If this is the case then check your environment variables as sometimes they can be subtly different.
Found the reason. Turns out /dev/audio and the devices below /dev/snd/ where all owned by the user logged in on the remote computer, and readable/writable by no one else. For testing I applied chmod 777 /dev/audio /dev/snd/* and it started working.
Anyone know how I can apply a bit more generous permissions to the audio devices for the remote computer (which will last after a reboot)?
We are developing an application in VB.NET that will need to accomodate remote users logging onto a Microsoft Terminal Server using RDP through the MSTSC.exe client.
Is it possible to offer an 'Upload' button which will allow the remote user to pick a file from his/her local hard drive and upload to the server ?
In the Windows Remote Desktop client, each user will have to enable an option. Under Local Resources, press More.... Here you can select the local drives you want the Terminal Server to see. The drives will come up as a network drive on the Terminal Server.
I don't know if you need to set up anything on the Terminal Server. You may need to open additional ports on the firewall.
I want to be able to access some device specific data while running an application on a remote machine. The problem is that if the RDP window is minimized this data is not available. One solution I'm examining is writing my own RDP client so that the server machine always thinks that it has an active display (even when the client machine is locked).
Does anyone know of a reference on how to develop an RDP client (preferably in .NET)?
Check out Terminals at Codeplex. Open source multiple RDP client; browse the code for some hints.