Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WYSE Terminal can't find Citrix Server when using DHCP

Status
Not open for further replies.

markc99

IS-IT--Management
May 1, 2001
2
US
I have a client that has 3 WYSE Terminals and about 30 PC's. I recently setup a DHCP server, and a WINS server. I put the WINS server in the DHCP configuration so all the clients would access it. The WYSE terminals all worked fine for about a day, then one of them couldn't find the Citrix server. After spending some time troubleshooting it, I figured out that it would work fine if I put a static IP address in it. The client said he would rather all the PC's be the same and access the DHCP server, but if we had to use static to make it work, oh well. The following day, another one of the WYSE terminals had the same problem.

Here is my question, why can't they seem to find the Citrix server when it uses DHCP, but not when it's static. The only thing I can think of has to do with the way I setup the WINS server in the DHCP server. I used h-node (hybrid) instead of b-node (broadcast). I noticed some of the PC's after switching them to DHCP came up with Broadcast node type, and then after awhile would switch to Hybrid node type. Does a Winterm have trouble with the Hybrid node type? Thanks for any help on this issue.
 
h-node is a combination of b-node and p-node (point-to-point). There is no reason I can think of why b-node would work and h-node would not - but I've never seen your issue "in the flesh".

You'd be better off checking your DNS configurations. ICA uses pure IP rather than Microsoft's implementation - WINS only resolves Windows NetBIOS names.

I recently did a rollout of 200 WYSE WinTerms using DHCP, and the only Static IP address that was needed was the IP of the ICA Master Browser in the Connection Settings on the WinTerms.

Hope this helps - good luck!

 
Well, if that is the case, I do not have a DNS entry in the DHCP configuration. We do not have a DNS server on site, so I figured what was the point in including it. Is that needed for ICA to work?
 
Since Winterms use WinCE, I would have thought WINS would work - again, I've never worked with a WINS only installation; every implementation I've worked on has had a DNS server on the main site.

ICA uses whichever implementation of TCP/IP it gets. If you're using Microsoft's, then WINS should work - DNS is just the internet name resolution standard.

My one stumbling block is that you say that the WYSE terminals worked well for about a day. Clearly your setup does not require DNS to function.

It could be a licensing/undeleted cached profile issue. Some users (bless them!) simply turn off their Winterms rather than logoff through the Start button first.

Does your Citrix server have a regular reboot cycle?

Which Microsoft/Citrix Service Packs and Hotfixes are you running?

Are the Winterms using the latest WYSE firmware? I had issues at one site where about 20 out of 100 Winterms would completely lose their settings until we upgraded the firmware.

I hope some of this helps!



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top