Forum Replies Created
-
AuthorPosts
-
I had this issue trying to use “DisableEditDomain=yes” under the advanced configuration like you mentioned and I found I had to include another parameter for it to work, so I ended up needing to do “SignOn=NTLM DisableEditDomain=yes”.
Maybe the “ConnectionManager=hide” also requires the “SignOn” field to be defined?
I performed the upgrade again from 1.4 to 3.0 and it was successful this time around. I guess the service stopping broke it before, good call.
I’ll try again without the services part I suppose. The Dell rep I spoke to said 1.4 to 3.0 is supported.
For our ThinOS clients we just use the direct RDP configuration and point it to the round-robin name (RDS.DOMAIN.CORP). Seems to work better than using the RD connection broker setup, for us anyway.
8.0_512 – Does not work with our configuration. Once you log into the WYSE using NTLM it does nothing. It is supposed to auto connect via RDP to terminal services.
8.0_037 – Random green screen error I cannot make sense of. I’ll attach the error.
I have already tested those C10LE versions was unsuccessful.
Fix that I found:
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
DWORD name: DisableStrictNameChecking
DWORD value: 1Basically in 8.0 the WYSE would do the following:
Lookup: EXAMPLE_LAN, EXAMPLE_LAN resolves to AD01, connect to: \\AD01\IPC$ and it works.
In 8.2+ the WYSE will do the following:
Lookup: example.com, connect to \\example.com\IPC$, does not work in 2012R2 because the server name is not \\example.com\, it is AD01 so it is rejected because security and stuff.
I opened a ticket with Dell to see if this will ever be fixed in newer firmware, but I doubt it.
Yes, it is mostly just a copy.
Did some more digging this morning and I’ve found the issue to be with 2012R2 domain controllers. It appears when the WYSE talks to a 2012R2 domain controller and performs the NTLMSSP_NEGOTIATE, it fails because of the error: STATUS_DUPLICATE_NAME. I have no idea what this means, but authentication works OKAY talking to 2008R2 domain controllers, hence why it only works a little of the time.
I’ll update when I find out more.
-
AuthorPosts