Does any body know of a free remote desktop utility for a business that supports Windows 2000 and is currently working? We did have LogMeIn installed as we are still central subscribers but we ended up with an issue yesterday where it was unreachable. I tried disabling LogMeIn and re-enabling but now LogMeIn will not come back online. It's experiencing an issue with an SSL cert and not connecting to the Web Gateway for LogMeIn. This is usually resolved by making sure the date and time are correct which they are already. I called LogMeIn and they advised me that Windows 2000 is no longer supported by LogMeIn and this could be why we are experiencing this issue. I tried setting up RDP but we decided It needs to be a web remote utility as we are planning on moving it off our main network for PCI compliance reasons since it would cost our company too much money to upgrade the software for our marquee and reader board.

Alexander.Hovis wrote: Marat (Remote Utilities) wrote: We had one customer, who tried previous versions up to 5.1 with Windows 2000 when they had the same error, and it still didn't work out. I'm assuming this is ok to try and install an older version if i can find one? Will this violate anything?

Learn more about which operating systems are supported for which TeamViewer versions and get further insights about the different operating systems to check, which TeamViewer version is the best fit for your personal setup. TeamViewer is an app that allows you to remotely connect to multiple workstations. Free TeamViewer Windows 98/Me/NT/2000/XP/2003/Vista/Server 2008/7/8.

Hello Alexander, This won't violate anything. It's only that we, understandably, no longer support such versions or fix bugs in them.

I'll send the links to you via PM so that not to misguide people who could unknowingly download an older version from this public thread. Scott Alan Miller wrote: Alexander.Hovis wrote: Scott Alan Miller wrote: LogMeIn is no longer free.

Your account was probably disabled. We have LogMeIn central so we are not affected by this 'yet'. All of our other PC's that are using LogMeIn are working fine because they have been upgraded to a newer OS version that is supported by LogMeIn.You'll be affected by the pricing change immediately, though. We are aware and are currently looking into alternatives for the future.

But at this time we are continuing to use LogMeIn until we find something. VWernicke wrote: Huh. That's strange. Worked fine for me. Perhaps google could shed some light on the issue? Everything that I've found from Google points to the same thing mentioned by Microsoft.

' This behavior can occur because a function that is contained in a dynamic-link library (.dll) file, which is typically meant for use in Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me), attempts to call the SetHandleContext() application programming interface (API). However, this API does not exist in the Windows 2000 version of the Kernel32.dll file, which results in the error that is described in the Symptoms section of this article. ' Here is Microsoft's workaround but it doesn't like a stable thing to do unless I'm misunderstanding what they are telling me to do. ' To work around this behavior, examine your home drive (the drive letter of your local workstation) and the entries in the path variable until you locate the incorrect versions of the.dll files. Then, delete the problem.dll files. If the.dll files are found in your home drive, you can disconnect the drive as a temporary workaround.' VWernicke wrote: Ok.

So from my research I'm finding this is a bug in the program. I'm apparently using an older version of Remote Utilites on my box. Apparently the new version is misinterpreting the operating system and thinks you have XP. Hopefully this will be fixed soon for you.

Because I see no way to download older versions on their site. We had one customer, who tried previous versions up to 5.1 with Windows 2000 when they had the same error, and it still didn't work out. Anyway, I'll check this out with our developers again to see if something can be done about this. I reckon there are still a lot of Windows 2000 installations. Alexander.Hovis wrote: Marat (Remote Utilities) wrote: We had one customer, who tried previous versions up to 5.1 with Windows 2000 when they had the same error, and it still didn't work out. I'm assuming this is ok to try and install an older version if i can find one?