Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Have an older wyse 3360 winterm thin client device, firmware 3.5.1 sp2, build 441.22.

We have several of these units that work fine when a manual ip address is assigned. But when dhcp is used on the thin client, they won't connect to a windows 2003 rdp server. The windows 2003 rdp server in question is used in production by many clients, pc based and thin clients, so I wouldn't suspect the server.

This is on a local lan, 10/100 ethernet, a cisco 3550 switch connects the wyse to the dhcp server and the rdp terminal server. The dhcp server is w2k3 sp2, 32 bit. Rdp server is win 2k3 server, sp2 64 bit.

When dhcp is used on the wyse, they will connect to our unix server with a terminal emulation session, so we know that dhcp works as far as network connectivity goes. It's just the rdp session won't work. Very odd. Is their a dhcp option that the wyse needs to be receiving in order for rdp to work?

ip address being assigned to the wyse via dhcp is , When this address (or a similiar one like / is assigned manually rdp sessions work fine.

share|improve this question

Figured this out. Since thin client was using DNS (and not wins), have to specify the fqdn for the rdp server. Not exactly intuitive on some of these older devices, they don't have ability to make a lan broadcast to discover the name, as most modern win os's would.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.