Forum Replies Created
-
Posts
-
Right, this has been resolved thanks to the user ‘ConfGen’, and because I absolutely hate it when I find a forum post online that describes my exact issue, and then doesn’t say how they resolved it, I will detail in this forum post about how it was solved.
In my xen.ini file, I had the line:
fileserver=ndlxenddc1Removing this from the Xen.ini resolved all of the problems with the Tx0 clients, and also meant that the Cx0 clients were ok as well. Turns out that the Tx0 clients got confused with this being set in the xen.ini file, and also being set in the DHCP scope options 161 & 162…
Thank you everyone for your help.
My friend, you are a genius. I can’t believe that it was something as simple as that one line in the .ini file that was causing this problem.
Removed ‘Fileserver=ndlxenddc1’ from my .ini file, and then client connected, getting the fileserver from DHCP Scope options and updated the firmware, and applied the correct .ini files. Also my Cx0 clients also work perfectly with this.
Any ideas? I really think that applying new firmware to the client will solve a lot of the problems.
This is the .ini file it should be applying:
;*************************************************************
;* *
;* This xen.ini file was generated with the *
;* Configuration File Generator 6.2.02 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
BootpDisable=yes
Fileserver=ndlxenddc1;*************************************************************
;* General 2 *
;*************************************************************Locale=English
Device=audio Volume=80;*************************************************************
;* Input Devices *
;*************************************************************Language=Uk
;*************************************************************
;* Time *
;*************************************************************Timeserver=ndlsvrdc01 Timeformat=”24-hour format” Dateformat=dd/mm/yyyy
; If you are using an older version of WTOS code please use:
; TimeZone= ‘GMT’ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=GMT DayLightName=GMTTimeZone=’Greenwich Mean Time’ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”GMT Standard Time” DayLightName=”GMT Daylight Time”
;*************************************************************
;* Network *
;*************************************************************VDIBroker=ndlxenddc1
ConnectionBroker=Default
SignOn=Yes
DomainList=”moneyadvice”;*************************************************************
;* Wireless / 802.1x *
;*************************************************************IEEE8021X=yes network=wired
;*********group option**********
SelectGroup=no
description=”dev” groupname=”dev”
description=”AdvancedUser” groupname=”advanceduser”AutoSignoff=yes Shutdown=yes
ShutDown=turnoffHi ConfGen,
Thank you for the reply. Unfortunately I don’t think the Xenith 2’s are picking up the fileserver correctly like the Xenith 1’s are.
We have the DHCP Option IDs set as:
161 – http://10.1.1.151
162 – /
181 – 10.1.1.151The Xenith 1’s pick that up fine, but not the Xenith 2’s
Regards,
Jack
Hi ConfGen,
I’ve tried adding that to my XEN.ini file, but it has made no difference.
I’ve confirmed again that the Cx0 works perfectly in the same port that i’m testing the Tx0 in.
This is the XEN.ini file:
;*************************************************************
;* *
;* This xen.ini file was generated with the *
;* Configuration File Generator 6.2.02 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
BootpDisable=yes
Fileserver=ndlxenddc1;*************************************************************
;* General 2 *
;*************************************************************Locale=English
Device=audio Volume=80;*************************************************************
;* Input Devices *
;*************************************************************Language=Uk
;*************************************************************
;* Time *
;*************************************************************Timeserver=ndlsvrdc01 Timeformat=”24-hour format” Dateformat=dd/mm/yyyy
; If you are using an older version of WTOS code please use:
; TimeZone= ‘GMT’ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=GMT DayLightName=GMTTimeZone=’Greenwich Mean Time’ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”GMT Standard Time” DayLightName=”GMT Daylight Time”
;*************************************************************
;* Network *
;*************************************************************VDIBroker=ndlxenddc1
ConnectionBroker=Default
SignOn=Yes
DomainList=”moneyadvice”;*************************************************************
;* Wireless / 802.1x *
;*************************************************************IEEE8021X=yes network=wired
;*********group option**********
SelectGroup=no
description=”dev” groupname=”dev”
description=”AdvancedUser” groupname=”advanceduser”AutoSignoff=yes Shutdown=yes
ShutDown=turnoffI tried changing the 161 value to /$, but it ended up meaning that all of the Cx0 clients couldn’t get the XEN.ini file.
This is a really strange issue. Why are the Cx0 clients fine, but the Tx0 ones not? They can obviously pick up the .ini file settings so it can’t be a permissions issue can it?
Ok new twist. I’ve been literally scouring these forums trying to find simular users that have had this issue, and I finally found one that mentioned the DHCP scope options being the issue… and I think they’re are right.
At the moment 161 FTPServer value is an the IP address of the IIS server ‘http://10.1.1.151’, when it is like this, the Tx0 clients don’t get an IP address. If I change value and get rid of the http:// and just have it as the IP ‘10.1.1.151’ then the Tx0 client gets an IP address from DHCP, but doesn’t pull any of the .ini information down.
I’m still testing, but if anyone has any ideas they could share, that would really help. The DHCP scope settings we currently have setup are:
161 FTPServer = http://10.1.1.151
162 FTP Directory = /
181 PNAgent Server List = 10.1.1.151Please note that these settings currently work fine for the Cx0 clients, just not for the Tx0 clients
Thank you for your suggestion, but sorry no that didn’t seem to work.
I wish I could flash the firware on the Tx0 device, but the WYSE USB Firmware tool I don’t think works on the Tx0 devices, or atleast every keyboard command i’ve tried with the device to get it to boot from a USB hasn’t worked.
Any other ideas would be greatly appreciated?
