Using plink and putty on Windows Server 2008 x64

I am trying to get Putty and plink operable on an x64 bit server with Windows 2008.  This will connect to a vendor via the web.  This same process with the same software works on Windows 2003 server and XP.  I am assuminng it to be an issue with either a:  windows 2008 or b:  the fact that the server is x64 running Windows 2008.  Any insight?
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

ee_autoConnect With a Mentor Commented:
Question PAQ'd, 500 points not refunded, and stored in the solution database.
What error are you getting?
kotechnologiesAuthor Commented:
That probably would have helped.

Network Error:  Software caused connection abort.  I get this about 5 minutes after launching the application.
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

So it does work for a period of time and then dies with this error or it just sits for a period of time then you get this error?
Can you grab the PuTTY event log?  Right-click the title bar and choose 'event log'.

kotechnologiesAuthor Commented:
It never seems to connect, just sits there for 5 minutes and then throws the error.  Below is the event log.

2010-03-23 13:25:11      Looking up host ""
2010-03-23 13:25:11      Connecting to port 22
2010-03-23 13:25:11      Server version: SSH-1.99-OpenSSH_3.9
2010-03-23 13:25:11      We claim version: SSH-2.0-PuTTY_Release_0.60
2010-03-23 13:25:11      Using SSH protocol version 2
2010-03-23 13:33:42      Network error: Software caused connection abort
I was able to launch PuTTY on one of my servers running Server 2k8 x64 and connect to my router and firewall without an issue.

This is from the PuTTY user manual (

10.11 "Network error: Software caused connection abort"

In modern versions of PuTTY, you should not see this error.

Windows's documentation about this error condition is not very good, but as far as we can tell, this error occurs when PuTTY is listening on a port, another program makes a connection to that port, but closes the connection so fast that PuTTY has no time to answer it.

PuTTY only ever listens on a port when it is doing local-to-remote port forwarding (see section 3.5); and if an incoming connection on that port receives this error, PuTTY should simply close the connection and continue without error.

If you see this error in PuTTY 0.53 or above, we would welcome a report of the circumstances.

Not very helpful I know, sorry.  
All Courses

From novice to tech pro — start learning today.