[Storefrant 2203 CU3 replication fails]

Finally i got a synced store, but...

 

I did a backup of my config from node1

Restore on node2

reseted node2 to unconfigured (the trick is, all certs keep in place)

replicated from node1 to node 2 (same failed -node1-, success  -node2-  as before)

resynced once again and both sides are ok

when adding a new store, the first sync fails...

... but the 2nd succeeds.

 

citrix case 82136020 if someone needs a reference 

[Storefrant 2203 CU3 replication fails]

Hi Carl,

 

weither a GPO  modifying local admins nor someting else.

[Storefrant 2203 CU3 replication fails]

Hi Team,

 

i got 2 new server 2019 incl 2023-07 up and running.

No antivirus in place yet.

Installed storefront on both servers.

Applied an internal wildcard cert for iis.

Configured the first storefront and checked functionality.

Went to my second storefront and added to existing group.

Giving the name and token of my first server.

Secondary node say's finished successful.

Primary gives an error with unsuccessful sync.

 

So what i did:

Double-checked DNS / DHCP and reverse Lookup zones

Disabled ip v6

Reading nearly every article advised by anty GOOGLE!

 

As this is my first storefront install for this year and also my LAB installation throws the same error, I'm asking my self ift this could be related to the latest protocol modifications by Microsoft.

 

Any ideas welcome.

THX Andreas

[ADC crashes with 13.0-90.11 and 13.1-45.63]

New Firmware is plubic

[ADC crashes with 13.0-90.11 and 13.1-45.63]

We received a private fix today. You have to reference NSHELP-35288 and you will get the download link
 

[ADC crashes with 13.0-90.11 and 13.1-45.63]

As i'm using http2 streams, it is not possible to drop this function.

But it is a very useful hint if you don't require this function.

 

thx very much

[ADC crashes with 13.0-90.11 and 13.1-45.63]

Hi Guys,

 

after upgrading our netscalers to lates firmware we can see all systems crashing.
Affected are VPXs and MPXs.

TM, CS and Gateway - traffic cause immediately this behavior.

We also open a ticket with citrix support and if needed we will share the ticket number for faster case tracking.

 

Any idea welcome

thx Andreas

[querying SNI header does not work as expected]

Just checked:

 

[replace netscaler tab titel from "Citrix ADC - Configuration" to hostname or given name]

Is there a way to replace netscaler browser tab titel from "Citrix ADC - Configuration" to hostname or given name.

Has anyone a working rewrite pol with a short explantation?

So I want to see in the browser tab which netscaler I'm working on.

 

thx

Andreas

 

[AAA Client Handler: Found extended error code 589827, ReqType 16386 request /AGServices/Discover]

It's working with latest Firmware, i.e. document is found again.

And we had a 2nd issue with proxy settings.

Please check your proxy with netsh winhttp show proxy.

If no special requirements are given it should be: "DirectAccess"

[Citrix Gateway --> ICA Connections...does not show anymore the UDP based user connections]

Just checked if it is a gui related problem.

SNMP also does no loger report session when udp

 

[Citrix Gateway --> ICA Connections...does not show anymore the UDP based user connections]

Same with 13.0.89.7

Has anyone already opend a case?

 

[AAA Client Handler: Found extended error code 589827, ReqType 16386 request /AGServices/Discover]

I got a workaround for this issue.

Export your .rc file from the portal page and send via email to the mobile devices.

If it's not opening with the workspace app you con use the SHARE WITH option and select the workspace app.

 

hop this hint wil help.

[AAA Client Handler: Found extended error code 589827, ReqType 16386 request /AGServices/Discover]

Hi Guys,

 i'm getting a error "AAA Client Handler: Found extended error code 589827, ReqType 16386 request /AGServices/Discover" on Netscaler 13 latest patch with storefront 2022cu1 in the back.

Every OS is working fine but mobile (android and iOS)

I only found a very old hint within the support. and i tried to turn off ica proxy as mentioned.

 

- NOT WORKING -

 

I'm pretty sure the error is sitting in front of the computer.

If anybody got's a hint, it would be perfect.

 

Thx, Andreas

[Netscaler Gateway not working with firefox 105 or chrome 106]

As no more tickets are raising up i guess ist's solved.
So the only change was not tu use global session settings.

For me it's sounds like the problem with the intranet ip, where global settings are ignored.

I'm going to check all global settings in place and replace them with settings in session profiles.

 

THX to all for your perfect BRAIN dumps.

[Netscaler Gateway not working with firefox 105 or chrome 106]

Hi Carl,

I'll keep you informed,

 

[Netscaler Gateway not working with firefox 105 or chrome 106]

Just checking both time out boxes seems to work

[Netscaler Gateway not working with firefox 105 or chrome 106]

DUO is configured as the only primary factor.
I see that the logon is signed on DUO and on the ns side.
I'll give the idea with the timeouts a chance.

I'm still thinking about the browser versions.

What about  disabling FEO globally, just for testing.

[Netscaler Gateway not working with firefox 105 or chrome 106]

Looping the landing page begun after autoupdates for chrome /edge and firefox.
Clearing the caches helps (but only onetime).

Netscaler is running on 13.0.85.19, witch was fine since may.

No config change at the gateway side.

No config change at the duo side.

Both logs, duo and ns have no issues.

Timesync is checked.

Actually i'm going to check all browser versions in question.

[Netscaler Gateway not working with firefox 105 or chrome 106]

Hi Carl,

 

yes, it is default global.

 

[Netscaler Gateway not working with firefox 105 or chrome 106]

Hi guys, i've got a problem with latest browser releases and the netscaler gateway using DUO as primary authentication.
After browser updates you can sign in but you will be redirected to the logon landing page.

DUO log is fine and even the ns.log.
If you clear files and cookies you can login once.

 

Any idea welcome.

THX Andreas

[file too large]

Trying to update to signature 89 results in "file too large"

Does anyone know how to handle this error?

 

thx Andreas

[No IntranetIP available. Please try login later.]

Did you turn off global or per session policy?

My experience was to turn off per session policy.

Actually I'm using release 13 85.19.

And have you checked to failover after your last update?

If nothing works for you, try to configure a network not in place to provide ip addresses.

 

 

[No IntranetIP available. Please try login later.]

I changed every session profile to NS / OFF.

As  I made bad experiences doing this global.

After changing everthing works perfect.

 

[Gateway Callback fails after upgrade to Storefront 2203]

@Miguel Contreras

 

I'm running on ADC 13 and 13.1 all latest firmware