Protocol Driver error

[Dukester0122]

We just upgraded to PS 4. When a user tries to open a published application they always get this error the first time:
Cannot connect to the Citrix MetaFrame server.
Protocol Driver error

 

[wazzup2474]

You should have not wasted your money on updating citrix and went ahead with implamenting termianl services thought out the company Does everyone get that error internal and external and the ones that are getting that error are they running sp2 you might want to check if sp2 block any ports trying turning it off and then connecting, are they using the must updated client if not uninstall the old and reinstall the new

 

[carlodoep]

Also check that your primary zone collector is not recieving any errors. The protocal errors we got always related to the zone collector or network slowness.

C'ya
Carlo

 

[patrickrouse]

This will also happen if the user is not connected to the network, i.e. doesn't have a TCP/IP Bound NIC.

wazzup2474 (MIS) - 2003 TS base product is nice, but there a re any, many features that Presentation Server has that the base product does not, i.e. bi-directional audio, which can only be had with ICA.

Patrick Rouse
Microsoft MVP - Terminal Server

http://www.workthin.com

 

[dts01]

Can you try disabling session reliablity

 

[enigma99]

Here is what I've done in the past to fix this issue.
The issue came up when we split up our home directories for our end-users.
Originally all of our users were pointing to:
\\server1\home1
\\server1\home2

After the move it looked like this:
\\server1\home1
\\server2\home2

Everyone in server2 had issues connecting to published applications and it would throw up that "Protocol Driver" message.
Search in the registry for the username under HK_USERS.
You will find a registry key named Program Neighborhood Cache. Simply highlight this registry key and delete it.

That should do it.
If not, I have also narrowed it down to a specific server and I've restarted the IMA services on that box.

Hope that helps.