Forum Replies Created
-
Posts
-
Haven’t seen that error at all. Have you tried a factory reset?
I’d be happy to test against my policies. Send me an email and your Citrix broker URL.
Yes, ours works just like the video.
Silly question, you’re testing from an external connection and not from your corporate network correct? Internal our same URL just uses the Dell username and password and LDAP when left on the “Default” authentication type in WMS. Only when going through the gateway from external internet will you get a prompt for MFA.
Here’s one more, again I don’t know your full setup so just throwing these out as something to check.
https://support.citrix.com/article/CTX134965
Came across this, I know its older article, but could be something simple as #4, Time settings and session timeouts does not match across servers
https://support.citrix.com/article/CTX201985
Not much
Authenticate to broker and I have a default domain though I don’t think that’s necessary with MFA.
Under session settings
Idle 120
Inactive 120
Lock 0
Enable Auto log off
No configuration for 3rd Party and SmarCard sections.
Pointing it to a different store and having the issue go away tells me it’s a store configuration and not ThinOS. If it was a ThinOS issue it should occur regardless of the store you’re pointing to, don’t you think?
Sounds to me like something is different in the storefront configurations then. I know you say they’re identical but I’d take another look really closely.
Anything in the logs from the storefront server? Might be worth a packet capture and analysis to see which side of the conversation is initiating a time out?
I can understand this must be frustrating and I can only provide what works for me in my organization. It’s likely something that differs between our infrastructure configuration.
just thinking out loud here, doesn’t happen in your main central data centers but it does in the mills (branch offices I’m guessing). Are those “branch” location connected “internally” through a GRE tunnel? Any WAN acceleration between them? That can all add to packet overhead, we’ve had a few remote location going across a GRE tunnel where we’ve dropped the MTU size in WMS from the default of 1500 to 1340 and that corrected some connectivity issues for those locations.
Again, not the same situation and I don’t know your infrastructure but we found the issue through deep packet inspection and found oversized packets being fragmented and one side of the conversation would then stop. Lowering the MTU from default helped correct it. Also allowing UDP 1494 and 2598 has helped internally as well.
This same setting works on 5470 mobiles to a single URL, so it works internally to storefront and externally through netscaler. Have you tried the setting to see if it works regardless of your setup?
This is how my broker settings have been since the beginning. The only thing missing from the screenshot is my broker URL but it’s the same as you would use externally.
Tested the following scenarios:
- 5470 mobile undocked but on power plug, integrated camera has no issue.
- 5470 mobile undocked but on power with Logitech C920 USB webcam and no issue
- 5470 mobile docked on WD19 via USB-C using integrated webcam and video slows down
- 5470 mobile docked on WD19 via USB-C using Logitech C920 plugged into dock and video slows down
I’m starting to wonder if I have the correct power brick for the WD19 dock in use and if not enough power is getting to the 5470 through the USB-C because of an underpowered power pack. Will check the specifics for the WD19 power I may be using the wrong power brick since I have lots going on in my basement office since the pandemic started.
more to come…
