I have estimated 44 GB of data from my web server. I want to transfer it to another server with less time. I am using Putty to transfer file. is there any way to achieve this? I don't know which commands to use but some blogs said to use rsync or scp to transfer these files. your help is greatly appreciated. I've tried scp from local to server but I what I need is from server to server.

I used puttygen to generate both my public and private key files (ssh2, 2048 bit). I have set up the settings in putty correctly and it is using the correct private key file. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys I have tried using chmod on .ssh to 700 and on authorized_keys to 400. That did not do anything. Does anyone have any recommendations? edit: here's an ls -ldZ of my .ssh folder and authorized_keys file drwx------ root root ? /root/.ssh -rw------- root root ? /root/.ssh/authorized_keys

I'm running Ubuntu 18.04 on Windows Powershell on Windows 10. I installed XMing and PuTTY and configured them so that X11 forwarding is turned on. After all this, and installing x11-apps and running xeyes, it tells me "Error: Can't open display: 0.0". I tried changing the DISPLAY to 0 and 'localhost:0.0, but nothing. I installed several packages, many of which will probably end of being unnecessary. I've tried just about everything in the responses both of these questions: https://unix.stackexchange.com/questions/67111/x-cant-open-display-0-while-display-variable-is-correct?newreg=2fece9554c164efd90a2726a9c526fb5 https://unix.stackexchange.com/questions/1596/can-i-launch-a-graphical-program-on-another-users-desktop-as-root , but who | awk -v user="$target_user" '$1 == user && $2 ~ "^:" {print $2}' returns nothing and xhost + gives me the same display error. I tried various configuration files such as xauth, /etc/X11/Xwrapper.config. It might be important to note that xinit returns the fatal error no screens found and /var/log/Xorg.0.log shows many errors dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory No devices detected. I need to be able to use image tools like ds9 for my research and have been unable to do so, so any help would be very much appreciated.

I am: - Running a program on a Ubuntu 20.04 AWS instance - Using SSH & X11 forwarding in PuTTY, with the VcXsrv X-server, to run program GUIs on my local Windows 11 machine **The GUIs of test programs like xclock/xeyes successfully run on my local machine**. The issue arises when trying to run the GUI of interest (NVIDIA's Isaac Gym). I run a test script that activates the GUI. It opens up for a second, closes, then I get the following error:

X Error of failed request:  BadIDChoice (invalid resource ID chosen for this connection)
  Major opcode of failed request:  148 ()
  Minor opcode of failed request:  3
  Resource id in failed request:  0x200002
  Serial number of failed request:  26
  Current serial number in output stream:  18

**The Opcodes** As per the Xorg opcode page (thanks Kenster): - Major opcode: **PRESENT** extension (apparently called for things related to "frame representation timing" - screen refreshing, tear-free rendering, etc.) - Minor opcode: **X_PresentSelectInput** request (apparently "selects a set of Present events to be delivered for the specified window on the X server specified by display" - source ) It sounds like it's just an initial request that's sent when setting up/running PRESENT-related things. How do I fix this? Some help would be greatly appreciated. ---------- More System Info --------- **Server** As per this well-known post for setting up X11 forwarding: - /etc/ssh/sshd_config looks as follows:

#AllowAgentForwarding yes   # unspecified
  X11Forwarding yes           # activated
  #X11DisplayOffset 10        # unspecified
  #X11UseLocalhost yes        # unspecified

- /etc/ssh/ssh_config looks as follows:

#   FowardX11 yes           # unspecified
  #   ForwardX11Trusted yes   # unspecified

- xauth is installed

$ xauth -V
  1.1

- The server's DISPLAY variable seems to be set correctly

$ env | grep DISPLAY
  DISPLAY=localhost:10.0

- The XAUTHORITY variable seems empty

$ env | grep XAUTHORITY
  $

**PuTTY** - Obviously "Enable X11 forwarding" box is checked - "X display location" is empty **X Server (VcXsrv)** Using XLaunch: - "Display number" is -1 (to let vcxsrv automatically choose one) - "Disable access control" box is unchecked ---------- **What I've Tried** --------------------------- The following all yield the BadIDChoice error mentioned up top: - (After reading David G.'s answer) Enabled ForwardX11Trusted in /etc/ssh/ssh_config, together with "Disable access control" in XLaunch - Tried once with X11UseLocalhost no in /etc/ssh/sshd_config - Tried once with #X11UseLocalhost yes (commented out) - Changing VcXsrv "Display number" to 0 - Changing PuTTY "X display location" to localhost:0 Other Errors: - Changing VcXsrv "Display number" to 1 or 10 --> yields (4 times for some reason):

PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused

----------

I'm building a simple shell server using raw Python sockets (not using telnetlib). The client connects using PuTTY with the Telnet connection type. The server displays a basic prompt like: [user@hostname:~]# --- ## The issue: ## When I type a command (for example, wh0ami) and press Ctrl+C, the entire line is wiped and only a fresh prompt appears: [user@hostname:~]# wh0ami ← typed input ^C ← pressed Ctrl+C [user@hostname:~]# ← result: input line cleared --- ## What I expect: ## In typical terminal behavior (like Bash or real Telnet servers), I would expect to see something like: [user@hostname:~]# wh0ami^C [user@hostname:~]# But in my case, the previously typed input disappears completely after pressing Ctrl+C. --- ## Notes: ## - I’m not using raw terminal mode — and I’m unable to use it for my use case. --- ## Question: ## Why does Ctrl+C cause the current input line to be cleared in this setup? Is this normal Telnet behavior, or am I missing something related to how the input buffer or terminal display should be handled? What's the solution to this? Thanks in advance. ---

How can I copy content of large unix file (putty tool) to notepad?

I'm using an old redhat virtual machine with VMware Player. I used to be able to connect it using PuTTY, but for some reason now I can't. Here's what I do: 1. I use ifconfig to get the IP address 2. I ping the IP address and get a response just to make sure 3. I check that iptables accepts TCP connections through port 22 4. I use PuTTY to connect to the IP address I got from step 2 It used to work, now it doesn't. I didn't change anything but everytime I reset the iptables rules gets deleted and I have to redo it, but it still doesn't work. I get "connection timed out" error. Any ideas?

I'm trying to use Byobu on a Linux server via SSH from Windows. I've tried with MobaXterm and putty, but some of the F key combinations simply don't work. In MobaXterm there is even a dedicated Byobu terminal type setting, but the F5-F8 keys ignore the key combinations with Ctrl. I've listed the codes sent to the terminal with cat -v. The code for example **F6** is ^[[17~, but for **Ctrl+F6**, it sends the exact **same** code. Is there any terminal client for Windows that can send distinct codes for all F-keys with all modifiers (Ctrl, Alt, Shift)?

I have a Linux server running xtightvnc on Ubuntu 18.04. Using my laptop, I am able to establish an SSH tunnel connection using PuTTY on Windows and establish a connection to vnc through localhost:5901. This works without issue. On the same laptop, if I boot into Debian 9 to try to replicate the connection using: ssh -L 5901:127.0.0.1:5901 -N -f -l username server_ip_address I receive an error: bind: Cannot assign requested address Running the same command with the verbose option: ssh - v -L 5901:127.0.0.1:5901 -N -f -l username server_ip_address Gives the following output (I have shortened the output): debug1: Local connections to LOCALHOST:5901 forwarded to remote address 127.0.0.1:5901 debug1: Local forwarding listening on 127.0.0.1 port 5901. bind: Address already in use debug1: Local forwarding listening on ::1 port 5901. bind: Cannot assign requested address channel_setup_fwd_listener_tcpip: cannot listen to port: 5901 Could not request local forwarding. debug1: Requesting no-more-sessions@openssh.com debug1: forking to background debug1: Entering interactive session. debug1: pledge: network I'm not sure what this means, but it sounds as though the previous connection I opened under Windows is still active somehow? I also tried to tunnel on Debian using PuTTY and the same settings I have under Windows. It seems I am able to connect using the same settings, and I can connect to vnc, though this wasn't working earlier. (Perhaps there is some sort of cool down setting I am not aware of after a connection has been closed out that still keeps the connection open/address assigned?) edit: This is the error I receive using PuTTY on Linux if the address hasn't reset yet: The main issue here is perhaps that when I close PuTTY, the connection is still active (I just tested this, as I was still able to connect to vnc using localhost:5901). I exit my PuTTY sessions using exit. The out put of netstat -tulpn might also be relevant: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:6342 0.0.0.0:* LIS TEN 21618/megasync tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN 21527/Xtightvnc tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 21527/Xtightvnc tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 796/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 874/sshd tcp6 0 0 :::22 :::* LISTEN 874/sshd udp 33024 0 127.0.0.53:53 0.0.0.0:* 796/systemd-resolve Update: It seems that everything is functional, but that there is a cool down period after I close my connection with PuTTY before I can establish another connection from a different instance of Windows or Linux. If anybody knows a way to speed up the process, I would be grateful to hear the solution. Update 2: Under linux it seems I can effectively kill the ssh tunnel, e.g. by using pkill ssh (to kill all current ssh connections). It therefore seems that PuTTY appears to have the tendency to not properly close the tunnel to the server upon logout.

I'm using Kitty (putty clone) and Keepass agent (similar to pagent). Keepass agent contains 5 ssh keys. This setup works fine with all linux boxes I've encountered so far, connection to our new RHEL7 linux box fails with type 2 (protocol error): "Too many authentication failures for ..." I added MaxAuthTries 6 to /etc/ssh/sshd_config and did a systemctl restart sshd.service but the error remains.

I have built a new Ubuntu server in AWS. Now for some reason my private key that works on other Ubuntu servers is not working here. The error in auth.log is:

userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]

This is an issue only with PuTTY; if I try logging in via a Linux workstation, there are no issues at all with any machine. The difference I see is the new server is Ubuntu 22.04.1 LTS running “OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022”. The working (old) server is Ubuntu 20.04.4 LTS (Focal Fossa) running “OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020”. Has something changed in this version of OpenSSH?  How do I get PuTTY working again?

When using a VPN to connect to my Rocky Linux 9.3 server running on a virtual machine, my connection is randomly disconnected. After disconnection, I cannot reconnect for about one or two minutes, and the connection is refused. I have tried connecting from different computers on different networks, but the same error occurs. Only connections within the main network work (WinSCP from another Windows server to the Rocky Linux server remains stable). I am using pfSense as a firewall. I have already set the keep-alive connection parameters, but there is nothing suspicious in the server logs. I'm kind of running in the dark here. Some of the logs:

Knocking FTP port.
. 2024-08-21 11:35:02.610 FTP port did not open.
* 2024-08-21 11:35:02.693 (EFatal) Network error: Connection to "192.168.178.205" refused.
. 2024-08-21 11:35:06.189 Looking up host "192.168.178.205" for SSH connection
. 2024-08-21 11:35:06.189 Connecting to 192.168.178.205 port 22
. 2024-08-21 11:35:08.287 Failed to connect to 192.168.178.205: Network error: Connection refused
. 2024-08-21 11:35:08.287 Knocking FTP port.
. 2024-08-21 11:35:10.302 FTP port did not open.
* 2024-08-21 11:35:10.368 (EFatal) Network error: Connection to "192.168.178.205" refused.

/var/log/secure:

Aug 21 14:49:01 localhost sshd: Connection from 172.16.17.4 port 49860 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:49:05 localhost sshd: Accepted password for woshi from 172.16.17.4 port 49860 ssh2
Aug 21 14:49:05 localhost sshd: Starting session: subsystem 'sftp' for woshi from 172.16.17.4 port 49860 id 0
Aug 21 14:49:30 localhost sshd: Connection from 172.16.17.4 port 49945 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:49:58 localhost sshd: Accepted password for woshi from 172.16.17.4 port 49945 ssh2
Aug 21 14:49:58 localhost sshd: Starting session: shell on pts/1 for woshi from 172.16.17.4 port 49945 id 0
Aug 21 14:52:16 localhost sshd: Connection from 172.16.17.4 port 50512 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:52:17 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50512 ssh2
Aug 21 14:52:17 localhost sshd: Starting session: subsystem 'sftp' for woshi from 172.16.17.4 port 50512 id 0
Aug 21 14:53:23 localhost sshd: Connection from 172.16.17.4 port 50739 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:53:23 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50739 ssh2
Aug 21 14:53:24 localhost sshd: Starting session: shell for woshi from 172.16.17.4 port 50739 id 0
Aug 21 14:53:28 localhost sshd: Connection from 172.16.17.4 port 50757 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:53:32 localhost sshd: Failed none for woshi from 172.16.17.4 port 50757 ssh2
Aug 21 14:53:59 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50757 ssh2
Aug 21 14:54:00 localhost sshd: Starting session: shell on pts/0 for woshi from 172.16.17.4 port 50757 id 0
Aug 21 15:09:06 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 49860
Aug 21 15:11:30 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 49945
Aug 21 15:18:25 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50739
Aug 21 15:21:18 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50512
Aug 21 15:21:28 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50757

**UPDATE:** So my network is managed by pfSense. I am connecting to that network over OpenVPN. My Rocky Linux server (target server) is on VmWare virtual machine.

I created a Ubuntu 18.04.6 LTS VM on vSphere. Created a user, test. VM is a 1-year-old machine. Now when I am trying to log in ( through PuTTY), I can't. I checked the logs it says that the "account root has expired" (failed to change password) and the account test has expired (failed to change password) How can I log in to the VM?

I'm getting a "Display all possibilities? (y or n)" dialogue in a PuTTY Terminal connected to a Synology NAS. The Synology Support people are abdicating responsibility for this, so I'm wondering if someone can help to identify the source? I'm connecting with a PuTTY Terminal, using the Default Config: just login with user & password & wait...
...after a long wait (an hour, say) the "Display all possibilities" message appears. ps -ef suggested the Session is running a Bourne Shell ("sh") but $SHELL --version yields:
GNU bash, version 4.4.23(1)-release (x86_64-pc-linux-gnu) The reported OS is: Linux 4.4.302+ x86_64 There were no user-written scripts/processes running on the NAS. Pure Synology. During the wait, no input of any kind was made at the Terminal.
In that time, the NAS Filesystem was not accessed.
Neither was the Synology Console used (although it was open, displaying the Control Panel App). Is there some way my own Session can be issuing a Command without my knowledge?
(there was absolutely no spurious input - Tabs, or otherwise - after the login) Could some other Process be displaying the message on my Terminal? I'd be grateful for any ideas how I can get to the bottom of this and/or put a stop to it. Thanks in advance. **Screenshot 1, after login:** **Screenshot 2, after long wait:** **Screenshot 3, after entering "y":**

Oracle linux 7.9 Putty v0.83 on Windows-10 Some of the linux hosts in our fleet are showing the following errors when a user connects via putty (or mobaxterm): (from /var/log/messages)

Feb 21 16:06:04 xxxxxxxxx systemd: Started Session 287625 of user yyyyyy.
Feb 21 16:06:04 xxxxxxxxx systemd-logind: New session 287625 of user yyyyyy.
Feb 21 16:06:05 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StScrollBar' tried to allocate a size of -13.00 x 14.00
Feb 21 16:06:05 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StBoxLayout' tried to allocate a size of -13.00 x 1.00
Feb 21 16:06:05 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StScrollBar' tried to allocate a size of -13.00 x 14.00
Feb 21 16:06:05 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StBoxLayout' tried to allocate a size of -13.00 x 1.00
Feb 21 16:06:18 xxxxxxxxx systemd-logind: Removed session 287625.
Feb 21 16:06:19 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StScrollBar' tried to allocate a size of -13.00 x 14.00
Feb 21 16:06:19 xxxxxxxxx journal: clutter-actor.c:10069: Actor 'StBoxLayout' tried to allocate a size of -13.00 x 1.00

This does not happen on all our hosts. This does not happen on all our Oracle linux 7.9 hosts. When it does happen, ALL connections with putty/mobaxterm show the same results. Looking for an explanation as to why this would happen. Thanks.

I connect to a Slackware server. When a command is longer than the size of the putty window, the line continues in the same line, and the start of the command disappears as I continue adding to the same command, just putting a "<" at the beginning of the line. When I work on the Red Hat server, I can see the whole command because the console just adds lines as it needs. I don't know where I turn on word wrapping. Where can I set the Slackware server to wrap words as my Red Hat server does? P.S.: Excuse my English.

I've noticed one second delay before Midnight Commander or mcedit starts in Putty. It took me a while before I realized it is caused by X11 forwarding enabled. mc -X start immediately. Unfortunately starting any X11 application has same delay. Maybe I'm nitpicking but it drives me crazy. Especially because some users mentioned cause and solution for this: xming does not support X11 security, so Linux must wait for network timeout. It is on second for me, but 30 seconds for others according to some discussions. The solution is trusted X11 forwarding enabled by -Y commandline option for ssh. Unfortunately Putty doesn't have this option. Is there any other way to enable trusted forwarding on Putty ?

After upgrading a server from Oracle Linux 7 to Oracle Linux 8 via leapp, one of our users who will use X sessions for testing and DB management is getting a message when he logs in of "PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused" I didn't do anything with the X server, and he is the only person getting this message. Any ideas on where to start to get rid of this error?

I am trying to print two string separated by a TAB. I have tried: echo -e 'foo\tbar' printf '%s\t%s\n' foo bar Both of them print: foo bar Where the whitespace between the two is actually 5 spaces (as per selecting the output with mouse in Putty). I have also tried using CTRL+V and pressing TAB when typing the command, with the same result. What is the correct way to force tab being printed as tab, so I can select the output and copy it to somewhere else, with tabs? And the secondary question: why is bash expanding tabs into spaces? **Update**: Apparently, this is a problem of Putty: https://superuser.com/questions/656838/how-to-make-putty-display-tabs-within-a-file-instead-of-changing-them-to-spaces

I am renting a VPS running CentOS Stream 8, for which I set up SSH pubkey authentication for the user "foo". I access it via PuTTY on Windows. Recently I rented another VPS running Rocky Linux 9, and I set up sshd in an identical way, then copying the /home/foo/.ssh/authorized_keys file from the old VPS to the new one. In this way I had just to clone the PuTTY profile configuration, changing only the IP address from the old to the new one, and reusing PuTTY's PPK key. However, when I SSH to the new server via PuTTY, I get the error: Using username "foo". Authenticating with public key "foo@newvps.example.com" Server refused public-key signature despite accepting key! Using keyboard-interactive authentication. Password: and I have to enter "foo" user's password. However, I'd like to ditch password-based authentication, as in the old server. The private and public keys are the same on both ends. SELinux is not interfering here. Permissions of ~/.ssh and ~/.ssh/authorized_keys are correct. Note that SSHing in via pubkey from the new server to itself works perfectly. Clearly in this case it uses id_rsa, not PuTTY's PPK key. dmesg and /var/log/messages do not show anything useful. What could be the problem? Note: this is not a duplicate of https://unix.stackexchange.com/questions/282908/server-refused-public-key-signature-despite-accepting-key-putty , as none of the answers apply.