- This topic is empty.
-
AuthorPosts
-
January 16, 2012 at 2:55 pm #7065
Hi ,
i have a problem configuring NTLM authentication on the Wyse S10 devices.
Let me explain the situation :We have a Windows 2008R2 Standard with remote desktop services installed.
Our thin clients are all Wyse S10.
Firmware Version 7.0.0_30 (upgrade from 6.5…)The strange thing is , NTLM authentication worked just untill last night , when the server was updated with some security updates and SP1.
I think , some of these updates (SP1) broke the NTLM connection…Now what happens is , when the S10 starts connecting it all goes well untill you have to type the user credentials in the NTLM box (where the correct domain is already filled in)
The thin client always says “invalid userid and password” when typing the credentials , but i am 100% sure that the userid and password are correctly inserted!
I noticed this problem already on a thin client which wasn’t updated to 7.0 BUT now , it seems , the updates break the connection…This looks strange to me because what other updates will break the connection..I already checked the registry of the server to check the NTLM authentication and it is set to
network security : Send NTLM response onlyI already tried to audit the NTLM traffic but i am unable to trigger events in
Event Viewer (Local)Applications And Services LogsMicrosoftWindowsNTLMOperationalThis is my wnos.ini file :
autoload=0
PlatformConfig=SClass
Privilege=none
AdminMode=yes Username=xxx Password=xxx
EnableCacheIni=yes;*************************************************************
;* Input Devices *
;*************************************************************Language=fr_be Charset=ISO-8859-1
MouseSpeed=1;*************************************************************
;* Time *
;*************************************************************Timeserver=xxx Timeformat=”24-hour format” Dateformat=dd/mm/yyyy
TimeZone=’GMT + 01:00′ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”W. Europe Standard Time” DayLightName=”W. Europe Daylight Time”;*************************************************************
;* Network *
;*************************************************************Device=Ethernet Speed=”Auto”
SignOn=NTLM ConnectionManager=Hide EnableOK=Yes DisableGuest=yes SaveLastDomainUser=yes
DomainList=”xxx”
AutoSignoff=Yes Shutdown=Yes
ShutdownCounter=0;*************************************************************
;* Display *
;*************************************************************Resolution=1024×768
;Resolution=800×600;*************************************************************
;* General Session *
;*************************************************************SessionConfig=ALL UnmapPrinters=yes Smartcards=yes
FixLicense=yes
TCXLicense=xxxx-xxxxx-xxxxx-xxxxx-xxxxx;*************************************************************
;* RDP *
;*************************************************************ScreenSaver=15 LockTerminal=1 type=1
;
;- RDP Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=RDP
Host=xxx
Description=”xxx”
Icon=xxx.bmp
AutoConnect=yes
Reconnect=no
Fullscreen=yes
Logon_Mode=user-specified
Username=$UN
Password=$PW
Domainname=xxx
Mapdisks=no
LocalCopy=noinclude=$mac.ini
Can someone put me in the right direction as i am out of options ?
January 16, 2012 at 4:16 pm #21637Why do you think you should change anything in your Thin Client environment, when everything was working before you modified your server site?
CG
January 16, 2012 at 4:57 pm #21638Maybe someting fundamental needs to change in my wnos file ?
January 17, 2012 at 7:52 am #21639No, it is your server environment.
CG
January 17, 2012 at 10:08 am #21645Ok ,
but why do i see then , in the newest firmware version 7.1.033 , in the fixes topic :
CIR58894/TIR59503: NT LAN Manager (NTLM) Authentication fails against a Window Server 2008 R2 Domain Controller.
?January 17, 2012 at 3:25 pm #21650OK, once again. You said that everything was working before you installed latest MS hotfixes. Now it is no longer working.
Mayb there is an issue in WTOS but it worked before the installation of the HF.CG
-
AuthorPosts
- You must be logged in to reply to this topic.