Unsolved
This post is more than 5 years old
4 Posts
0
18170
Wyse Terminal using two IP addresses (ThinOS)
Wyse Terminal using two IP addresses (ThinOS)
We are seeing an issue with some of our WYSE terminals using two IP addresses. One of the IP addresses is coming from DHCP. The other address is in the DHCP range so we are thinking it may be a previous DHCP lease that the WYSE terminal was given and the WYSE terminal continues to use.
We discovered the issue because the DHCP server gave another WYSE terminal the IP address out that the WYSE terminal is holding on to.
We verified this is what is happening via the router's ARP table. We cleared the IPs out of the ARP table and the entries get added back (we have done more TS). We have about 8 terminals doing this.
Is this a known bug? Is there a fix?
Example ARP table entry:
Cisco_router#show ip arp 0080.64ac.XXXX
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.XXX.XXX.1 197 0080.64ac.XXXX ARPA Vlan2
Internet 10.XXX.XXX.2 184 0080.64ac.XXXX ARPA Vlan2
Rmontalvo1
623 Posts
0
June 16th, 2015 08:00
Shade69,
What model of the thin client are you talking about, and what version of firmware do they have?
Roger Montalvo
Visit our Dell Wyse Thin Client Knowledge Base and Manuals web site at www.wyse.com/KB
Visit our Dell Wyse PocketCloud Knowledge Base and Manuals web site at http://pocketcloudsupport.wyse.com/forums
[SIGPIC][/SIGPIC]
b_a_Slacker
4 Posts
0
June 16th, 2015 08:00
Still occurring
No solution yet.
It's getting annoying as we are finding the issue more and more, at multiple sites. We have adjusted the DHCP servers to check for duplicates before assigning a DHCP address and that has helped with the duplicate IP aspect but we still have the WYSE terminal trying to use 2 IP addresses and not able to communicate. A resetting of the WYSE terminal (Ctrl-g on boot-up) seems to solve the issue for a short term but it comes back.
We are investigating Cisco switch configuration possibilities impacting the WYSE terminals. These configuration changes should not be needed but they may give us clues as to the nature of the problem.
joshg1
2 Posts
0
June 16th, 2015 08:00
We are starting to see this issue on our network and are sending the logs to Wyse for troubleshooting. did you get any resolution to this?