Error: "1030 - Protocol Driver Error" Troubleshooting Steps and Suggestions

The 1030 Protocol Driver Error could be caused by a number of different things. Each step must be taken and verified true.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

First, look at the server's configuration:

1. Ensure the server has the latest Terminal Server or Windows 2000 Service Pack Level.

2. Ensure the Network Interface Card (NIC) has the latest driver installed.

3. For MetaFrame 1.8, enure to have Service Pack 2 installed.

4. Check the Event Viewer for any 1004 Terminal Server Licensing Errors.

5. Check that the subnet mask is consistent on every MetaFrame server in the farm.

On the client:

1. Ensure that you are using the latest client build. For updates to this, go to http://www.citrix.com/download. A listing of the latest clients and their respective build numbers are available there.

2. Ensure to use the latest IP stack for the client operating system.

--------------------------------------------------------------------------------------------

If all appropriate updates to the server and client are applied, try the following items:

1. Increase the idle winstation pool count in the registry. By default, Terminal Server creates two idle winstations. Increase this count by two and re-try. Edit the following registry key by using REGEDT32:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
IdleWinStationPoolCount.

NOTE: Each idle winstation will take up 1 MB RAM. Take this into consideration when adjusting this count.

2. Adjust or remove any TCP KeepAlive settings that may have been added. For this functionality to be added, MetaFrame 1.8 Service Pack 1or higher is required. Refer to Citrix Document: CTX708444

--------------------------------------------------------------------------------------------

If connecting over a WAN or Internet connection, ensure that the following ports are opened:

• Port 1494 for TCP/IP is opened.

• Port 1604 for UDP is open Inbound on the firewall.

• Port 1023 and above (The High Ports) are opened for TCP and UDP outbound.

If using Network Address Translation, refer to the Solutions Knowledgebase Article "ICA Browsing With Firewall Address Translation (NAT)".

In some instances (depending on Firewall manufacturer) all connections through the Firewall may be reset when a rule is added to the Firewall. This has been verified to occur on Checkpoint Firewalls.

--------------------------------------------------------------------------------------------


If users are receiving this error when attempting to authenticate to a Server Farm, make sure that the Program Neighborhood Service is started. If this is confirmed, the load level of the Server Farm(s)
could be an issue. The following Solutions Knowledgebase Documents should assist you with troubleshooting this:

• Application Load Levels Defined: 10000, 10000!, 10001, 10002, 9999

• Additional Information on Qserver /App Load Factor 10002

If none of the above items resolve the issue, there may be an issue with the ICA Master Browser. Check and see if the ICA Master Browser Service is started on the server that you are trying to connect to.
If the service is started, and you have multiple Citrix servers in your environment, configure a different Citrix server to become the ICA Master Browser by default. Then, force an election. Once the new
server is registered as the ICA Master Browser, try the connection again.
-------------------------------------------------------------------------------------------

Special Considerations when Connecting to an Application with Citrix A.L.E.

If you receive an Error 1030: Protocol Driver Error when connecting to a web published application, try a connection with the full version of the ICA Client for Win32. Create a Custom ICA Connection to
the published application and attempt the connection. If this is not successful, follow the instructions previously noted. If this type of connection works, then the contents of the ICA File need to be
reviewed. For more information refer to the Solutions Knowledgebase Article "Checklist for Connecting to a Citrix Server by ICA Link on Web Page". Look for a section titled "The ICA File".

If you are running the ICA Client to connect to a Windows 2000 Server, you are required to have one of each of the following licenses:

• Microsoft Client Access License.

• Terminal Services Client Access License.

If you do not have a sufficient number of these licenses installed onto your server, you will not be able to connect to the Windows 2000/MetaFrame 1.8 server.

Customer's using Windows 9x may get the 1030 protocol driver error while Windows 2000 based clients do not.

In order to connect to Windows 2000/MetaFrame 1.8, use client version 4.21.779 or higher on Windows 32-bit workstations. With the release of this client, the connection checks for available Microsoft Licenses (both regular CAL and Terminal Services CAL (if not connecting from a Windows 2000 Professional based client) before a connection is established. If the connection fails, then check the Microsoft product License manager to see if you are complying with this licensing scheme.

Also, be sure that your Windows 2000 Terminal Licenses are activated! If they are not activated, you will see the 1030 error.

For more detailed information, refer to the Microsoft White Paper "MS Windows 2000 Terminal Services Licensing"