Re: WAN speed issue

From: etarhan (engin_tarhan_at_hotmail.com)
Date: 01/18/05 

Date: Tue, 18 Jan 2005 22:13:23 +0200

The first that can be said is that your IT person is right. In a LAN
environment, bits and bytes move at a speed of 10, 100 or possibly 1000
megabits per second. Żn a wan, the speed is principally limited by your
connection speed, which can be anything between 256 kilobits to 2 megabits,
possibly 4.

Therefore you are doomed to slowdown when connected through WAN.

Second thing that can be said is that did you separate your database into
front- and back-ends? If not, then you should do it immediately. Having only
data moving on the wires is really much much better than starting a remotely
located program and forcing everything including the form and query data to
go back and forth between two computers is simply a waste of bandwidth. This
is true even on a LAN. Separation of two ends is extremely easy, as there is
a wizard in Access to do this.

The third possibility to speed up things is to use a terminal server on the
main office and have the users to log on to it to run the program. This way,
program is running on the main computer and only the really necessary
thižngs are moving on the byte. Still, you have to separate database into a
front- and a back-end.

Good luck,

Engin

"Jeff" <Jeff@discussions.microsoft.com> wrote in message
news:4099D4F5-4661-4FCA-B867-41DC92CD2B45@microsoft.com...
> Hello,
>
> I have an Access Aplication that I designed & it currently resides on a
> Server here in our office & has other offices from different locations
> accessing it via a WAN.
>
> The problem is the speed. From the other locations the speed is VERY VERY
> slow to the point of making it unusable.
>
> I am unfortunatly not a Networking person. So I contacted someone from IT
> in this office & he said...
>
> "The network response is the same as its being since its been install.
> Unitization stats for both site WAN circuits are fine. The application is
> more likely design for a LAN environment and not via WAN which means
> you are going to have to look into the application design base on bytes or
> packet types. In addition,
> to re-sync the database."
>
> Is their anyone who could give me any feedback on possible ways, Access
> changes, (if any) to help speed up the database.
>
> Any help would be greatly appreciated.
>
> Thank you,
> Jeff
>

Relevant Pages

  • We have lots of users with SonicWalls for VPN connectivity in to FW-1, possible major security hole
    ... With default rule disabled: Disable default Src: LAN Dst: ALL ... The firewall WAN address is 24.184.168.52 ... A NT server on the internal LAN is 192.168.1.22 ... why is my internal server responding to this packet as a "Destination ...
    (Incidents)
  • Re: SBS 2003 - dual nics connectivity problem
    ... sbs 2003 servers, both with a nic for wan and a nic for lan. ... The problem is that after a day or so of running with both nics ...
    (microsoft.public.windows.server.sbs)
  • Windows XP Service Pack 2
    ... WAN 9000 times. ... and have noticed that in my environment, Windows 2000 AD 2000 that many GPO ... settings made have no effect. ... environment, and protecting the users from themselves, as well as helping me ...
    (microsoft.public.windowsxp.security_admin)
  • Re: SBS 2003 - dual nics connectivity problem
    ... Paul Barker typed: ... both with a nic for wan and a nic for lan. ... I've tried different nics, ...
    (microsoft.public.windows.server.sbs)
  • Re: Special configuration of DHCP, NAT
    ... DSL modem and NAT's the LAN. ... scrub in on $WAN all ... pass out on $WAN proto tcp from any to any modulate state flags S/SA ... pass in on $WAN inet proto icmp from any to any icmp-type $icmp_types keep state ...
    (comp.unix.bsd.openbsd.misc)