Windows NT Assigning virtual IPs per user

  • Thread starter Thread starter mark@vk.net
  • Start date Start date
M

mark@vk.net

Hi, I know this can be done on Citrix, but I need to do it on native
Terminal Server.

It is it possible to have a pool of addresses that are assigned to
Windows Terminal Server users so that when they launch client/server
apps they use a unique IP address.

For example, server has a bunch of addresses bound to it's interface
10.1.1.1
10.1.1.2
10.1.1.3
10.1.1.4
10.1.1.5
10.1.1.6
10.1.1.7
10.1.1.8
10.1.1.9

Remote user #1 logs in and when they open a browser connection to
server another server, their source ip address for that connection is
10.1.1.1

Remote user #2 logs in and when they open a browser connection to
server another server, their source ip address for that connection is
10.1.1.2

Remote user #3 logs in and when they open a browser connection to
server another server, their source ip address for that connection is
10.1.1.3

and so on.

This would allow a packet filter or other firewall device to permit/
deny particular users access to systems at the network level.
 
No, you need either Citrix Presentation SErver or the virtual IP product
from Provision Networks.

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

mark@vk.net wrote:
> Hi, I know this can be done on Citrix, but I need to do it on native
> Terminal Server.
>
> It is it possible to have a pool of addresses that are assigned to
> Windows Terminal Server users so that when they launch client/server
> apps they use a unique IP address.
>
> For example, server has a bunch of addresses bound to it's interface
> 10.1.1.1
> 10.1.1.2
> 10.1.1.3
> 10.1.1.4
> 10.1.1.5
> 10.1.1.6
> 10.1.1.7
> 10.1.1.8
> 10.1.1.9
>
> Remote user #1 logs in and when they open a browser connection to
> server another server, their source ip address for that connection is
> 10.1.1.1
>
> Remote user #2 logs in and when they open a browser connection to
> server another server, their source ip address for that connection is
> 10.1.1.2
>
> Remote user #3 logs in and when they open a browser connection to
> server another server, their source ip address for that connection is
> 10.1.1.3
>
> and so on.
>
> This would allow a packet filter or other firewall device to permit/
> deny particular users access to systems at the network level.
>
 
Back
Top