Jump to content
Updated Privacy Statement

loadbalancing port ranges


Recommended Posts

Sean,

You should be able to do this using an ANY vserver and then restrict the ranges using policies. See this KB article:

http://support.citrix.com/article/CTX129192

That will at least take care of the listening vservers. As far as I know you would have to add the services in the same old way if you are looking to have the same port ranges on the other end.

Link to comment
Share on other sites

  • 7 years later...
On 03/10/2011 at 6:31 PM, Adam Comerford said:

Sean,

You should be able to do this using an ANY vserver and then restrict the ranges using policies. See this KB article:

http://support.citrix.com/article/CTX129192

That will at least take care of the listening vservers. As far as I know you would have to add the services in the same old way if you are looking to have the same port ranges on the other end.

Thank you for all these details. I am fairly new to the netscaler world. My question is, do I need to bind the vserver  after configuring to listen to all ports to the service groups on the ports I am interested. This will create a lot of admin work, I am still confused. Ports I am interested:

https://docs.microsoft.com/en-us/previous-versions/mim/ee534892(v=ws.10)

 

TCP/UDP 135 (RPC EPMapper)
TCP/UDP 389 (LDAP, LDAP Ping)
TCP 636 (LDAP over SSL)
TCP 3268 (GC)
TCP 3269 (GC SSL)
TCP/UDP 53 (DNS)
TCP/UDP 88 (Kerberos)
TCP Dynamic (RPC)
TCP/UDP 464 (Kerberos Change/Set Password)
TCP 445 – (CIFS/ MICROSOFT-DS)


To facilitate WMI communication, you will also need to make sure the following ports are open between the server running the FIM Service and the server running the FIM Synchronization Service:

TCP/UDP 135 (RPC EPMapper)
TCP 135 (RPC EPMapper)
TCP 5725
TCP 5726
TCP 5000-5001 Dynamic RPC ports (PCNS)
TCP 57500-57520 Dynamic RPC ports (AD MA)

 

Screen Shot 2019.png

Link to comment
Share on other sites

  • 1 year later...
20 minutes ago, Hakan Polatli1709158891 said:

After binding a service with wildcard port configured, how Citrix ADC selects the destination port when communicating to backend server? I assume it uses the destination port of the original client request at the front-end side.

I tested on my lab. Yes, it does select destination port of the original client request at the front-end side when communicating with the back-end server.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...