A
Anthony Smith
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!
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!