Graham J wrote:
> "The Natural Philosopher" <(E-Mail Removed)> wrote in message
> news:hmbnhn$6eq$(E-Mail Removed)...
>> alexd wrote:
>>> On Sat, 27 Feb 2010 12:32:55 +0000, Graham J wrote:
>>>
>>>> Note that it is essential that the subnet in office 1 has a different IP
>>>> address from the subnet in office 2. The routers then route between the
>>>> two subnets over the VPN.
>>> It is actually possible to have a bridged rather than routed VPN, but
>>> probably not desirable.
>>>
>>>> Assuming ordinary ADSL connections, the limiting speed factor is the
>>>> upload speed - probably 448kbits/sec at each site.
>>> Given the low cost of ADSL2+, there's no reason not to switch if it's
>>> available.
>>>
>>>> Be aware that performance of typical M$ applications between the two
>>>> sites will be painfully poor - 448kbits/sec is 200 (or 2000) times
>>>> slower than the LAN in each of the offices.
>>> If the problem is the SMB protocol, Windows has native support for WebDAV
>>> file shares. If you used HTTPS you wouldn't need the VPN either, although
>>> you may want a VPN for other applications.
>>>
>> It's also been my experience that SMB is far far worse than e.g. ftp over
>> a WAN.
>>
>> This may be beacause windows tries to be clever, and build icons, and so
>> on from file info. FTP just transfers the file.
>>
>> Whilst SMB (Netbios over TCP etc etc) works, its very very slow.
>
> The issue for users is what they want to do. The most obvious requirement
> is to open Word files for editing, so SMB is the underlying protocol. What
> they don't want is to learn a new way of working simply because their files
> are on a non-local computer.
>
drag and drop to local, work there, drag and drop to remote
|