- This topic is empty.
-
Posts
-
Hi all,
We’re currently using the Wyse Xenith Cx0 clients for 200+ users in our company, the issue now is though that this model has been discontinued.
We’ve purchased a new Xenith 2 Tx0 client for testing, but for some reason I can’t get it to aquire an IP via DHCP. The WYSE terminal will boot, go to loading it’s IP from DHCP, state that it will restart after 5 seconds to pick up new configuration files, and then loop with the same message.
I have to cancel the network check with CTRL + ESC to view the admin settings, but when I check the admin settings, it has picked up what I believe are the exact same config settings that the current Cx0 clients use, but then has a loop back IP of 127.0.0.1 so I’m at a bit of a loss.
The event log on the client states the following:
Looking up WDM server by DNS Hostname…
DNS sendto error: Network is unreachable…
DNS/WINS can’t resolve [wdmserver]…
Looking up WDM server by DNS SRV record…
DNS sendto error: Network is unreachable
DNS/WINS can’t resolve [_wdmserver._tcp.domain.net]
If I statically assign the Tx0 an IP, then it works perfectly and I can connect it to the Citrix Xen Desktop. i can’t summise if this is a DHCP issue, or a firmwae issue with the client? The firmware version of the Tx0 client is 2.0_017, and there is an updated version available being the 2.0_104, but I don’t have any idea how to flash this onto the device.We use the Wyse Xenith Manager through Citrix Desktop Studio, but I don’t quite know how to get the new firmware version imported into it, and how to only get the Tx0 to pull it down (not the Cx0 clients)
Any assistance would be greatly appreciated.
Regards,
I had a few similar issues with mine when I was testing them and was advised to try the following in my .ini which seem to sort it. not exactly the same as what you have but similar.
EnableNetworkTest=no
Device=Ethernet Speed=”Auto”
BootpDisable=yes
RapportDisable=yes
WDMService=no
DhcpExpire=ShutdownNot 100% sure it will help but worth a shot!
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?
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
with my xen.ini file in the wnos folder off the FTP Site which uses anonymous permissions
I 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?
BishopFlemming is right.
BootpDisable=yes parameter should fix you issue, if a Xenith works fine on the same network port.CG
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=turnoffRight, 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.
- You must be logged in to reply to this topic.