Policies not applying correctly

  • This topic is empty.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #437
    AvatarKenD
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Hi all,

    Another S10/Citrix problem. We have a few hundred S10s connecting to our PSE4.0 farm, using the PNAgent to present published applications to our users. The farm is split into two zones, one at each location.

    I’ve configured policies to assign users from the relevant subnets to the farm servers at that site. Policy is applied by IP address. However, despite many weeks of trying to get this working, users are still randomly connected to servers in the wrong zone.

    I noticed the interesting article http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=31&mode=&order=0&thold=0 which mentions policies not being applied when using UDP browsing. However, we’ve got our wnos.ini configured to use HTTP browser. Here’s the wnos.ini:


    Autoload=1
    VNCPrompt=0
    MaxVNCD=2
    DomainList=OURDOMAIN
    Seamless=yes
    ScreenSaver=30 Type=1 LockTerminal=1
    Privilege=Low HidePPP=yes HideConnectionManager=yes
    Reconnect=No
    Hide_IP=1
    PnliteServer=192.168.247.202:8888
    Timeserver=192.168.7.205
    TimeZone='GMT + 01:00' ManualOverride=yes daylight=no start=030507 end=100507
    DeskColor="022 058 127"
    DisableDomain=yes
    VNCPrompt=no
    ICABrowsing=http

    I’m in the process of collecting a diagnostic trace for Citrix, as I suspect this may be a PS rather than a Wyse problem, but having seen that note I wondered whether anyone could spot anything wrong with my configuration which would cause the policy to seemingly not be applied?

    #9602
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Ken,

    This file looks fine to me, you can try pointing the terminals at each site to the respective DC’s in the same subnet (really this should make no difference but it will make resolution faster)

    It sounds like a load balancing issue but wait to see what Citrix comes up with,

    Cheers,
    -TT

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.