Re: FileSharing over WAN
- From: "Jabez Gan [MVP]" <mingteikg@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 1 Apr 2006 13:20:04 +0800
You're welcome.
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
"TPSchaefer" <TPSchaefer@xxxxxxxxxxx> wrote in message
news:uyMojTMVGHA.4436@xxxxxxxxxxxxxxxxxxxxxxx
thanks
"Jabez Gan [MVP]" <mingteikg@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eLUAnKIVGHA.328@xxxxxxxxxxxxxxxxxxxxxxx
If you have tons of files to transfer and share, it's best to acquire
Server to do the job. WiNXP doesn't have all these compression/file
sharing bandwidth savings natively, so files can't be speed up
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
"TPSchaefer" <TPSchaefer@xxxxxxxxxxx> wrote in message
news:OvI11c$UGHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
Thank you for the info.
Unfortunately, we only have servers at the main hub. Non of the
branches have servers. Is there any other way to speed filesharing up?
Thanks
"Jabez Gan [MVP]" <mingteikg@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OesoOG7UGHA.5148@xxxxxxxxxxxxxxxxxxxxxxx
Hi Terry,
In your scenario, it's best that you implement R2's DFS. R2's DFS has
better bandwidth throttling and replication will only replicate the
bits and bytes which got changed (from the original file).
What I would suggest is that you can have R2 implemented on all the
hubs and have replication set for the folders users need access to
frequently. Then, users can grab the files from the nearest hub (or if
the nearest hub is down, it will auto connects to other hubs which has
the file).
For more info, please see:
http://www.microsoft.com/windowsserver2003/R2/branchoffice/default.mspx
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
"TPSchaefer" <TPSchaefer@xxxxxxxxxxx> wrote in message
news:%23ozv%23eqUGHA.3192@xxxxxxxxxxxxxxxxxxxxxxx
Anyone / All
I have a MPLS WAN system that is killing our productivity. Since the
install of the new WAN links, filesharing and emails have been
horrible. A
typical 6k file that usually takes 3 to 4 seconds to open up takes 45
seconds to open up over the WAN link. Prior to the switch we uses
point to
point and the response was not as bad.
Does anyone know of any tweaks that can be done to get better response
times. The problems seems to be the worse for Microsoft products. If
we
use a telnet session for our unix info, everything seems to respond
better.
Our Setup:
We have several centers. Each center connects back to the central hub
by
way of a T1 to a Frame Cloud. For each center that has a T1 line to
the
cloud, the Hub has a T1 for that center to the cloud. Bandwidth is
match for
the total of all centers from the hub to the Frame Cloud. ie... 4
centers =
6.0MB and Hub has 6.0MB to Cloud
Each center has a maximum of 6 users that could possibly transfer or
use the
network. The hub has 4 max. Total users throughout the network is 40
users.
Thank You
Terry
.
- Prev by Date: Re: Adding Windows 2K3 to W2K Domain
- Next by Date: Re: Two internet connections
- Previous by thread: Re: Adding Windows 2K3 to W2K Domain
- Next by thread: Re: Two internet connections
- Index(es):
Relevant Pages
|
