QuickBooks client over VPN


M

Mark St Laurent

We have set up a gateway to gateway VPN between QuickBooks Enterprise server
site and wish to connect remote client at another site. Standard windows
file transfer averages 30k/sec. Fractional T1 @ 256K on server side standard
ADSL on the client side. Opening quick books client very slow. I am not that
familiar with bandwidth requirements for this app and realize that an RDP or
term services session may be faster but is this really necessary. Can it not
be accomplished over VPN, as it would on the local LAN and what would be
reasonable in terms of bandwidth requirements. I know this is more of a
networking question. I am hoping that others in this group who have also
expanded their businesses and use QuickBooks could shed some light on this
issue.
 
Ad

Advertisements

M

Mike Schumann

Terminal Server is the ONLY way to go. If you have a normal QBooks client
connection over a VPN link, and the link goes down, you have a very good
chance that your QBooks database will be corrupted. Terminal Server solves
this problem.

There is nothing you can do to make performance on this type of a connection
acceptable. With large QBooks files (150+MBytes), performance becomes a big
issue even on 10MBPS LANs.

Mike Schumann
 
J

JerryMouse

Mark said:
We have set up a gateway to gateway VPN between QuickBooks Enterprise
server site and wish to connect remote client at another site.
Standard windows file transfer averages 30k/sec. Fractional T1 @ 256K
on server side standard ADSL on the client side. Opening quick books
client very slow. I am not that familiar with bandwidth requirements
for this app and realize that an RDP or term services session may be
faster but is this really necessary. Can it not be accomplished over
VPN, as it would on the local LAN and what would be reasonable in
terms of bandwidth requirements. I know this is more of a networking
question. I am hoping that others in this group who have also
expanded their businesses and use QuickBooks could shed some light on
this issue.
An alternative solution, perhaps, is remote access. That way nothing but the
screen and keyboard have to move over the network (and the mouse).
 
G

Gary

JerryMouse said:
An alternative solution, perhaps, is remote access. That way nothing but the
screen and keyboard have to move over the network (and the mouse).
I recently switched a client over to terminal services from PCAnywhere, and
they are very happy with the result. Unless the location I was helping
didn't have a Windows Server, I wouldn't do it any other way.

Gary
 
M

Mike Schumann

If someone can't afford Windows Server, a poor man's approach is to set up a
computer running Windows XP Pro using the built in Remote Access capability.
This is identical to running a Terminal Server, except that a user can't be
logged on to the computer's console if someone is using the machine remotely
(and vis versa).

Mike Schumann
(e-mail address removed)
 
M

Mark St Laurent

Thanks for the info. I know I used quite a few acronyms in the original post
but I did indicate that I was aware this could be accomplished using
RDP("Windows XP Pro using the built in Remote Access capability") or,
TermServices depending on the QB server level. It seems that 2005 directly
supports and 2003 requires a couple of work arounds. My question was with
using Direct File access through VPN. The consensus seems to indicate that
the database requirements for bandwidth preclude this as an option. We will
probably be going with either RDP or VNC over VPN. If the previous posts
regarding bandwidth requirements are inaccurate which I doubt, possably
someone could post what reasonable requirements are necessary for the direct
access option. Your, previous post indicated that you have experienced
problems with 10 MBPS Lan which is infinitely faster than any remote
connection we could or would afford.
Again thanks for your time I have no experience with QB and the input from
this forum has saved me from recommending connection upgrades that would be
marginal at best and possably result in a corrupted database.
 
Ad

Advertisements

W

*Watt

Mark,

We have use a VPN, and the bandwidth is nowhere near what is necessary to
handle an app like Quickbooks. (Although Quickbooks is not our only
offender.)

We have successfully used QB with : Terninal Server on Win2000 and Win2003
servers, the XP remote access, and PC Anywhere.

The terminal server approach is by far the fastest, cleanest, most secure,
and most reliable.

You might check out the previous threads on installation and configuration
of QB on the terminal server.

*Watt
 
Z

Z Man

*Watt said:
Mark,

We have use a VPN, and the bandwidth is nowhere near what is necessary to
handle an app like Quickbooks. (Although Quickbooks is not our only
offender.)

We have successfully used QB with : Terninal Server on Win2000 and Win2003
servers, the XP remote access, and PC Anywhere.

The terminal server approach is by far the fastest, cleanest, most secure,
and most reliable.

You might check out the previous threads on installation and configuration
of QB on the terminal server.
QuickBooks versions prior to Enterprise don't support Terminal Services.
Some users have gotten it to work, but if you fry your data, don't complain
to Intuit. Be careful out there...
 
M

Mike Schumann

Yes, QBooks Pro is NOT officially supported on Terminal Server. However, if
you understand how Terminal Server works, and you have the 5 user pack (if
you are interested in having more than one simultaneous QBooks session on
the Terminal Server), you shouldn't have any problem making this work.

If you do run into problems, QBooks won't run. I've never heard of anyone
"frying" their data while using Terminal Server.

Mike Schumann
 
W

*Watt

Z Man,

You a shill for Intuit ?

The question related to shedding light on how people are remotely accessing
the QB over a VPN.

As someone who has used QB on Terminal Services, used QB over PC Anywhere,
used QB over a WinXP RDP connection, AND discussed these with Intuit tech
support......I think I can throw in my two cents !

The enterprise version is definitely NOT needed. I have been using the QB
Pro 5 user since 2001 and have zero problems.

Now we might discuss the need to have suitable backups for your data due to
drive failure, fire, tsunami, user idiocy, etc.....All of these are more
likely than data being "fried" from terminal services use.

Cheers, and I won't complain,

*Watt

"Lets shed light, not heat...."
 
Ad

Advertisements

sdd

Joined
May 14, 2012
Messages
1
Reaction score
0
Options....

RE just having two-user access, and having explored all sorts of options and comparing:

VPN has been buggy and problematic re folder sharing, router and port settings, IP address issues - but this works for some;

Local cloud hosting for QB seems to require Win 2008 Terminal Server (expensive software and a dedicated machine), and maybe needs Enterprise version of QB - from what I've read. Tech issues? Have to pay for local support and maybe experience downtime...;

Cloud hosting takes the software and data off your computer or LAN giving you access anywhere you have an internet connection, permits ANY two users at a time to access and use the company files, and permits, depending on the provider, use of any printers. Static Ip may have to be purchased (a few dollars a month) and you are reliant on the internet connection being up. Need more than two users? Purchase another user license and add a subscription and it’s up and running. (Do a google search of "Quickbooks cloud services" to compare);

And then there is what might be the best (WAN-type) solution for two users: RDP through a second machine on your LAN. The remote user uses their computer to access through MS's in-built remote desktop user software the second machine on your LAN running the 2nd QB license, which then can access the company files on that computer or another mapped on the network. No heavy transfer of date - just mouse clicks and keyboard strokes. Downside? Possibly difficulties or the impossibility of printing anywhere but at the LAN site...And you are of course reliant on the internet connections being up, as well as the local router/LAN and computer hosting the company files being up to use this approach.
- SDD/Beaufort, SC
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top