Tag Archives: Driver

Windows 8 and Intel USB 3.0 Host Controllers

Leave a reply

http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers

Now download these two .inf files which have been modified to allow the Intel driver to install on Windows 8:
inf

We are going to replace the existing versions of these two files with the ones we just downloaded. Place the files in the following directory of the unzipped driver package and click yes when Windows warns that we are over writing a file with the same name:

Intel(R)_USB_3.0_eXtensible_Host_Controller_DriverDriversWin7x64

This will update these two infs with the modified versions that will allow the Intel driver to install on Windows 8 when the Host Controller and USB hub drivers are updated.

To install the Intel drivers in place of the in box XHCI stack, we’ll have to temporarily disable Driver Signing Enforcement. To do this press the Windows key + R and in the run box type:

shutdown.exe /r /o /f /t 00

Now make the following selections to boot into the Start Up Setting Screen

Troubleshoot — Advanced options — Start Up Settings — Restart

Then, when the machine restarts, select “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.

When the machine restarts, open Device Manager (win + r, devmgmt.msc). Double click on the entry for the Intel(R) USB 3.0 eXtensible Host Controller and select the Drivers tab. You should see that the driver provider is Microsoft.

Now click “Update Driver” and then select “Browse my computer for driver software”.

Next choose “Let me pick from a list of device drivers on my computer”.

Next, select “Have Disk”.

In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the original infs with the two modified .inf files we downloaded earlier. Select iusb3xhc.inf and click ok.

Windows will warn that the driver is not signed and will require you to confirm the installation.

Once the installation is complete, reboot the machine following the same procedure as above:

shutdown.exe /r /o /f /t 00

Now make the following selections to boot into the Start Up Setting Screen

Troubleshoot — Advanced options — Start Up Settings — Restart

When the machine starts, select “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot. Once logged in, open Device Manager (win + r “devmgmt.msc”) and locate the entry under Other devices for an Unknown device, to find the correct one, double click on the entry for the unknown device view the details tab. Make sure it has the VID_8086.

Once you have located the correct device right click on it and choose “Update Driver” Choose “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.

Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the Intel(R)_USB_3.0_eXtensible_Host_Controller_DriverDriversWin7x64 folder earlier and click ok.

Again, Windows will warn about driver signing, when the install is finished, reboot your machine.

When it restarts look at the driver tab for the Intel(R) USB 3.0 eXtensible Host Controller and the Intel(R) USB 3.0 Root Hub to confirm that you are now running the Intel drivers.

To return to the built in Microsoft USB 3.0 driver stack, use the uninstall drivers button from the driver tab in device manager. When it’s finished, select the Action menu of Device Manager and “scan for hardware changes” Windows should find the Intel USB 3.0 host controller and re-install it using the built in Microsoft XHCI stack.

Citrix Protocol Driver Error

there is a problem with the clients configuration, or there is possibly a network connection problem.  If you are getting this error “Citrix Protocol Driver Error” try the following steps to resolve the problem

– Find out what servers belong in that published application and test connectivity to each one.  Log in to the citrix admin console and locate the published application that the client is trying to connect to, Now note down all the server names that are in that published app.  Go back to the client and try the following on every server from the command prompt (Replace server1 with the name of your server)

ping each %server% > Do you get a reply? If not check the server, has it crashed, is it turned off??

From the command prompt type  “telnet %server% 1494”     If the screen goes black and says ICA then connectivity is okay. This is the port that ICA runs on. If the screen does not go black then you have a connectivity problem.  Try to reboot the server, check if there is a firewall between the client and the server, the port 1494 could be getting blocked

Can you connect to the server via RDP ??

– Next thing to check if the published application is enabled. Log in to the citrix admin console and locate the published application, make sure it is enabled  Sounds silly but it happens. If it is disabled clients will get the error “Citrix Protocol Driver Error”  Also are there servers in the published application that are offline?? If yes take them out of the app as this can cause a problem.

– Is there a firewall between the client and the server?? If yes make sure port 1604 is open to all servers in the published application.  This port will be used if the published application is load balanced.  The client will also need to communicate with the citrix master browser on port 1604. To find out what server is the master browser do the following

In citrix metaframe 1.8 and earlier versions log on to any server in the farm and go to the command prompt and type in qserver  now look for a server that has an M  next to it,  This server will be the master browser.

In Citrix metaframe XP / Presentation server 3.0 and newer versions log in to the citrix admin console and right click on the root “Where it says the name of your farm” and click on properties, now click on zones, search for the servers which are in your published application.  Are they all in the same zone?? If not it will be a good idea to move them in to the same zone.  Now in this zone there should be at least 1 master and 2 backup browser servers.

– Install the latest microsoft and citrix hotfixes.  In my experience if you install citrix and dont install any hotfixes you are going to run in to lots of problems with just about everything including this problem “Citrix Protocol Driver Error”.  Run microsoft windows update, Open internet explorer and click on tools > windows update and follow the prompts.  Visit www.citrix.com and download the latest hotfixes for your version of citrix and install them.

– Are clients having problems connecting via secure gateway 3.0?? If yes install citrix hotfix SGE300W003

-Check the eventvwr on each server in the published app, this might give you an idea what the problem is.

-Windows Services,  Log on to each server and make sure the “IMA, Metaframe COM, and all other citrix” windows services are running, to do this click on start > run type in  services.msc and enter.  If a service has stopped it will cause the citrix protocol driver error

-Is the firewall port 1604 (Citrix load balancing port) open between your client and the primary data collector / master browser for the zone? If not it needs to be.

-Have you enabled session reliability?? Try disabling it. If it is enabled it could force your clients to use a different port to connect to citrix servers,  a firewall could be blocking this connection.  If the firewall is not blocking the connection install the latest citrix hotfixes as this is what caused my problem once with the citrix protocol driver error.

-Verify the citrix server has no licensing problems,  Can it hand out Terminal server licenses and citrix licenses??  Log on to the licensing servers and make sure the licenses have not ran out and you can also see the citrix server polling in to get licenses.

-Do your clients go through a proxy to contact the browser servers? If yes check the proxy, also test connecting to the published app not going through the proxy

-Has the client got any local firewall software?? Check and temporary disable any existing firewalls just to make sure.  Do you have VPN software installed?? Try disabling this as well, I have checkpoints VPN software installed on my laptop and it causes a problem when the windows services are running, so i simply stop them.

Tips To Avoid “Citrix Protocol Driver Error”

Follow these tips to help avoid you getting the error “Citrix Protocol Driver Error”

-If possible the server that acts as a browser server should be on the same network as the client,  it is possible that network latency or even network problems can cause the error “Citrix Protocol Driver Error”

-If possible place the browser server in the same zone as the data collector.

-Install the latest citrix hotfixes on your servers,  I usually install the latest hotfixes on one of our servers, then leave for a week or two and then roll out to our other servers.

-Make sure all required firewall ports are open  “Citrix ICA Port 1494” “Citrix Load Balancing Port 1604” “Session Reliability Port (Set in citrix management console”

Summary of error “Citrix Protocol Driver Error”

Please note this guide was written completely by me based on my real life experiances with this error.  As you can tell I have ran in to the error “Citrix Protocol Driver Error” a few times before

Installing Windows XP on ESX/ESXi using LSI Logic driver

Leave a reply

By default, ESX will use the LSI Logic driver when deploying a new Windows XP virtual machine. The LSI Logic driver is not found on the CD-ROM media, so Windows XP will not continue with the installation if this driver is not found.

WinXP

  1. The steps:
    Create a new Windows XP Virtual Machine
    Upload a Windows XP .iso file to your datastore/ISOstore (preferably a VLK version) and link it via the CD-ROM options in your Virtual Machine. Make sure it is connected / at power on
    Go to http://www.lsilogic.com/cm/DownloadSearch.do and search for a driver for the LSI20320-R controller.
    Extract all files in the symmpi_wXP_1201800.ZIP
    Use a program such as WinImage to create an LSILogic.flp file and include the extracted files in the .flp image.
    Upload the newly created LSILogic.flp to your datastore/ISO store
    Link the .flp file via the Floppy options => use existing floppy image in datastore in your Virtual Machine. Do NOT connect it yet.
    Power On your Windows XP machine. The installation of Windows XP should begin.
    During setup, press F6 to select additional SCSI drivers
    Now is the time to connect your floppy and use S during Windows Setup when prompted to connect to the floppy drive.

S-Command

The LSILogic drive should appear. Press ENTER to continue
Setup will continue as normal
Install VMware tools
Done!

NOTE: when using the BusLogic driver instead, you can download & use a preconfigured .flp file from the VMware site: http://download3.vmware.com/software/vmscsi-1.2.0.4.flp. Follow the same procedure as described above. The driver should be name VMware SCSI Controller in Windows XP.

Technorati Tags: ,,,,