- This topic is empty.
-
Posts
-
Hi,
Since the upgrade to 6.5.0_23 (and now 6.5.0_24), we have a DHCP issue on V10L (and not on S10):
At boot time, the V10L doesn’t allways get an IP adress from DHCP and then show the network settings dialog. If we validate the network dialog (with the choice “DHCP” activated) the terminal then get its IP adresse and works OK.Anyone else has got the same issue ?
(we have a standard Windows 2003 DHCP server)PS: We also have the wrong time issue discussed here http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=5837
Hi atmora, how are your devices connecting…hard wired or wireless? I have noticed some flukey things with DHCP when connecting wirelessly. Once I connect hardwired I pull the IP information, reboot and connect wirelessly with no issues.
Could be an issue that your switch is not opening the port fast enough. Check your switch.
CG
sfhxen: They are wired (100Mb full duplex)
ConfGen: Thx, I’ll try with another switch.
I haven’t got this issue with previous firmware (it worked more than a year, and i didn’t change the switch or his settings), so I’m a bit suprised that nobody else got this problem.
If it is specific, I’ll chek our LAN & DHCP.We are seeing this same issue. V10L with WTOS 6.5.0_23 connected to a Cisco 2950 with autonegotiate and portfast. Windows 2008 R2 (was 2003) DHCP, we get the popup and have to validate the network dialog.
We have called, not sure where the issue stands with them, but we will be calling them back about it.
We are having the same issue as well. Our setup is pretty much the same as jvocaire, but we don’t have the R2 version of Server 2008 and we are using Cisco 2948 and 3560s.
We have a 3Com 4228 switch (autonegociate) and a Windows 2003 (R1) DHCP server.
On your switch, try enabling “PortFast” on the particular interface your terminal is plugged into.
This worked for us, as ConfGen suggested the port wasn’t being opened fast enough for WTOS.
Michael,
As you can see in my post, we already have portfast enabled. We got a newer build from Wyse (30), and now the DHCP issue doesn’t occur every time. It now seems to happen about 50% of the time, and we haven’t yet found a pattern, so we will be calling Wyse back.
Hi,
For us the 6.5.0_30 firmware didn’t help at all. We still have the problem 60% of the time.
And our switch (3Com 4228) don”t offer a “fast port” setting.Our issue turned out to be bad documentation. The device was not plugged into the switchport that was listed. We noticed this when we bought some new units that shipped with 6.5 and they didn’t have the DHCP issue.
So, for us, 6.5 build 30 doesn’t appear to have any issues.
Hi,
For us, S10 and V10L have the problem with firmwares 6.5.xxx, 7.0.0_30 and 7.0.0_34.
But adding TCPTimeout=2 to te wnos.ini did solde the problem !We had this problem with some 10Mbit locations.
keep alive settings on the ARP table in the router was set to 4 hours, we changed this settings to 30 seconds. Everything works now. Why it only happened on 10Mbit locations and not 100Mbit locations we don`t know. It was different Cisco switch models, but could also be firmware related to the switches.HI Guys
Seeing the same issue on the following devices:
C10LE with f/w – 7.0_113
S10 with f/w – 6.5.0_47I haven’t tried adding TCPtimeout=2 ( which introduces a 60 second delay ) to WNOS as suggested by someone above.
Nick
Hi All
Have an update on the issue of Wyse ThinOS based termimals with issues obtaining IP addresses. We have two domain controllers running DHCP service at the datacentre. The remote sites obtain IP addresses using IP helper addresses on the router.
It appears a DHCP Request is sent to both domain controllers on our network. DHCP request is serviced by both DC’s. Only one IP address is accepted by the Wyse terminal.
The router retains the IP to MAC allocation for the Wyse terminal for both IP’s issued. This was causing the issue all along. We changed the RP cache timeout to 30 mins (from 4hr default) and this seems to have resolved the issue.
Does anyone know if this issue was addressed in a ThinOS upgrade ?
Nick
- You must be logged in to reply to this topic.