Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Whenever I attempt a long command (such as listing a directory with a few hundred files) or use a text-based GUI (like Yast from command line) while using PuTTY, I receive the error "Incorrect MAC received on packet". I have reason to believe that this is NOT the bug that effects SSH server versions 3.x, as I have version 4.4p1. I have also tried playing with the setting in putty that corrects for that bug, but none of the settings fix it. Using different encryption methods in putty do not help at all either.
I have tried forcing yast to update both SSH and SSL, and I have also updated putty on my end, however the error still keeps happening, no matter where I access the server from. Anyone know how I can get rid of this? It really gets in the way..
I am running OpenSuse 10.2.
Last edited by jaguar11735; 03-27-2007 at 11:11 PM.
I am running SSH 4.4p1, as I stated in my first post. The link you gave me refers 3.4. Both SSH and SSL have been forcefully updated in yast, even though they were both listed as the newest version.
I have recently been getting the same error when I try to run X11 applications (though my setup has been running okay for months).
The PuTTY FAQ and a Google search turned up three possible causes:
- Old SSH 2 servers distributed by ssh.com calculated the MAC
incorrectly. However, PUTTY version 0.52 or better will detect the
buggy servers and compensate. I've been running version 0.58. Also
I'm using the OpenSSH server, not one from ssh.com.
- OpenSSH built against an incorrect version of OpenSSL. The specific
versions of OpenSSH are 3.1p1 and 3.4p1. However, I am running version
4.3p2.
- Buggy firmware in certain Linksys routers. We are running only
Cisco routers, and their configuration has not changed, and connections to a Linux box on the same LAN segment (no routers) also failed.
Some things I have tried:
- Upgrading to PuTTY 0.60. No change.
- Other ciphers. No change.
- Other MACs. No change.
- Other X clients. I have been testing mostly with xdvi, which usually dies on the first page. xclock seems to work okay. GNU emacs fails pretty
quickly. MATLAB fails every time, when it tries to display its splash
screen.
- I used PuTTY to access the same X clients on different hosts.
Failures were similar. Connections to one host seemed more reliable
than to the other two (e.g. xdvi died on the 4th or 5th page, instead
of almost always on the first page). Connections to a host on the same
LAN segment were not more reliable.
- I used "cygcheck ./putty.exe" to check DLLs used. None of them had been changed recently (e.g. by the company's patch/upgrade service).
- I used ssh on a Linux box to access the same X clients on several
hosts. That worked fine.
- I used Cygwin rxvt/ssh to access the same X clients on several
hosts. That worked fine.
As a workaround I have been using Cygwin rxvt/ssh, e.g. a shortcut with this "target":
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.