Comments on: WYSE terminal causing DHCP issues http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/ I know people from the future. Ask me anything. Tell me what you know. Tue, 06 Jul 2010 20:33:09 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: joelgibby http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-15986 joelgibby Tue, 06 Jul 2010 20:33:09 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-15986 The only way I've been able to keep things running is by setting a longer lease time and constantly reminding users to power off the devices at the end of the day. If you're using a windows DHCP server, make sure to turn on conflict detection (sends a ping to the address before it's offered and marks it in the table as in use if there's a reply).<br><br>Not a solution, but a workaround until we move to a newer platform without these problems. WYSE wasn't much help. I got bounced around and was told it wasn't a WYSE issue each time. I finally gave up and worked around it myself. The only way I've been able to keep things running is by setting a longer lease time and constantly reminding users to power off the devices at the end of the day. If you're using a windows DHCP server, make sure to turn on conflict detection (sends a ping to the address before it's offered and marks it in the table as in use if there's a reply).

Not a solution, but a workaround until we move to a newer platform without these problems. WYSE wasn't much help. I got bounced around and was told it wasn't a WYSE issue each time. I finally gave up and worked around it myself.

]]> By: cacka2it http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-15984 cacka2it Tue, 06 Jul 2010 20:13:55 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-15984 Joel, Did you find a solution to this problem? I have not had DHCP issues here until I installed these Wyse thin Clients (C10LE). So I am wondering if this is a problem with the Thin Clients or with the way they are expecting DHCP to be enabled. Joel, Did you find a solution to this problem? I have not had DHCP issues here until I installed these Wyse thin Clients (C10LE). So I am wondering if this is a problem with the Thin Clients or with the way they are expecting DHCP to be enabled.

]]> By: Tim http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-15206 Tim Fri, 30 Apr 2010 11:57:47 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-15206 Hello Everyone. In dealing with Wyse Winterms I am experiencing PXE and DHCP issues. (We are not using PXE.) I noticed the thin clients grab an IP address during PXE and a second address when the OS boots. On all but one of my sites the PXE IP address has a 5 minute lease. However on my problem site the PXE lease is the same as the OS IP lease. The result is I use twice the number of IP addresses, and eventually run out of addresses in my DHCP pool. I could take the easy way out and allocate more IP addresses. But I do not want to. We are trying to get a Rapport server up, but it is proving very frustrating. It is my understanding Rapport is the only way to configure or shut off PXE on Wyse thin clients. Unfortunately our Wyse thin clients are no longer supported and Wyse refuses to offer any help. By the way, anyone have experience with HP thin clients? I'm thinking of switching vendors. Hello Everyone. In dealing with Wyse Winterms I am experiencing PXE and DHCP issues. (We are not using PXE.) I noticed the thin clients grab an IP address during PXE and a second address when the OS boots. On all but one of my sites the PXE IP address has a 5 minute lease. However on my problem site the PXE lease is the same as the OS IP lease. The result is I use twice the number of IP addresses, and eventually run out of addresses in my DHCP pool. I could take the easy way out and allocate more IP addresses. But I do not want to.

We are trying to get a Rapport server up, but it is proving very frustrating. It is my understanding Rapport is the only way to configure or shut off PXE on Wyse thin clients.

Unfortunately our Wyse thin clients are no longer supported and Wyse refuses to offer any help.

By the way, anyone have experience with HP thin clients? I’m thinking of switching vendors.

]]> By: Ben http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-14829 Ben Wed, 21 Apr 2010 08:12:12 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-14829 http://geekswithblogs.net/dlussier/archive/2006/10/28/95319.aspx perhaps this is in some way related? Not had a chance to check. Ben http://geekswithblogs.net/dlussier/archive/2006/10/28/95319.aspx perhaps this is in some way related?

Not had a chance to check.

Ben

]]> By: Ben http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-14828 Ben Wed, 21 Apr 2010 08:10:10 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-14828 Hi, We seem to face a lot of similar IP issues with the WYSE, we have a mixture of PC and thin clients on our network. The WYSE thin clients seem to have problems with DHCP and picking up duplicated IP... none of the other thin clients experience this problem so this makes me think there is something wrong with the WYSE firmware? Be interested to know if WYSE have come up with any comments on these issues? Ben Hi,

We seem to face a lot of similar IP issues with the WYSE, we have a mixture of PC and thin clients on our network. The WYSE thin clients seem to have problems with DHCP and picking up duplicated IP… none of the other thin clients experience this problem so this makes me think there is something wrong with the WYSE firmware?

Be interested to know if WYSE have come up with any comments on these issues?

Ben

]]> By: tony http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-14579 tony Wed, 14 Apr 2010 13:48:20 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-14579 We are also having the same issue. any news on this topic? tony We are also having the same issue. any news on this topic?

tony

]]> By: J http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-11460 J Wed, 03 Feb 2010 07:55:16 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-11460 Same problem here as it seems, using V10L thin clients with newest firmware. Strange thing is that after rebooting the DHCP server everything works fine for about a week (using a 2008 R2 server as DC with DHCP). Any news so far about that topic? Same problem here as it seems, using V10L thin clients with newest firmware. Strange thing is that after rebooting the DHCP server everything works fine for about a week (using a 2008 R2 server as DC with DHCP).
Any news so far about that topic?

]]> By: ali http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-9751 ali Mon, 30 Nov 2009 20:38:59 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-9751 i seem to get similar dhcp issues at a client location. The thin client is forced to reboot after getting a 'dhcp lease expired' message which seems to happen at regular intervals (every two hours in my case). Wyse 1200LE is the thin client model with upgraded firmware. the thin client was directly connected to the dsl model, so i had a router put in between the dsl model and the thin client and that seemed to 'hide' the problem. No more 'dhcp lease expiration' messages, and hence no more reboots, on the thin client but the thin client still freezes or lockouts and disconnects without any reasons a couple of times a day because it seems like now the router is dealing with the dhcp problem. So I am probably guessing there is nothing wrong with the thin client dhcp settings but rather with the DSL model which seems to be expiring its dhcp lease every two hours. i am beginning to think this is an ISP issue and debating if i should ask the user to switch isps. anybody else facing these issues and found any viable solution? i seem to get similar dhcp issues at a client location. The thin client is forced to reboot after getting a ‘dhcp lease expired’ message which seems to happen at regular intervals (every two hours in my case). Wyse 1200LE is the thin client model with upgraded firmware.

the thin client was directly connected to the dsl model, so i had a router put in between the dsl model and the thin client and that seemed to ‘hide’ the problem. No more ‘dhcp lease expiration’ messages, and hence no more reboots, on the thin client but the thin client still freezes or lockouts and disconnects without any reasons a couple of times a day because it seems like now the router is dealing with the dhcp problem. So I am probably guessing there is nothing wrong with the thin client dhcp settings but rather with the DSL model which seems to be expiring its dhcp lease every two hours.

i am beginning to think this is an ISP issue and debating if i should ask the user to switch isps.

anybody else facing these issues and found any viable solution?

]]> By: joel http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-9633 joel Tue, 24 Nov 2009 18:26:11 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-9633 Hi Reuben, It looks like the main issue is that the WYSE firmware, rather than renew the lease or release it, just has the option of rebooting or shutting down. The other issue is that if the system is in a low power mode, it seems that the reboot does not happen. I went ahead and specified: DhcpExpire=reboot in our WINOS.INI file and extended our DHCP lease time to 8 days (I know this won't work for a lot of people) which seems to have worked for us as by the time 8 days are up it's likely a user has walked up to the terminal and seen the message to restart. The other option might be to disable the screensaver. I would like to build a test lab and set the lease to a short time to really test things though. Let us know if you find anything else that works! Joel Hi Reuben,

It looks like the main issue is that the WYSE firmware, rather than renew the lease or release it, just has the option of rebooting or shutting down. The other issue is that if the system is in a low power mode, it seems that the reboot does not happen. I went ahead and specified:

DhcpExpire=reboot

in our WINOS.INI file and extended our DHCP lease time to 8 days (I know this won’t work for a lot of people) which seems to have worked for us as by the time 8 days are up it’s likely a user has walked up to the terminal and seen the message to restart. The other option might be to disable the screensaver. I would like to build a test lab and set the lease to a short time to really test things though. Let us know if you find anything else that works!

Joel

]]> By: Reuben http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-9570 Reuben Sun, 22 Nov 2009 22:04:25 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-9570 Hey Joel, I'm having the same issue at a clients site. Did you ever solve this? Hey Joel,

I’m having the same issue at a clients site. Did you ever solve this?

]]> By: Rob D http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/comment-page-1/#comment-3820 Rob D Wed, 19 Sep 2007 04:53:13 +0000 http://joelgibby.net/2007/07/31/wyse-terminal-causing-dhcp-issues/#comment-3820 Joel, nice post on sniffing DHCP. Sounds like it is the WYSE terminal causing the problem. Did you ever nail it down? -Rob Joel, nice post on sniffing DHCP. Sounds like it is the WYSE terminal causing the problem. Did you ever nail it down?

-Rob

]]>