VPN NEWBIE

I kow how to setup w2003 std. srvr. (one nic card) for VPN using
theirdomain.dyndns.org in linksys router and know how to setup xp vpn client.
but how does vpn on server know to let client into their workstation at
office (not server) like in remote desktop?

Well, actually you could run RDP through the VPN tunnel. Otherwise a VPN
connection essentially makes the client the equivalent of a node on the
internal network; except that you probably would not be able to browse
through My Network Places. So you connect to shares on a workstation by
Start/Run \\WorkstationName or \\WorkstationIP.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Donna" <(E-Mail Removed)> wrote in message
news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> theirdomain.dyndns.org in linksys router and know how to setup xp vpn
client.
> but how does vpn on server know to let client into their workstation at
> office (not server) like in remote desktop?

thank you, so I would just go to Start Run \\workstationip and that would
connect me to the computer so I can use the desktop programs etc. on the
workstation?

"Doug Sherman [MVP]" wrote:

> Well, actually you could run RDP through the VPN tunnel. Otherwise a VPN
> connection essentially makes the client the equivalent of a node on the
> internal network; except that you probably would not be able to browse
> through My Network Places. So you connect to shares on a workstation by
> Start/Run \\WorkstationName or \\WorkstationIP.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Donna" <(E-Mail Removed)> wrote in message
> news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > theirdomain.dyndns.org in linksys router and know how to setup xp vpn
> client.
> > but how does vpn on server know to let client into their workstation at
> > office (not server) like in remote desktop?
>
>
>

No. \\workstationIP will connect you only to the shared resources on
workstation. Think of this as being the same thing that you would get if
you brought your home computer to work, connected it to the network, and
then browsed to workstation. You could run programs on your home computer
and access/use shared data on workstation, but for the most part you would
not be able to run programs which are installed only on the workstation.

However, if you establish a VPN connection and RDP is enabled on the
workstation, then you should be able to establish an RDP connection by
opening the Remote Desktop client on the home computer and entering the IP
of the workstation. Of course, if you really want RDP, you don't need to
use a VPN connection. Instead on the office Internet router or firewall you
can map port 3389 to the IP of workstation - then you connect by entering
your public IP in the RDP client on your home computer.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Donna" <(E-Mail Removed)> wrote in message
news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> thank you, so I would just go to Start Run \\workstationip and that would
> connect me to the computer so I can use the desktop programs etc. on the
> workstation?
>
> "Doug Sherman [MVP]" wrote:
>
> > Well, actually you could run RDP through the VPN tunnel. Otherwise a
VPN
> > connection essentially makes the client the equivalent of a node on the
> > internal network; except that you probably would not be able to browse
> > through My Network Places. So you connect to shares on a workstation by
> > Start/Run \\WorkstationName or \\WorkstationIP.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Donna" <(E-Mail Removed)> wrote in message
> > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > theirdomain.dyndns.org in linksys router and know how to setup xp vpn
> > client.
> > > but how does vpn on server know to let client into their workstation
at
> > > office (not server) like in remote desktop?
> >
> >
> >

yes I do understand and would rather run RDP instead of VPN but my only
problem is that onle oe workstation at a time can be logged into the company
network using RDP that is why I have to set up VPN because more than one user
wants to access their corporate PC from home.

So back to VPN, I do the VPN connection from the home PC to the corporate PC
and then after connecting run the rdp of the ip of the corporate PC, right?

"Doug Sherman [MVP]" wrote:

> No. \\workstationIP will connect you only to the shared resources on
> workstation. Think of this as being the same thing that you would get if
> you brought your home computer to work, connected it to the network, and
> then browsed to workstation. You could run programs on your home computer
> and access/use shared data on workstation, but for the most part you would
> not be able to run programs which are installed only on the workstation.
>
> However, if you establish a VPN connection and RDP is enabled on the
> workstation, then you should be able to establish an RDP connection by
> opening the Remote Desktop client on the home computer and entering the IP
> of the workstation. Of course, if you really want RDP, you don't need to
> use a VPN connection. Instead on the office Internet router or firewall you
> can map port 3389 to the IP of workstation - then you connect by entering
> your public IP in the RDP client on your home computer.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Donna" <(E-Mail Removed)> wrote in message
> news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > thank you, so I would just go to Start Run \\workstationip and that would
> > connect me to the computer so I can use the desktop programs etc. on the
> > workstation?
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > Well, actually you could run RDP through the VPN tunnel. Otherwise a
> VPN
> > > connection essentially makes the client the equivalent of a node on the
> > > internal network; except that you probably would not be able to browse
> > > through My Network Places. So you connect to shares on a workstation by
> > > Start/Run \\WorkstationName or \\WorkstationIP.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Donna" <(E-Mail Removed)> wrote in message
> > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > > theirdomain.dyndns.org in linksys router and know how to setup xp vpn
> > > client.
> > > > but how does vpn on server know to let client into their workstation
> at
> > > > office (not server) like in remote desktop?
> > >
> > >
> > >
>
>
>

Once you've established a VPN tunnel from the remote PC into the corporate
network, you can connect via RDP to any machine on the corporate network
provided the corporate machine is configured to accept RDP connections.

On the corporate workstation (or server), right-click on the My Computer
icon, select Properties and click on the Remote tab. From there you can
enable (or disable) RDP, as well as define which users are allowed access the
machine via RDP.

RDP is supported in Windows XP Pro and the Windows Server 2003 family. You
can use RDP to access Windows 2000 Servers if they have Terminal Services
installed and running. Two users can access a server at a time, and only one
user can access a workstation at a time.

You can use either the IP address of the machine you want to connect to or
the computer name so long some sort of name service is running on your
network, DNS or WINS, or NetBIOS in a workgroup.

Good luck!

Kirk Hauer, CCNA, MCSE

"Donna" wrote:

> yes I do understand and would rather run RDP instead of VPN but my only
> problem is that onle oe workstation at a time can be logged into the company
> network using RDP that is why I have to set up VPN because more than one user
> wants to access their corporate PC from home.
>
> So back to VPN, I do the VPN connection from the home PC to the corporate PC
> and then after connecting run the rdp of the ip of the corporate PC, right?
>
> "Doug Sherman [MVP]" wrote:
>
> > No. \\workstationIP will connect you only to the shared resources on
> > workstation. Think of this as being the same thing that you would get if
> > you brought your home computer to work, connected it to the network, and
> > then browsed to workstation. You could run programs on your home computer
> > and access/use shared data on workstation, but for the most part you would
> > not be able to run programs which are installed only on the workstation.
> >
> > However, if you establish a VPN connection and RDP is enabled on the
> > workstation, then you should be able to establish an RDP connection by
> > opening the Remote Desktop client on the home computer and entering the IP
> > of the workstation. Of course, if you really want RDP, you don't need to
> > use a VPN connection. Instead on the office Internet router or firewall you
> > can map port 3389 to the IP of workstation - then you connect by entering
> > your public IP in the RDP client on your home computer.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Donna" <(E-Mail Removed)> wrote in message
> > news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > > thank you, so I would just go to Start Run \\workstationip and that would
> > > connect me to the computer so I can use the desktop programs etc. on the
> > > workstation?
> > >
> > > "Doug Sherman [MVP]" wrote:
> > >
> > > > Well, actually you could run RDP through the VPN tunnel. Otherwise a
> > VPN
> > > > connection essentially makes the client the equivalent of a node on the
> > > > internal network; except that you probably would not be able to browse
> > > > through My Network Places. So you connect to shares on a workstation by
> > > > Start/Run \\WorkstationName or \\WorkstationIP.
> > > >
> > > > Doug Sherman
> > > > MCSE, MCSA, MCP+I, MVP
> > > >
> > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > > > theirdomain.dyndns.org in linksys router and know how to setup xp vpn
> > > > client.
> > > > > but how does vpn on server know to let client into their workstation
> > at
> > > > > office (not server) like in remote desktop?
> > > >
> > > >
> > > >
> >
> >
> >

Kirk got it.

Also, if your clients can keep track of port numbers, you can alter these to
allow multiple RDP connections without VPN:

http://support.microsoft.com/kb/306759/en-us


Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Donna" <(E-Mail Removed)> wrote in message
news:B23DE492-3C7A-477E-830A-(E-Mail Removed)...
> yes I do understand and would rather run RDP instead of VPN but my only
> problem is that onle oe workstation at a time can be logged into the
company
> network using RDP that is why I have to set up VPN because more than one
user
> wants to access their corporate PC from home.
>
> So back to VPN, I do the VPN connection from the home PC to the corporate
PC
> and then after connecting run the rdp of the ip of the corporate PC,
right?
>
> "Doug Sherman [MVP]" wrote:
>
> > No. \\workstationIP will connect you only to the shared resources on
> > workstation. Think of this as being the same thing that you would get
if
> > you brought your home computer to work, connected it to the network, and
> > then browsed to workstation. You could run programs on your home
computer
> > and access/use shared data on workstation, but for the most part you
would
> > not be able to run programs which are installed only on the workstation.
> >
> > However, if you establish a VPN connection and RDP is enabled on the
> > workstation, then you should be able to establish an RDP connection by
> > opening the Remote Desktop client on the home computer and entering the
IP
> > of the workstation. Of course, if you really want RDP, you don't need
to
> > use a VPN connection. Instead on the office Internet router or firewall
you
> > can map port 3389 to the IP of workstation - then you connect by
entering
> > your public IP in the RDP client on your home computer.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Donna" <(E-Mail Removed)> wrote in message
> > news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > > thank you, so I would just go to Start Run \\workstationip and that
would
> > > connect me to the computer so I can use the desktop programs etc. on
the
> > > workstation?
> > >
> > > "Doug Sherman [MVP]" wrote:
> > >
> > > > Well, actually you could run RDP through the VPN tunnel. Otherwise
a
> > VPN
> > > > connection essentially makes the client the equivalent of a node on
the
> > > > internal network; except that you probably would not be able to
browse
> > > > through My Network Places. So you connect to shares on a
workstation by
> > > > Start/Run \\WorkstationName or \\WorkstationIP.
> > > >
> > > > Doug Sherman
> > > > MCSE, MCSA, MCP+I, MVP
> > > >
> > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > > > theirdomain.dyndns.org in linksys router and know how to setup xp
vpn
> > > > client.
> > > > > but how does vpn on server know to let client into their
workstation
> > at
> > > > > office (not server) like in remote desktop?
> > > >
> > > >
> > > >
> >
> >
> >

so technically I do not need the VPN, I can use RDP and in my router open
ports 3389 with an ip say .24 enable
another port 3390 with an ip say .25 and in remote desktop wanip# or
computername colon(3390 and I have to change the listening port in the
registry of that computer from 3389 to 3390? I went by the link you send but
could not find it in the Windows XP Prof. Registry.

"Doug Sherman [MVP]" wrote:

> Kirk got it.
>
> Also, if your clients can keep track of port numbers, you can alter these to
> allow multiple RDP connections without VPN:
>
> http://support.microsoft.com/kb/306759/en-us
>
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Donna" <(E-Mail Removed)> wrote in message
> news:B23DE492-3C7A-477E-830A-(E-Mail Removed)...
> > yes I do understand and would rather run RDP instead of VPN but my only
> > problem is that onle oe workstation at a time can be logged into the
> company
> > network using RDP that is why I have to set up VPN because more than one
> user
> > wants to access their corporate PC from home.
> >
> > So back to VPN, I do the VPN connection from the home PC to the corporate
> PC
> > and then after connecting run the rdp of the ip of the corporate PC,
> right?
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > No. \\workstationIP will connect you only to the shared resources on
> > > workstation. Think of this as being the same thing that you would get
> if
> > > you brought your home computer to work, connected it to the network, and
> > > then browsed to workstation. You could run programs on your home
> computer
> > > and access/use shared data on workstation, but for the most part you
> would
> > > not be able to run programs which are installed only on the workstation.
> > >
> > > However, if you establish a VPN connection and RDP is enabled on the
> > > workstation, then you should be able to establish an RDP connection by
> > > opening the Remote Desktop client on the home computer and entering the
> IP
> > > of the workstation. Of course, if you really want RDP, you don't need
> to
> > > use a VPN connection. Instead on the office Internet router or firewall
> you
> > > can map port 3389 to the IP of workstation - then you connect by
> entering
> > > your public IP in the RDP client on your home computer.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Donna" <(E-Mail Removed)> wrote in message
> > > news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > > > thank you, so I would just go to Start Run \\workstationip and that
> would
> > > > connect me to the computer so I can use the desktop programs etc. on
> the
> > > > workstation?
> > > >
> > > > "Doug Sherman [MVP]" wrote:
> > > >
> > > > > Well, actually you could run RDP through the VPN tunnel. Otherwise
> a
> > > VPN
> > > > > connection essentially makes the client the equivalent of a node on
> the
> > > > > internal network; except that you probably would not be able to
> browse
> > > > > through My Network Places. So you connect to shares on a
> workstation by
> > > > > Start/Run \\WorkstationName or \\WorkstationIP.
> > > > >
> > > > > Doug Sherman
> > > > > MCSE, MCSA, MCP+I, MVP
> > > > >
> > > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > > > > theirdomain.dyndns.org in linksys router and know how to setup xp
> vpn
> > > > > client.
> > > > > > but how does vpn on server know to let client into their
> workstation
> > > at
> > > > > > office (not server) like in remote desktop?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>

wait I just did a search on 3389 TCP in registry and found two instances both
under globallyopenports\list one under sharedaccess\parameters\firewall and
then another so that is what I would change?

"Donna" wrote:

> so technically I do not need the VPN, I can use RDP and in my router open
> ports 3389 with an ip say .24 enable
> another port 3390 with an ip say .25 and in remote desktop wanip# or
> computername colon(3390 and I have to change the listening port in the
> registry of that computer from 3389 to 3390? I went by the link you send but
> could not find it in the Windows XP Prof. Registry.
>
> "Doug Sherman [MVP]" wrote:
>
> > Kirk got it.
> >
> > Also, if your clients can keep track of port numbers, you can alter these to
> > allow multiple RDP connections without VPN:
> >
> > http://support.microsoft.com/kb/306759/en-us
> >
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Donna" <(E-Mail Removed)> wrote in message
> > news:B23DE492-3C7A-477E-830A-(E-Mail Removed)...
> > > yes I do understand and would rather run RDP instead of VPN but my only
> > > problem is that onle oe workstation at a time can be logged into the
> > company
> > > network using RDP that is why I have to set up VPN because more than one
> > user
> > > wants to access their corporate PC from home.
> > >
> > > So back to VPN, I do the VPN connection from the home PC to the corporate
> > PC
> > > and then after connecting run the rdp of the ip of the corporate PC,
> > right?
> > >
> > > "Doug Sherman [MVP]" wrote:
> > >
> > > > No. \\workstationIP will connect you only to the shared resources on
> > > > workstation. Think of this as being the same thing that you would get
> > if
> > > > you brought your home computer to work, connected it to the network, and
> > > > then browsed to workstation. You could run programs on your home
> > computer
> > > > and access/use shared data on workstation, but for the most part you
> > would
> > > > not be able to run programs which are installed only on the workstation.
> > > >
> > > > However, if you establish a VPN connection and RDP is enabled on the
> > > > workstation, then you should be able to establish an RDP connection by
> > > > opening the Remote Desktop client on the home computer and entering the
> > IP
> > > > of the workstation. Of course, if you really want RDP, you don't need
> > to
> > > > use a VPN connection. Instead on the office Internet router or firewall
> > you
> > > > can map port 3389 to the IP of workstation - then you connect by
> > entering
> > > > your public IP in the RDP client on your home computer.
> > > >
> > > > Doug Sherman
> > > > MCSE, MCSA, MCP+I, MVP
> > > >
> > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > > > > thank you, so I would just go to Start Run \\workstationip and that
> > would
> > > > > connect me to the computer so I can use the desktop programs etc. on
> > the
> > > > > workstation?
> > > > >
> > > > > "Doug Sherman [MVP]" wrote:
> > > > >
> > > > > > Well, actually you could run RDP through the VPN tunnel. Otherwise
> > a
> > > > VPN
> > > > > > connection essentially makes the client the equivalent of a node on
> > the
> > > > > > internal network; except that you probably would not be able to
> > browse
> > > > > > through My Network Places. So you connect to shares on a
> > workstation by
> > > > > > Start/Run \\WorkstationName or \\WorkstationIP.
> > > > > >
> > > > > > Doug Sherman
> > > > > > MCSE, MCSA, MCP+I, MVP
> > > > > >
> > > > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN using
> > > > > > > theirdomain.dyndns.org in linksys router and know how to setup xp
> > vpn
> > > > > > client.
> > > > > > > but how does vpn on server know to let client into their
> > workstation
> > > > at
> > > > > > > office (not server) like in remote desktop?
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >

No - do not mess with anything other than:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TerminalServer\WinStatio
ns\RDP-Tcp\PortNumber

All of my XP Pro machines have this key, but it may not exist unless and
until RDP is enabled on the machine.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Donna" <(E-Mail Removed)> wrote in message
news26BDADE-7F1A-468C-8463-(E-Mail Removed)...
> wait I just did a search on 3389 TCP in registry and found two instances
both
> under globallyopenports\list one under sharedaccess\parameters\firewall
and
> then another so that is what I would change?
>
> "Donna" wrote:
>
> > so technically I do not need the VPN, I can use RDP and in my router
open
> > ports 3389 with an ip say .24 enable
> > another port 3390 with an ip say .25 and in remote desktop wanip# or
> > computername colon(3390 and I have to change the listening port in the
> > registry of that computer from 3389 to 3390? I went by the link you send
but
> > could not find it in the Windows XP Prof. Registry.
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > Kirk got it.
> > >
> > > Also, if your clients can keep track of port numbers, you can alter
these to
> > > allow multiple RDP connections without VPN:
> > >
> > > http://support.microsoft.com/kb/306759/en-us
> > >
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Donna" <(E-Mail Removed)> wrote in message
> > > news:B23DE492-3C7A-477E-830A-(E-Mail Removed)...
> > > > yes I do understand and would rather run RDP instead of VPN but my
only
> > > > problem is that onle oe workstation at a time can be logged into the
> > > company
> > > > network using RDP that is why I have to set up VPN because more than
one
> > > user
> > > > wants to access their corporate PC from home.
> > > >
> > > > So back to VPN, I do the VPN connection from the home PC to the
corporate
> > > PC
> > > > and then after connecting run the rdp of the ip of the corporate PC,
> > > right?
> > > >
> > > > "Doug Sherman [MVP]" wrote:
> > > >
> > > > > No. \\workstationIP will connect you only to the shared resources
on
> > > > > workstation. Think of this as being the same thing that you would
get
> > > if
> > > > > you brought your home computer to work, connected it to the
network, and
> > > > > then browsed to workstation. You could run programs on your home
> > > computer
> > > > > and access/use shared data on workstation, but for the most part
you
> > > would
> > > > > not be able to run programs which are installed only on the
workstation.
> > > > >
> > > > > However, if you establish a VPN connection and RDP is enabled on
the
> > > > > workstation, then you should be able to establish an RDP
connection by
> > > > > opening the Remote Desktop client on the home computer and
entering the
> > > IP
> > > > > of the workstation. Of course, if you really want RDP, you don't
need
> > > to
> > > > > use a VPN connection. Instead on the office Internet router or
firewall
> > > you
> > > > > can map port 3389 to the IP of workstation - then you connect by
> > > entering
> > > > > your public IP in the RDP client on your home computer.
> > > > >
> > > > > Doug Sherman
> > > > > MCSE, MCSA, MCP+I, MVP
> > > > >
> > > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > > news:CF3A5CDF-C3F7-43F6-BBF7-(E-Mail Removed)...
> > > > > > thank you, so I would just go to Start Run \\workstationip and
that
> > > would
> > > > > > connect me to the computer so I can use the desktop programs
etc. on
> > > the
> > > > > > workstation?
> > > > > >
> > > > > > "Doug Sherman [MVP]" wrote:
> > > > > >
> > > > > > > Well, actually you could run RDP through the VPN tunnel.
Otherwise
> > > a
> > > > > VPN
> > > > > > > connection essentially makes the client the equivalent of a
node on
> > > the
> > > > > > > internal network; except that you probably would not be able
to
> > > browse
> > > > > > > through My Network Places. So you connect to shares on a
> > > workstation by
> > > > > > > Start/Run \\WorkstationName or \\WorkstationIP.
> > > > > > >
> > > > > > > Doug Sherman
> > > > > > > MCSE, MCSA, MCP+I, MVP
> > > > > > >
> > > > > > > "Donna" <(E-Mail Removed)> wrote in message
> > > > > > > news:EC2023C0-D1C2-4B0A-A21A-(E-Mail Removed)...
> > > > > > > > I kow how to setup w2003 std. srvr. (one nic card) for VPN
using
> > > > > > > > theirdomain.dyndns.org in linksys router and know how to
setup xp
> > > vpn
> > > > > > > client.
> > > > > > > > but how does vpn on server know to let client into their
> > > workstation
> > > > > at
> > > > > > > > office (not server) like in remote desktop?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >