RDP between sites.

[Guest Fred]

Hi, i'm looking to put a solution together which will provide a RDP

connector at a remote site, so the staff there can use a database.

I'm trying to calculate the amount of bandwidth i'm going to need, and in

the process trying to understand exactly how RDP works.

 

Am i correct in saying that RDP uses an asymentrical type connection, in

that the remote site will be downloading more bits than uploading.

Surely only the keystrokes are uploaded by the remote site to the T/S

server, and then the download of the "screen" after the keystrokes have

taken affect will require a quick upload.

 

Is this correct?

[Guest Benny Tritsch [MVP]]

Re: RDP between sites.

 

This is correct, sending the user interface element from server to client

requires more RDP bandwidth than keystrokes and mouse events from client to

server. Things get even worse when a printer is physically attached to your

client and is mapped into the remote user session. In this case the print

data stream is transmitted from server to client as well.

 

Benny

 

--

Bernhard Tritsch

MVP Windows Server - Terminal Server

Author of "Windows Server 2003 Terminal Services", MS Press

http://www.wtstek.com

 

"Fred" <fred@nospam.esd.com> wrote in message

news:5D3562B2-3FC3-47FC-9CF7-5D812D2C150D@microsoft.com...

> Hi, i'm looking to put a solution together which will provide a RDP

> connector at a remote site, so the staff there can use a database.

> I'm trying to calculate the amount of bandwidth i'm going to need, and in

> the process trying to understand exactly how RDP works.

>

> Am i correct in saying that RDP uses an asymentrical type connection, in

> that the remote site will be downloading more bits than uploading.

> Surely only the keystrokes are uploaded by the remote site to the T/S

> server, and then the download of the "screen" after the keystrokes have

> taken affect will require a quick upload.

>

> Is this correct?

[Guest Fred]

Re: RDP between sites.

 

many thanks for the reply Benny,

 

is there anyway to quantify the bandwidth printing will take up or is that

an unknown quantity, that will take as much as it can get?

plus also are there any ball park figures as to how much bandwidth RDP will

user per session?

I'm being told that it's around 50Kb per session, others have said 50KB per

session.....it would be nice to find out a true figure on this.

 

TIA

"Benny Tritsch [MVP]" <bt@nospam.web.de> wrote in message

news:uR0CUe6JIHA.4688@TK2MSFTNGP06.phx.gbl...

> This is correct, sending the user interface element from server to client

> requires more RDP bandwidth than keystrokes and mouse events from client

> to server. Things get even worse when a printer is physically attached to

> your client and is mapped into the remote user session. In this case the

> print data stream is transmitted from server to client as well.

>

> Benny

>

> --

> Bernhard Tritsch

> MVP Windows Server - Terminal Server

> Author of "Windows Server 2003 Terminal Services", MS Press

> http://www.wtstek.com

>

> "Fred" <fred@nospam.esd.com> wrote in message

> news:5D3562B2-3FC3-47FC-9CF7-5D812D2C150D@microsoft.com...

>> Hi, i'm looking to put a solution together which will provide a RDP

>> connector at a remote site, so the staff there can use a database.

>> I'm trying to calculate the amount of bandwidth i'm going to need, and in

>> the process trying to understand exactly how RDP works.

>>

>> Am i correct in saying that RDP uses an asymentrical type connection, in

>> that the remote site will be downloading more bits than uploading.

>> Surely only the keystrokes are uploaded by the remote site to the T/S

>> server, and then the download of the "screen" after the keystrokes have

>> taken affect will require a quick upload.

>>

>> Is this correct?

>

>

[Guest Benny Tritsch [MVP]]

Re: RDP between sites.

 

There is no true figure. In bursts, RDP will consume all the bandwidth it

can get. If you have a big print job it may create problems on a WAN. This

is why I recommend using network products that allow protocol priorisation

and bandwidth throttling. The figures you refer to are derived from

collecting average numbers you get when watching a large TS environment over

a long time, it's only statistics. But the RDP bursts can be really painful

in networks without protocol priorisation.

 

Benny

 

--

Bernhard Tritsch

MVP Windows Server - Terminal Server

Author of "Windows Server 2003 Terminal Services", MS Press

http://www.wtstek.com

 

"Fred" <fred@nospam.esd.com> wrote in message

news:8AFCB03C-9CC9-4EA6-B434-0CDF37983A09@microsoft.com...

> many thanks for the reply Benny,

>

> is there anyway to quantify the bandwidth printing will take up or is that

> an unknown quantity, that will take as much as it can get?

> plus also are there any ball park figures as to how much bandwidth RDP

> will user per session?

> I'm being told that it's around 50Kb per session, others have said 50KB

> per session.....it would be nice to find out a true figure on this.

>

> TIA

> "Benny Tritsch [MVP]" <bt@nospam.web.de> wrote in message

> news:uR0CUe6JIHA.4688@TK2MSFTNGP06.phx.gbl...

>> This is correct, sending the user interface element from server to client

>> requires more RDP bandwidth than keystrokes and mouse events from client

>> to server. Things get even worse when a printer is physically attached to

>> your client and is mapped into the remote user session. In this case the

>> print data stream is transmitted from server to client as well.

>>

>> Benny

>>

>> --

>> Bernhard Tritsch

>> MVP Windows Server - Terminal Server

>> Author of "Windows Server 2003 Terminal Services", MS Press

>> http://www.wtstek.com

>>

>> "Fred" <fred@nospam.esd.com> wrote in message

>> news:5D3562B2-3FC3-47FC-9CF7-5D812D2C150D@microsoft.com...

>>> Hi, i'm looking to put a solution together which will provide a RDP

>>> connector at a remote site, so the staff there can use a database.

>>> I'm trying to calculate the amount of bandwidth i'm going to need, and

>>> in the process trying to understand exactly how RDP works.

>>>

>>> Am i correct in saying that RDP uses an asymentrical type connection, in

>>> that the remote site will be downloading more bits than uploading.

>>> Surely only the keystrokes are uploaded by the remote site to the T/S

>>> server, and then the download of the "screen" after the keystrokes have

>>> taken affect will require a quick upload.

>>>

>>> Is this correct?

>>

>>

>

[Guest Fred]

Re: RDP between sites.

 

ok, so printing is going to be an issue,

can a T/S client / RDP connection be setup to print locally?

Though i guess to answer my own question, the data being printed will

originate from the T/S server,

so if the client did have some way of printing locally, the data in the

print queue will still travel up the pipe to the remote printer.

 

 

"Benny Tritsch [MVP]" <bt@nospam.web.de> wrote in message

news:OY1oOB9JIHA.4584@TK2MSFTNGP03.phx.gbl...

> There is no true figure. In bursts, RDP will consume all the bandwidth it

> can get. If you have a big print job it may create problems on a WAN. This

> is why I recommend using network products that allow protocol priorisation

> and bandwidth throttling. The figures you refer to are derived from

> collecting average numbers you get when watching a large TS environment

> over a long time, it's only statistics. But the RDP bursts can be really

> painful in networks without protocol priorisation.

>

> Benny

>

> --

> Bernhard Tritsch

> MVP Windows Server - Terminal Server

> Author of "Windows Server 2003 Terminal Services", MS Press

> http://www.wtstek.com

>

> "Fred" <fred@nospam.esd.com> wrote in message

> news:8AFCB03C-9CC9-4EA6-B434-0CDF37983A09@microsoft.com...

>> many thanks for the reply Benny,

>>

>> is there anyway to quantify the bandwidth printing will take up or is

>> that an unknown quantity, that will take as much as it can get?

>> plus also are there any ball park figures as to how much bandwidth RDP

>> will user per session?

>> I'm being told that it's around 50Kb per session, others have said 50KB

>> per session.....it would be nice to find out a true figure on this.

>>

>> TIA

>> "Benny Tritsch [MVP]" <bt@nospam.web.de> wrote in message

>> news:uR0CUe6JIHA.4688@TK2MSFTNGP06.phx.gbl...

>>> This is correct, sending the user interface element from server to

>>> client requires more RDP bandwidth than keystrokes and mouse events from

>>> client to server. Things get even worse when a printer is physically

>>> attached to your client and is mapped into the remote user session. In

>>> this case the print data stream is transmitted from server to client as

>>> well.

>>>

>>> Benny

>>>

>>> --

>>> Bernhard Tritsch

>>> MVP Windows Server - Terminal Server

>>> Author of "Windows Server 2003 Terminal Services", MS Press

>>> http://www.wtstek.com

>>>

>>> "Fred" <fred@nospam.esd.com> wrote in message

>>> news:5D3562B2-3FC3-47FC-9CF7-5D812D2C150D@microsoft.com...

>>>> Hi, i'm looking to put a solution together which will provide a RDP

>>>> connector at a remote site, so the staff there can use a database.

>>>> I'm trying to calculate the amount of bandwidth i'm going to need, and

>>>> in the process trying to understand exactly how RDP works.

>>>>

>>>> Am i correct in saying that RDP uses an asymentrical type connection,

>>>> in that the remote site will be downloading more bits than uploading.

>>>> Surely only the keystrokes are uploaded by the remote site to the T/S

>>>> server, and then the download of the "screen" after the keystrokes have

>>>> taken affect will require a quick upload.

>>>>

>>>> Is this correct?

>>>

>>>

>>

>

>