Re: Home Office wants a Remote Workstation to access resources

Keeping your current SBS 2000 LAN, you seem to have two choices:

1. Install a dedicated WinXP Pro workstation on the SBS 2000 LAN that can
be remote controlled by the Location A workstation (via VPN/Remote Desktop
Connection (RDC) or maybe just an RDC session without the VPN). The
workstation at Location A could then be a lesser model running Windows XP
Pro or even (shudder) Windows XP Home Edition. All work would then be
processed on the dedicated Win XP Pro machine and no data would be
transferred to the remote PC at Location A.

2) Install a Terminal Server in your SBS 2000 LAN and access it from
Location A. This is the more expensive approach if you don't plan on adding
more remote PCs in the near future.

--
Merv Porter [SBS MVP]
===================================

"Anthony Smith" <anthony@xxxxxxxxxxx> wrote in message
news:%23Kv7DVb1FHA.3856@xxxxxxxxxxxxxxxxxxxxxxx
> Good Afternoon Everyone,
>
> I hope everyone is doing fine. Our family has a small home office network
> of about 3 PCs.
> We recently hired an administrator and set up a PC in a garage down the
> street from the home office. The garage is probably about 1/4 to 1/2 mile
> away. This remote computer has access to a high speed internet connection
> and we have been trying out the remote desktop feature from XP to the
> Win2000 SBS server but it's not working out for us. We really want the
> remote desktop to act like it's a local desktop within the small office.
> Terminal Svc isn't working. Here are details below:
>
> Okay, here is what we're trying to do. We are trying to allow a
> computer/workstation, with Windows XP (SP2) Professional, located at one
> location (home/residence or Location A) to connect to a Windows network
> domain (OLETANET) that is located at another home/residence (Location B).
>
> The workstation must be able to connect to OLETANET via a high-speed
> internet connection. The workstation is currently on a secured wireless
> network, and OLETANET is behind a hardware firewall, Netgear FR318. The
> primary domain server of OLETANET is the Windows 2000 server. The server
> is primarily used as a file server; data files exist on the server that
> are accessed by software running on the workstations that are connected to
> OLETANET.
>
> We have been successful in establishing a remote connection from one
> residence (Location A) to another residence (Location B), and the
> workstation at Location A is able to use the Windows XP Remote Desktop to
> connect to the file server on OLETANET at Location B. Permissions have
> been set on the server at Location B for one user, limiting access for
> this user that sits at the workstation at Location A.
>
> It would be nice to have the Windows XP workstation at Location A to be
> able to connect to OLETANET at Location B and operate just like the rest
> of the workstations at Location B. The workstations at Location B are able
> to login to the domain (OLETANET) at startup of their machines, map a
> network drive to the file server on OLETANET, run client software (on the
> C drive of the workstations) that connect to the mapped network drive on
> the file server, and print to the network printer that is also connected
> to OLETANET.
>
> The workstations need to run client software (Windows and DOS
> applications) from the C drive and connect to the G drive (mapped network
> drive), because the data for the software resides on the G drive (mapped
> network drive to file server).
>
> We have tried VPN, and the connection was very slow, and the Remote
> Desktop is just not going to meet our requirements. We are trying to avoid
> the situation of paying for a T1 line (or high-speed broadband/internet
>
> connection) between Location A and B.
>
> Someone, please let us know what we can do to make the workstation at
> Location A operate just like the workstations at Location B can operate,
> being connected to OLETANET.
>
> Anthony....
>
> In God We Trust!
>
>


.

Relevant Pages

  • Re: RWW-RDP
    ... It utilizes a cross-over cable between it and the SBS Server. ... Ehternet from hub to server and from hub to workstation ... Ethernet adapter Server Local Area Connection: ... Also, Merv, I can connect to the server and client machines on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace Issue
    ... I had to "rebuild" my server. ... I could use RWW to a remote desktop on the ... I also am running a new workstation with Vista Ultimate that was never ... on that computer either but can use the remote desktop connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow Network with New SBS 2003 & Old XP Workstations
    ... perhaps some other software installed on the old workstation not on the ... We are running ISA server 2004 with SP3, ... Ethernet adapter Server Local Area Connection: ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Problems ?? Slow connection to Server
    ... The server has a Cisco router between it and the NHS Server ... I ran system restore on my workstation This made no difference. ... > Health Service) managed connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trouble integrating existing SBS 2003 server into a home netwo
    ... If the problematic workstation is getting that IP, ... workstations and the SBS server should be using 192.168.1.x as an ip range. ... Disabling Internet Connection Sharing and Internet Sharing ...
    (microsoft.public.windows.server.sbs)