Private Network and Public Network Link

Hi all,
I have a following scenario want all your suggestions on how to do it ?
I have desktop pcs that are in private network.And I also have One Server in
public network.I want these desktop pc 's in private network to access the
Server using Remote desktop or terminal service .And when these desktops pcs
connect to the server and access the internet ,I want the request from the
Server to go out as different public ips .So for each session or when each
desktop connects the Server through rdp ,each of the request from the Server
to the internet must have a diferent public ip.
That is giving each client a public ip when they access the internet through
RDP .

Not gonna happen.

What you are describing is the old orignal NAT back before the days when they
figured out how to "overload" a single public IP# with multiple users by using
the random Client Source Port as a unique identifier in the NAT Table. The old
form of NAT required and equal number of public IP#s as there were Hosts on the
private LAN (assuming they are used the Internet at the same time) and used a
Time-To-Live stamp on the IP-to-IP relationship. It was akward, inefficient,
horribly unsecure,..and deserved to die,...and it died. I don't know of any NAT
Devices today that can even do that.

The NAT being used today under the simple name "NAT",...is really "NAT
Overload",...but that name has died away as well and is now just referred to as
"NAT" which is what the old dead method used to be called.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

"kris" <(E-Mail Removed)> wrote in message
news:9C22C1DB-61D5-43D2-A114-(E-Mail Removed)...
> Hi all,
> I have a following scenario want all your suggestions on how to do it ?
> I have desktop pcs that are in private network.And I also have One Server in
> public network.I want these desktop pc 's in private network to access the
> Server using Remote desktop or terminal service .And when these desktops pcs
> connect to the server and access the internet ,I want the request from the
> Server to go out as different public ips .So for each session or when each
> desktop connects the Server through rdp ,each of the request from the Server
> to the internet must have a diferent public ip.
> That is giving each client a public ip when they access the internet through
> RDP .
>

To add to my other post,...Sorry, I didn't catch the Remote Desktop element of
the post the first time around. Remote Desktop does not even figure in or have
anything to do with NAT. When the users access the internet from the RDP
session the server is going to be using the Primary IP# of the outbound Nic. It
doesn't matter how many IP#s you have on the Nic,...it will still show as
originating from the Primary IP#. It is the way it works.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------


"kris" <(E-Mail Removed)> wrote in message
news:9C22C1DB-61D5-43D2-A114-(E-Mail Removed)...
> Hi all,
> I have a following scenario want all your suggestions on how to do it ?
> I have desktop pcs that are in private network.And I also have One Server in
> public network.I want these desktop pc 's in private network to access the
> Server using Remote desktop or terminal service .And when these desktops pcs
> connect to the server and access the internet ,I want the request from the
> Server to go out as different public ips .So for each session or when each
> desktop connects the Server through rdp ,each of the request from the Server
> to the internet must have a diferent public ip.
> That is giving each client a public ip when they access the internet through
> RDP .
>

Ok clean , good ,Now I have an idea on this issue.See shall i catch the RDP
Session and create a virtual interface at the server .After I create a
virtual interface when the RDP Session is initiated i will do a ip forwarding
for the private ip(that has done the RDP request) with the public ip that is
mapped with the virtual interface.

Am I progressing in the right way.
Will this work ?

Hmmmm need your reply...

"Phillip Windell" wrote:

> To add to my other post,...Sorry, I didn't catch the Remote Desktop element of
> the post the first time around. Remote Desktop does not even figure in or have
> anything to do with NAT. When the users access the internet from the RDP
> session the server is going to be using the Primary IP# of the outbound Nic. It
> doesn't matter how many IP#s you have on the Nic,...it will still show as
> originating from the Primary IP#. It is the way it works.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft, or
> anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
> "kris" <(E-Mail Removed)> wrote in message
> news:9C22C1DB-61D5-43D2-A114-(E-Mail Removed)...
> > Hi all,
> > I have a following scenario want all your suggestions on how to do it ?
> > I have desktop pcs that are in private network.And I also have One Server in
> > public network.I want these desktop pc 's in private network to access the
> > Server using Remote desktop or terminal service .And when these desktops pcs
> > connect to the server and access the internet ,I want the request from the
> > Server to go out as different public ips .So for each session or when each
> > desktop connects the Server through rdp ,each of the request from the Server
> > to the internet must have a diferent public ip.
> > That is giving each client a public ip when they access the internet through
> > RDP .
> >
>
>
>

"kris" <(E-Mail Removed)> wrote in message
news:6CBA91BC-A708-45CC-A949-(E-Mail Removed)...
> Ok clean , good ,Now I have an idea on this issue.See shall i catch the RDP
> Session and create a virtual interface at the server .

Create a virtual interface ?

> After I create a
> virtual interface when the RDP Session is initiated i will do a ip forwarding
> for the private ip(that has done the RDP request) with the public ip that is
> mapped with the virtual interface.
>
> Am I progressing in the right way.

No. IP Forwarding doesn't map anything to anything. IP Forwarding is just
normal every-day simple Layer3 routing.

> Will this work ?

No.
According to how I interpret what you are asking,...there is just simply "no
such thing".

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

Hi Phillip ,
I guess you dint get my idea,Let me explain.See whenever RDP
session is initiated i will create virtual network interface and assign a
public ip to it.After the creation of Virtual Network interface ,I will
forward all the traffic to that public ip which was assigned to the virtual
nic.Its something like having one physical nic with multiple virtual nics....
Tel me your comments on this..?

Otherwise pls suggest me an idea as to how we can achieve my scenario.

"Phillip Windell" wrote:

> "kris" <(E-Mail Removed)> wrote in message
> news:6CBA91BC-A708-45CC-A949-(E-Mail Removed)...
> > Ok clean , good ,Now I have an idea on this issue.See shall i catch the RDP
> > Session and create a virtual interface at the server .
>
> Create a virtual interface ?
>
> > After I create a
> > virtual interface when the RDP Session is initiated i will do a ip forwarding
> > for the private ip(that has done the RDP request) with the public ip that is
> > mapped with the virtual interface.
> >
> > Am I progressing in the right way.
>
> No. IP Forwarding doesn't map anything to anything. IP Forwarding is just
> normal every-day simple Layer3 routing.
>
> > Will this work ?
>
> No.
> According to how I interpret what you are asking,...there is just simply "no
> such thing".
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft, or
> anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"kris" <(E-Mail Removed)> wrote in message
news:217538BF-5F67-4315-9E57-(E-Mail Removed)...
> Hi Phillip ,
> I guess you dint get my idea,Let me explain.See whenever RDP
> session is initiated i will create virtual network interface and assign a
> public ip to it.After the creation of Virtual Network interface ,I will
> forward all the traffic to that public ip which was assigned to the virtual
> nic.Its something like having one physical nic with multiple virtual nics....
> Tel me your comments on this..?
>
> Otherwise pls suggest me an idea as to how we can achieve my scenario.

I looked back at the first post to see the original request. There is no such
"functionality",...what you want cannot be done,...it does not exist.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

Hey Phillip ,
You mean say that we cannot create virtual Nic's .Yes it is
possible . Try to read about Microsoft Virtual Server and Virtual networks or
try reading abt the NDIS Mini port development. So I guess I can create
virtual Nic and assign a ip to it.
And there are also options to catch the RDP session at the server end using
the terminal services API ..


RDP Session Initiated -> Virtual NIC Creation -> New IP -> IP forwarding to
that new IP


I guess this should work ....


Tell me your comments...


"Phillip Windell" wrote:

> "kris" <(E-Mail Removed)> wrote in message
> news:217538BF-5F67-4315-9E57-(E-Mail Removed)...
> > Hi Phillip ,
> > I guess you dint get my idea,Let me explain.See whenever RDP
> > session is initiated i will create virtual network interface and assign a
> > public ip to it.After the creation of Virtual Network interface ,I will
> > forward all the traffic to that public ip which was assigned to the virtual
> > nic.Its something like having one physical nic with multiple virtual nics....
> > Tel me your comments on this..?
> >
> > Otherwise pls suggest me an idea as to how we can achieve my scenario.
>
> I looked back at the first post to see the original request. There is no such
> "functionality",...what you want cannot be done,...it does not exist.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft, or
> anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

Yes, you can create virtual NICs in virtual machines and you can create
virtual networks. But the basic rules of networking and TCP/IP still apply.
If you really want to waste your time, go ahead.

"kris" <(E-Mail Removed)> wrote in message
news:C57B225C-6F95-4033-A553-(E-Mail Removed)...
> Hey Phillip ,
> You mean say that we cannot create virtual Nic's .Yes it is
> possible . Try to read about Microsoft Virtual Server and Virtual networks
> or
> try reading abt the NDIS Mini port development. So I guess I can create
> virtual Nic and assign a ip to it.
> And there are also options to catch the RDP session at the server end
> using
> the terminal services API ..
>
>
> RDP Session Initiated -> Virtual NIC Creation -> New IP -> IP forwarding
> to
> that new IP
>
>
> I guess this should work ....
>
>
> Tell me your comments...
>
>
> "Phillip Windell" wrote:
>
>> "kris" <(E-Mail Removed)> wrote in message
>> news:217538BF-5F67-4315-9E57-(E-Mail Removed)...
>> > Hi Phillip ,
>> > I guess you dint get my idea,Let me explain.See whenever RDP
>> > session is initiated i will create virtual network interface and assign
>> > a
>> > public ip to it.After the creation of Virtual Network interface ,I will
>> > forward all the traffic to that public ip which was assigned to the
>> > virtual
>> > nic.Its something like having one physical nic with multiple virtual
>> > nics....
>> > Tel me your comments on this..?
>> >
>> > Otherwise pls suggest me an idea as to how we can achieve my scenario.
>>
>> I looked back at the first post to see the original request. There is no
>> such
>> "functionality",...what you want cannot be done,...it does not exist.
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft, or
>> anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>>

Oh no,Is there any other way where I can create different public ips for each
RDP session request ????





"Bill Grant" wrote:

> Yes, you can create virtual NICs in virtual machines and you can create
> virtual networks. But the basic rules of networking and TCP/IP still apply.
> If you really want to waste your time, go ahead.
>
> "kris" <(E-Mail Removed)> wrote in message
> news:C57B225C-6F95-4033-A553-(E-Mail Removed)...
> > Hey Phillip ,
> > You mean say that we cannot create virtual Nic's .Yes it is
> > possible . Try to read about Microsoft Virtual Server and Virtual networks
> > or
> > try reading abt the NDIS Mini port development. So I guess I can create
> > virtual Nic and assign a ip to it.
> > And there are also options to catch the RDP session at the server end
> > using
> > the terminal services API ..
> >
> >
> > RDP Session Initiated -> Virtual NIC Creation -> New IP -> IP forwarding
> > to
> > that new IP
> >
> >
> > I guess this should work ....
> >
> >
> > Tell me your comments...
> >
> >
> > "Phillip Windell" wrote:
> >
> >> "kris" <(E-Mail Removed)> wrote in message
> >> news:217538BF-5F67-4315-9E57-(E-Mail Removed)...
> >> > Hi Phillip ,
> >> > I guess you dint get my idea,Let me explain.See whenever RDP
> >> > session is initiated i will create virtual network interface and assign
> >> > a
> >> > public ip to it.After the creation of Virtual Network interface ,I will
> >> > forward all the traffic to that public ip which was assigned to the
> >> > virtual
> >> > nic.Its something like having one physical nic with multiple virtual
> >> > nics....
> >> > Tel me your comments on this..?
> >> >
> >> > Otherwise pls suggest me an idea as to how we can achieve my scenario.
> >>
> >> I looked back at the first post to see the original request. There is no
> >> such
> >> "functionality",...what you want cannot be done,...it does not exist.
> >>
> >> --
> >> Phillip Windell
> >> www.wandtv.com
> >>
> >> The views expressed, are my own and not those of my employer, or
> >> Microsoft, or
> >> anyone else associated with me, including my cats.
> >> -----------------------------------------------------
> >>
> >>
> >>
>
>
>