Timeout waiting for iSCSI persistently bound volumes



    I am running Windows 7 Ultimate 64 bit (en-us)

    I am connecting a D:-drive with iSCSI from a QNAP TS-659 device.

    Everything works fine untill I rebot my computern, then I get the following two events in the System Event Log.

    1. Warning - Source: MSiSCSI, EventID: 121
      The firewall exception to allow Internet Storage Name Server (iSNS) client functionality is not enabled. iSNS client functionality is not available.
    2. Error - Source: MSiSCSI, EventID: 103  (2s after msg 1)
      Timeout waiting for iSCSI persistently bound volumes. If there are any services or applications that use information stored on these volumes then they may not start or may report errors.

    Message 2 above indicate that D:-Drive shouldn't be availabel, but it is. Everything is working just fine when I have loged in to the machine. But the boot process is very slow and it first takes a long time before I see the logon screen, and after I have suplied the password it takes an even longer time before the desktop apears.

    I have followed the procedures in this article, including running the command "iscsicli.exe FirewallExemptiSNSServer":

    • All involved IP addresses are static
    • There is no router involved, only a 1Gbit Switch
    • Everything is working after I have successfully logged in, there is only a huge timeout before the login screen is shown and another timeout after I have loged in and waiting for the desktop to show.


    1. How do I get rid of the two System Event log messages above?
    2. How to I speed up the boot and login process so the computer dosen't need like 5 minutes for it to start?
    Thursday, January 27, 2011 8:28 PM

All replies

  • Hi Krickedick,

    I got the same problem.  Did you find solution to your situation? Please post.

    Saturday, May 26, 2012 10:33 PM
  • Hi!

    I made the server process depend on the iSCSI service in windows as described in this article

    even though I didn't have the problem described in there I thought it wouldn't hurt do delay the start of the server service, especially since a lot of other services depend on the server service. This helped me with the problem with eventid 103. The other one I still have.

    Saturday, May 26, 2012 10:52 PM