![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
chickenEver since our Solaris sysadmins started using a commercial version of SSH, we have been unable to SCP files from our OS X (Panther) machines to the Solaris machine, and have had to go the other direction:
This is fine, I can live with it. People say there's no way around this annoying difference between commercial and open source SSH.
The problem is that today, even going in that direction stopped working. (It has worked for months, years even).
Now I get this error (when executing the command shown above) --
Does anyone know why this is suddenly happening? Our Solaris sysadmins have not announced any sudden Solaris updates, and there hasn't been an OS X Panther update in a while either. (Of course, sometimes they do forget to tell us things.)
solaris machine > scp me@osx.machine.edu:Desktop/foo .
This is fine, I can live with it. People say there's no way around this annoying difference between commercial and open source SSH.
The problem is that today, even going in that direction stopped working. (It has worked for months, years even).
Now I get this error (when executing the command shown above) --
warning: Connecting to osx.machine.edu failed: Connection Refused scp: warning: child process (/opt/local/bin/ssh2) exited with code 2.
Does anyone know why this is suddenly happening? Our Solaris sysadmins have not announced any sudden Solaris updates, and there hasn't been an OS X Panther update in a while either. (Of course, sometimes they do forget to tell us things.)
