Local printing in QuickBooks 2006 through VPN Remote Access

Logmein Pro costs $70 (or less) per year and will give you that capability.

Gary

Pershaps you should look into these services again. I use LogMeIn at a cost of 59.00/Year. If I did not requre remote printing or the ability to transfer files the service is free.

I have also seen offers from GoToMyPC for 79.00/Year.

Just as a side bar. If Microsoft's built in solution works, why are there so many other vendors offering this functionality at a cost? What is wrong with this picture?

>

Don't know, but everything except QB works just as I expected with Remote Access through Windows XP Pro. Maybe not enough people know about XP's remote Access.

By the way, are you able to print checks (alignment, etc.) on your local printer through logmein.com?

Yes, no problems.

>

I use remote desktop with two different clients and have no problems printing locally. Perhaps it's just related to QB2006 as I'm using QB pro

2002 & 2004. Just like a stand up company that Intuit is to suggest the problem is with someone else's SW rather than their own.

AMAZING! Logmein works. After spending hours and hours trying to make QB in VPN to work, paying $70 per year is cheap. But it still boggles my mind why Logmein can do it and QB cannot. Oh well, for some things in life there are no answers. Thanks for steering me to Logmein, Allan.

Don't mention it. Besides LogMeIN working flawlessly the features included with the paid subscription are great. The service allows me to set up multiple workstations in my office or elsewhere and do a simple remote to them for free.

As a CPA it's great knowing that I have access to my office workstation from any client site that has broadband access (all do). Also being able to share any file(s) on my system with my clients puts an end to file size limitations inherent in e-mail file transfers.

I did notice that you posted your printing problem to a Microsoft newsgroup. I was wondering if the solution given there to map your printer to a local LPT port using a "net use" command would solve the problem?

>

When I have some time I am going to try that. But to do that, I am going to have to disconnect one of my printers from the server and hook it up to the workstation, etc., etc. Not a high priority right now.

You do not have to do that. The whole idea of mapping to an LPT port is so you do not have to physically move the printer. The Net Use command tells the operating system to treat the printer as if it were physically conected to one of your local LPT ports.

>

There is a documented bug with Microsoft's Terminal Services (the underlying engine with Remote Desktop) and using print servers. Something about not regognizing any device that did not start with LPT or USB. We had the same issue with our setup last year. While the precise details and unfortunately the knowledge base ID escape me at present, it was fixed with a simple registry entry on the clients. That said, our Quickbooks 2005 Pro still does not recognize ALL printers while in remote access, but it recognizes most of them - and most importantly, my home printer when I'm at home. You might try searching the Microsoft knowledge base for something like "terminal services print server". If you are not using print servers, this might not apply to your situation. But it sure sounds like it.

QuickBooks does not properly work with printers having long names. When you add a network printer, the addition of all the extra information in the name will often make it too long and you need to rename it to something more succinct. The problem is confusing because QuickBooks will appear to see the printer, and print to it, but you will never see output.

I also use GoToMyPC with outstanding results. Formerly used Personable.com to host and it was a disaster.

Craig