- This topic is empty.
-
Posts
-
I’m currently testing a v10L with our POS system and trying to determine what infrastructure changes may be required to make everything work at the lowest support cost possible.
Ideally in our remote sites I would like to use Dynamic IPs on all thin terminals so that when a new device is introduced, it just works, straight out of the box.
A DHCP will be available most of the time, however it is possible that if a sites router becomes unavailable due to failure or theft meaning both that the dhcp server and the failover dhcp server are unavaiable.
I this event any device that has been restarted must continue to boot and connect to the TS server that is on site. (they always connect to a TS server that is on site).
is there any way to configure WTOS so that it will remember and use its last assigned IP if no DHCP server is available?
I suspect a workaround may be the ability for the wnos.ini to force the device to dhcp every time it pickups the wnos.ini file.
if I could do this, then in the event of the dhcp server being unavailable, the helpdesk could guide users specify fixed ips and when the connection to a dhcp server becomes available again, the devices would all be reset to dhcp again.
I cannot find a parameter in the documentation that would provide this functionality.
does anyone have any ideas?How about a DHCP server on the site, so locationA will have a DHCP server and so does locationB ?
If a DHCP server is not available i think many things will not work (Terminal Server/Printers name it) our Wyse Devices will try endless and endless for a DHCP server and if there is an DHCP server you are sure everything works not only the connection.
You are talking about what if a site router/DHCP server is not available, i think if he is not avaialble you will have a bigger problem then just only DHCP. But i don’t know anything about your enviroment.
all of our sites operate completely independently of each other and have their own fixed ip terminal server with which the thin clients will connect to, a dead router should only cut of the site from the rest of the world, but not affect its ability to trade.
our infrastructure team are against running a dhcp server on each windows 2003 standard server as it ould mean that in normal operation there would be 500+ dhcp servers on our network.
upgrading to 2003 enterprise and using clustered dhcp as a failover on each site is not financially viable.
in my testing I have found that in the event of the loss of a dhcp server, the wyse device will prompt for a static ip, which I am going to describe in a support manual. Helpdesk staff will guide the onsite staff to specify a static ip, and once connectivity to the site has been restored, and the dhcp server is available again, helpdesk staff will reset the devices to factory default and they will retrieve their config from the ftp server on 1st boot.
- You must be logged in to reply to this topic.