iSCSI Targets

%3CLINGO-SUB%20id%3D%22lingo-sub-285470%22%20slang%3D%22en-US%22%3EiSCSI%20Targets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285470%22%20slang%3D%22en-US%22%3E%3CP%3EWhenever%26nbsp%3BI%20try%20to%20assign%20my%20iSCSI%20to%20a%20target%20using%20Query%20initiator%20computer%20for%20ID%2C%20I%20get%20this%20error%3A%3C%2FP%3E%3CP%3E%22Unable%20to%20determine%20IQN%20for%20PC.domainname.com%22.%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20where%20the%20problem%20stems%20from%3F%3C%2FP%3E%3CP%3EIs%20there%20any%20additional%20configuration%20I%20have%20probably%20forgotten%20to%20do%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-285470%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECompute%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286570%22%20slang%3D%22en-US%22%3ERe%3A%20iSCSI%20Targets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286570%22%20slang%3D%22en-US%22%3EThere's%20no%20such%20issue%20when%20I%20use%20the%20IP%20addresses%20(%20which%20are%20set%20statically%20of%20course).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286463%22%20slang%3D%22en-US%22%3ERe%3A%20iSCSI%20Targets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286463%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20happens%20when%20you%20try%20to%20connect%20using%20the%20IP%20address%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286201%22%20slang%3D%22en-US%22%3ERe%3A%20iSCSI%20Targets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286201%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20honestly%20speaking%2C%20this%20was%20the%20exact%20thing%20I%20did%20before%20posting%20my%20question%20here%20(%20I%20googled%20the%20issue%20and%20found%20the%20page%20with%20exactly%20the%20same%20context).%20However%2C%20it%20didn't%20workout%20even%20after%20I%20created%20the%20rule.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20weird%20issue%20during%20iSCSI%20configuration%20was%20that%20whenever%20I%20selected%20DNS%20name%20as%20the%20method%20to%20identify%20the%20initiator%2C%20the%20iSCSI%20initiator%20on%20the%20destination%20computer%20could%20not%20detect%20the%20disk%20(nor%20the%20server%20itself)%2C%20even%20though%20there%20wasn't%20really%20a%20connectivity%20issue%20between%20the%20two%20computers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285517%22%20slang%3D%22en-US%22%3ERe%3A%20iSCSI%20Targets%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285517%22%20slang%3D%22en-US%22%3E%3CP%3EMaybe%20this%20applies%20to%20your%20situation%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CBLOCKQUOTE%20dir%3D%22ltr%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3E%3CSPAN%3EIssue%3A%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3EIn%20a%20mixed%20language%20environment%2C%20where%20the%20domain%20name%20contains%20international%20characters%2C%20you%20run%20the%20New%20iSCSI%20Virtual%20Disk%20Wizard%20from%20a%20domain-joined%20Windows%20Server%202012%20computer%20that%20uses%20a%20different%20character%20set.%20In%20the%20wizard%2C%20you%20create%20a%20new%20iSCSI%20target.%20On%20the%20%3CSTRONG%3ESpecify%20access%20servers%3C%2FSTRONG%3Epage%2C%20when%20you%20try%20to%20add%20an%20iSCSI%20initiator%20by%20using%20the%20%3CSTRONG%3EQuery%20initiator%20computer%20for%20ID%3C%2FSTRONG%3Eoption%2C%20you%20select%20a%20computer%2C%20where%20the%20fully%20qualified%20domain%20name%20(FQDN)%20includes%20the%20domain%20with%20international%20characters.%20When%20you%20click%20%3CSTRONG%3EOK%3C%2FSTRONG%3E%2C%20you%20receive%20an%20error%20message%20that%20is%20similar%20to%20the%20following%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EUnable%20to%20determine%20IQN%20for%20%3CFQDN%3E.%3CBR%20%2F%3E%3C%2FFQDN%3E%3C%2FEM%3E%3CBR%20%2F%3EThis%20issue%20also%20occurs%20when%20you%20use%20the%20Query%20initiator%20computer%20for%20ID%20option%20in%20the%20following%20locations%3A%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20Import%20iSCSI%20Virtual%20Disk%20Wizard%3C%2FLI%3E%3CLI%3EThe%20Assign%20iSCSI%20Virtual%20Disk%20Wizard%3C%2FLI%3E%3CLI%3EThe%20Initiators%20tab%20of%20the%20Properties%20page%20for%20an%20iSCSI%20target%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CEM%3E%3CSPAN%3EWorkaround%3A%3C%2FSPAN%3E%3C%2FEM%3E%3CBR%20%2F%3ETo%20work%20around%20this%20issue%2C%20follow%20these%20steps%20on%20the%20computer%20on%20which%20you%20are%20trying%20to%20add%20an%20iSCSI%20initiator%3A%3C%2FP%3E%3COL%3E%3CLI%3EOpen%20the%20Local%20Group%20Policy%20Editor%20(Gpedit.msc).%3C%2FLI%3E%3CLI%3EUnder%20%3CSTRONG%3ELocal%20Computer%20Policy%3C%2FSTRONG%3E%2C%20expand%20%3CSTRONG%3EComputer%20Configuration%3C%2FSTRONG%3E%2C%20%3CSTRONG%3EWindows%20Settings%3C%2FSTRONG%3E%2C%20and%20then%20click%20%3CSTRONG%3EName%20Resolution%20Policy%3C%2FSTRONG%3E.%3C%2FLI%3E%3CLI%3EIn%20the%20%3CSTRONG%3ECreate%20Rules%3C%2FSTRONG%3Earea%2C%20click%20%3CSTRONG%3ESuffix%3C%2FSTRONG%3E%2C%20and%20then%20enter%20the%20namespace%20to%20which%20the%20rule%20applies%20(for%20example%2C%20%3CEM%3Econtoso.com%3C%2FEM%3E).%3C%2FLI%3E%3CLI%3EOn%20the%20%3CSTRONG%3EEncoding%3C%2FSTRONG%3Etab%2C%20select%20the%20%3CSTRONG%3EEnable%20Encoding%3C%2FSTRONG%3Echeck%20box%2C%20and%20make%20sure%20that%20%3CSTRONG%3EUTF8%20without%20Mapping%3C%2FSTRONG%3Eis%20selected.%3C%2FLI%3E%3CLI%3EClick%20Create.%3CBLOCKQUOTE%20dir%3D%22ltr%22%3E%3CP%3EThe%20rule%20appears%20in%20the%20%3CSTRONG%3EName%20Resolution%20Policy%20Table%3C%2FSTRONG%3E.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3C%2FLI%3E%3CLI%3EClick%20%3CSTRONG%3EApply%3C%2FSTRONG%3E%2C%20and%20then%20close%20the%20Local%20Group%20Policy%20Editor.%3C%2FLI%3E%3C%2FOL%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E
Soheil Badri
Occasional Contributor

Whenever I try to assign my iSCSI to a target using Query initiator computer for ID, I get this error:

"Unable to determine IQN for PC.domainname.com".

Does anyone know where the problem stems from?

Is there any additional configuration I have probably forgotten to do?

4 Replies

Maybe this applies to your situation:

Issue:
In a mixed language environment, where the domain name contains international characters, you run the New iSCSI Virtual Disk Wizard from a domain-joined Windows Server 2012 computer that uses a different character set. In the wizard, you create a new iSCSI target. On the Specify access servers page, when you try to add an iSCSI initiator by using the Query initiator computer for ID option, you select a computer, where the fully qualified domain name (FQDN) includes the domain with international characters. When you click OK, you receive an error message that is similar to the following:

Unable to determine IQN for <FQDN>.

This issue also occurs when you use the Query initiator computer for ID option in the following locations:

  • The Import iSCSI Virtual Disk Wizard
  • The Assign iSCSI Virtual Disk Wizard
  • The Initiators tab of the Properties page for an iSCSI target

Workaround:
To work around this issue, follow these steps on the computer on which you are trying to add an iSCSI initiator:

  1. Open the Local Group Policy Editor (Gpedit.msc).
  2. Under Local Computer Policy, expand Computer Configuration, Windows Settings, and then click Name Resolution Policy.
  3. In the Create Rules area, click Suffix, and then enter the namespace to which the rule applies (for example, contoso.com).
  4. On the Encoding tab, select the Enable Encoding check box, and make sure that UTF8 without Mapping is selected.
  5. Click Create.

    The rule appears in the Name Resolution Policy Table.

  6. Click Apply, and then close the Local Group Policy Editor.

Well, honestly speaking, this was the exact thing I did before posting my question here ( I googled the issue and found the page with exactly the same context). However, it didn't workout even after I created the rule.

 

Another weird issue during iSCSI configuration was that whenever I selected DNS name as the method to identify the initiator, the iSCSI initiator on the destination computer could not detect the disk (nor the server itself), even though there wasn't really a connectivity issue between the two computers.

What happens when you try to connect using the IP address?

There's no such issue when I use the IP addresses ( which are set statically of course).
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies