Hi Folks
I am trying to get my head around how to poke holes in a router access
list with a Firewall feature set (1600 series) to allow a Win2k terminal
server client to access a remote TS. From the packet decode the server
uses TCP =3389, but the client grabs a number in the range1560 upwards
Terminal Server:
remote desktop protocol (rdp) protocol 27
tcp 3389
tcp 1503
Citrix (doesn't require T/S stuff to be opened):
tcp 1494 (in)
udp 1604 (in/out)
tcp/udp 1023-65535 (out)
Both info was found from each vendor's knowledge base (T/S in TechNet or ,
Citrix on Citrix.com), but I keep a
Hi Edmund
This is how I am doing. I have port 3389 open on the
firewall and I use TS web client on a web site and I
access terminal server thru web.
u can down load the client from microsoft
--- Edmund Woltynski wrote:
Hi Folks
I am trying to get my head around how to poke holes
in a
Russell Lusignan wrote:
I assume your firewall is NAT'ng right? Make sure that you specify a
source
port range of 1-65535 and a destionation port of 3389. TCP randomly
selects
the source port number when a session starts, so if you are filtering on
source port 3389 and destination port
4 matches
Mail list logo
