Seamless applications are scaled as per the monitor DPI settings. You can scale the display to the required resolution based on the monitor DPI settings.
High DPI support is available in both application and desktop session. Using this feature, you can scale the sessions to the monitor DPI settings or use the native session’s resolution. You can now use multiple monitors with different DPI settings. Starting with this release, Citrix Receiver for Windows provides improved support for handling high DPI monitors in a session. Just remember when you setup your trunks they are not limiting what vlans can traverse them.Feature enhancement is included in Citrix Receiver 4.10 Installing and using Receiver 4.10 resolved the issue You can now assign vlans to any switch any port any where. Step 4: Setup classless routing and give your 3960G a default gateway On a similar note don't forget to setup the ip helper address so your clients on the various subnets/vlans can locate your DHCP server. I strongly suggest you setup a vlan per subnet. Remember that every vlan you setup give your 3960G an IP on, this will be the clients default gateway for that vlan. Step 2: Create all your vlans on your 3960G. It's very annoying when you have a VTP client member rewrite all of the other switches VLAN tables because its VTP version number is higher. Be sure to rename the VTP domain from whatever you have currently this way all the switches are reset. Step 1: setup a VTP domain, make the 3950G the server and the others clients with whatever password you want to use. What your trying to do is not port SPANing (if I understand what your saying) but setup vlans and have your "core" switch perform all your inter-vlan routing for you. Thanks in advance for any help that I get with this! Monitor session 1 destination fastethernet 0/ Monitor session 1 destination remote vlan Second, do I have to use RSPAN, since my VLANs cross multiple switches? Like so: My first question is whether or not this is good practice, and if there is any reason why I should NOT do this. I realize that only 2 SPAN sessions are supported on my switches, and that I will have to spread this across the 4 switches to cover each VLAN. I do not have any room on the core switch to set these up, so I would like to span each VLAN to ports on my L2 switches. Our core router / switch (Cisco 3960G - 元) is where all of the VLANs are defined, and where the routed interfaces for each VLAN reside. I would like to configure a span port for each of our VLANs. The L2 switches are all trunked to the one 元 switch (core). Anyway, I have 4 L2 switches (Cisco 3560's) and one 元.
0 kommentar(er)
