Re: VPN, FTP, or remote desktop
- From: "xfile" <cou-cou@xxxxxxxxxxxxxxxxx>
- Date: Sun, 8 Jan 2006 23:36:08 +0800
Hi,
Many thanks for your kind reply.
I guess our immediate choice will be testing on the possibility of remote
desktop for accessing individual systems, using your suggestions on the
other post.
I was told the WBR and WBR2 provide some VPN functions but could not find
any appropriate configurations assistance from their technical support.
If the cost of recommended router is not too expensive, we might be able to
get one but we already have more than needed routers.
Would appreciate if you or someone could also point us to where could we
find some tutorial materials for putting everything together including
router, Windows 2003 server and XP Pro.
It seems to be easy for experts but we know that as long as one part is
being configured incorrectly, there will be no connections and it's so
difficult to know which part is wrong.
Many thanks.
"Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u8t%23A6EFGHA.3056@xxxxxxxxxxxxxxxxxxxxxxx
> Well, I would recommend a VPN versus FTP simply because of security
> issues. You could also look at using Secure Shell (SSH) versus VPN. It
> would still require a PC at either site to be running as a SSH server for
> remote access.
>
> Remote Desktop to individual PCs is a good choice simply because of the
> flexibility and the fact the native RDP data link is encrypted.
>
> FTP is not encrypted natively although there are, I believe, secure FTP
> options out there. Personally I don't think FTP is a good choice.
>
> If your budget allows there are VPN end-point type routers that would...
>
> * Allow a site to site VPN tunnel to be setup independent of the
> availability of PCs at each site.
> * Allow remote client VPN tunnels to be setup to either site.
> * Include a wireless network function for the two different sites either
> by adding a wireless card to the router...
>
> http://www.zyxel.com/product/model.php?indexcate=1037588623&indexcate1=&indexFlagvalue=1021873683
>
> ...using the existing Buffalo access point/routers as access points only
> and plug it into a port on the end-point router...
>
> http://www.zyxel.com/product/model.php?indexcate=1082973192&indexFlagvalue=1021873683
>
> ...or built-in wireless...
>
> http://www.linksys.com/servlet/Satellite?childpagename=US%2FLayout&packedargs=c%3DL_Product_C2%26cid%3D1118334818868&pagename=Linksys%2FCommon%2FVisitorWrapper
>
> My personal solution for secure remote access to my *home* LAN is to use
> Secure Shell (SSH) and run Remote Desktop through the SSH tunnel.
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the
> mutual benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
> "xfile" <cou-cou@xxxxxxxxxxxxxxxxx> wrote in message
> news:%23TaDSSEFGHA.3100@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>>
>> I have been searching and testing a networking solution primarily for
>> file sharing and intranet web site development for a while.
>>
>> However, I am getting more and more confused about what is the ideal
>> approach(es) for our tasks. Appreciate those who have helped answering
>> many questions before but would like to clarify all the confusions, if
>> possible.
>>
>> The following are our wishes and current situations:
>>
>> (1) We have two work locations and each one has its own wireless routers
>> (Buffalo WBR-G54 and WBR2-G54) for LAN and Wireless connections, and each
>> location has its own DSL service and also has an ISP assigned static IP
>> address.
>>
>> (2) All computers belong to the same domain but not all are at the same
>> physical location.
>>
>> (3) One location has a Windows 2003 Server (Standard) but not always on
>> and will be turned off once a while. All other computers are using XP
>> Pro. DHCP server function is done by the primary router of each location
>> so does the Default Internet Gateway. DNS server is also done by the two
>> primary routers and Win 2003 also serves as the intranet DNS server.
>>
>> (4) All client computers can browse and use others' shared folders
>> without any problems, and if them all at one location where the server
>> sits, they can share folders as well.
>>
>> (5) All computers can access to Internet without any problem.
>>
>> Questions:
>>
>> (1) If for file sharing purpose (such as access a shared folder or an
>> employee wishes to access his/her second computer at a remote location),
>> what is the ideal approach for the networking method between the two
>> sites and at another location? Specifically, will it be the VPN, remote
>> desktop, or FTP?
>>
>> It seems all of the three can accomplish this with different levels of
>> complexity. We have not set up VPN yet, but tried FTP and remote desktop
>> and seems both can accomplish the task, except we have not tried from
>> "pure" internet environment yet - that means sitting at a cafe shop and
>> try to access
>>
>> (2) If someone is trying to edit the intranet web site sits in the Win
>> 2003 server, will VPN be the only approach?
>>
>> (3) In our case, do we need anything like Dynamic DNS or something
>> similar?
>>
>> (4) Finally, can someone point us to where can we find tutorial materials
>> that fit into our situations? We have tried many but seems to be more
>> and more confused now.
>>
>> Many thanks in advance.
>>
>>
>
>
.
- Follow-Ups:
- Re: VPN, FTP, or remote desktop
- From: Sooner Al [MVP]
- Re: VPN, FTP, or remote desktop
- References:
- VPN, FTP, or remote desktop
- From: xfile
- Re: VPN, FTP, or remote desktop
- From: Sooner Al [MVP]
- VPN, FTP, or remote desktop
- Prev by Date: TCP/IP over Firewire hides other network connections
- Next by Date: All folders on the computer is read-only
- Previous by thread: Re: VPN, FTP, or remote desktop
- Next by thread: Re: VPN, FTP, or remote desktop
- Index(es):
Relevant Pages
|
