Re: Ports used by Remotedesktop
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 May 2005 15:01:37 -0700
I could also be way off here, but surely rdp uses port 3389 for
inbound traffic and a dynamic port between 1024 and 65525 for
outbound traffic (as seen from the Terminal Server)?
Normally, firewalls understand this, but maybe yours doesn't?
This is from my XP client (vnxppro), which has an active TS session
open to my Terminal Server:
C:\>netstat
Active Connections
Prot. Local address Foreign address State
TCP vnxppro:1396 192.168.0.120:3389 ESTABLISHED
So your entry:
TCP vaio516.domain.xx:1132 wts:3389 ESTABLISHED
seems perfectly reasonable. The other 2 entries are more suspect, I
think.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"Ole Weigelt" <o.weigelt@xxxxxxxxxxxxxx> wrote on 18 maj 2005 in
microsoft.public.windows.terminal_services:
> I know about that one, but these ports change every time I
> connect to the server. Maybe that is the problem?
>
>
> "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> schrieb
> im Newsbeitrag
> news:4FF7207C-4E1F-4CA8-ACEA-F2D076FAAE88@xxxxxxxxxxxxxxxx
>> I could be way off, but when I did a search for TCP Port 1132
>> one of the first hits was for this:
>>
>>
> http://securityresponse.symantec.com/avcenter/venc/data/w32.mydoo
> m.ba@xxxxxxx
>>
>> --
>> Patrick Rouse
>> Microsoft MVP - Terminal Server
>> http://www.workthin.com
>>
>>
>> "Ole Weigelt" wrote:
>>
>> > I am just trying to use port 3389. This is what TCPView
>> > shows:
>> >
>> > Process ID Protocol Local Address
>> > Remote Address State
>> > mstsc.exe: 904 TCP VAIO516:1132
> VAIO516:0
>> > LISTENING
>> > mstsc.exe: 904 TCP vaio516.domain.xx:1132
> wts:3389
>> > ESTABLISHED
>> > mstsc.exe: 904 UDP VAIO516:1134
>> > *:*
>> >
>> > Sometimes there is even a fourth port open on the client's
>> > side.
>> >
>> > The bottom line is that it seems not enough to open port 389
>> > on the firewall. The connection does not work. A test with
>> > VNC showed taht it
> can
>> > work. So it does not seem to be a firewall problem.
>> >
>> > Any ideas?
>> >
>> > Thanks
>> >
>> > Ole
>> >
>> > "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> > schrieb im Newsbeitrag
>> > news:D3ED8D30-4D95-4F9D-9C9D-3541FFDA8802@xxxxxxxxxxxxxxxx
>> > > What other prost do you see being used. RDP uses ONLY
>> > > 3389. If you
> are
>> > also
>> > > using Remote Desktop Web Connection, this uses port 80, or
>> > > whatever
> prot
>> > you
>> > > have it advertising on.
>> > > --
>> > > Patrick Rouse
>> > > Microsoft MVP - Terminal Server
>> > > http://www.workthin.com
>> > >
>> > >
>> > > "Ole Weigelt" wrote:
>> > >
>> > > > Hello Everybody,
>> > > >
>> > > > I am trying to set up a firewall rule. RDP uses port
>> > > > 3389. So far.
>> > > >
>> > > > But now, the connection has three open ports, two TCP and
>> > > > one UDP
> and my
>> > > > firewall blocks the RDP traffic with only port 3389
>> > > > opened.
>> > > >
>> > > > Can anybody tell me what to do?
>> > > >
>> > > > Thanks for reading
>> > > >
>> > > > Ole Weigelt
.
- References:
- Ports used by Remotedesktop
- From: Ole Weigelt
- RE: Ports used by Remotedesktop
- From: Patrick Rouse
- Re: Ports used by Remotedesktop
- From: Ole Weigelt
- Re: Ports used by Remotedesktop
- From: Patrick Rouse
- Re: Ports used by Remotedesktop
- From: Ole Weigelt
- Ports used by Remotedesktop
- Prev by Date: Re: Printing to a USB Dell AIO-922
- Next by Date: Re: Log on Interactively
- Previous by thread: Re: Ports used by Remotedesktop
- Next by thread: What will be new in Longhorn TS?
- Index(es):
Relevant Pages
|
Loading