Wyse Thin Clients Error Connecting to Xen App Server

Check C:\windows\pfirewall.log and see whether firewall is enabled.

On the server?

On the thin clients

Can you give me direction on how to do that?  I didn't have to do that on the other 5 that are working now.  

I appreciate your assistance!

There is no firewall on these thin clients.

What is the OS on these thin clients? Is it WYSE Xenith?

Yes its Wyse Xenith.

What version of web interface do you have?

How is your web interface configured?

Also ensure that your other 3 wyse terminals are at the same firmware as your 5 working ones - if not update them with Dell.

Have a look at this thread too, it might help you:

http://forums.citrix.com/thread.jspa?threadID=288656

Compare the 2 VS 3 thin clients what settings different? Are they on same subnet but 2 OK 3 fail?

Mostly it related to firewall setting/network routing issue between them.

That is what we are looking at right now.  We are looking to see if its a network issue. I will let you guys know.

We have checked the following:

No firewall.  They are on same same subnet.
Thin client is configured to grab IP via DHCP.
I can ping thin client from Xen App server.
All setting are the same on the new ones and old ones, except the firmware.  Old one is v1.0 and new one is v1.7

We have unplugged new one and plugged it in where old one was and still get the same result.  No dice.

We have verified Xen App server is fully patched.

So I don't see where it can be firewall or network issue.

Any other ideas guys?  This is driving me crazy as to why the old ones will work and the new ones wont.

Ok I looked at the logs on the new thin clients  and I am getting these errors.
Error-on-Xen-App-server.PNG

Looks like the firmware of the new thin clients have been upgraded from an older version, but the upgrade corrupted something.

Follow this link to try to resolve your issue: http://www.repairerrorquick.com/ttfix-0xc000007b_error-zz0001

I uploaded the wrong pics.  Sorry about that.  Here are the errors.
New-Thin-Clients-Error.jpg
New-Thin-Clients-Error2.jpg

After view your pic , i 'd like to suggest you to use static ip to test first at least avoid some other issue. Pointing to the right DNS and static IP ..is it work. It seem your WDM server has record /config wrong

We are not using WDM server.

We are still getting no where on this.  We have tried to statically assign them and no go.  The only difference is the  firmware.  Old firmware looks like it loads Xen App interface and new ones load Xen Desktop interface.  I can get to login but it fails with error.
2012-10-08-11.34.44.jpg

What if you shutdown the 5 that had a successful connection and start the others?
Do they connect.
Have you looked at license contention on the XenApp server.

ate th network ports on the thin clients connected, do they have valid IP addresss?

We have had all the working thin clients shut down when troubleshooting this issue.  We only have one on at a time.  The new ones is what we have on.  We have 25 licenses for Xen App.  We have tried to statically assign the thin clients and get the same issue.  We have swapped places with a known working one and still no go.  The only difference I see is that the firmware are different on the new ones.

I have reached out to Wyse support but I am getting no where because its Indian support.

I just dont understand how all 5 of the others work but not these 3 new ones.

So I worked with Wyse support and we found out that our Xen App server will not connect using the new Citrix Receiver. It will work with the Online Plugin.  When we connect with the new receiver we can see all apps and published desktop.  But when we try to access the published desktop it says app cannot be started.  So Wyse stated we need to make sure that our server will connect using the new receiver and our thin clients will work.  Never thought that would be the problem.  We have no issues when users connect via the Xen App portal as they can connect to all published resources or by connecting with the online plugin in their task bar.

We are working on that now.

Did not really get any solution from anyone here to help with resolving the issue.