Windows Server 2022 — iSCSI target portal disconnects under heavy initiator load — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

iSCSI target portal disconnects under heavy initiator load on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the storage subsystem is in use, typically following configuration drift or recent updates.

Get-IscsiVirtualDisk
Get-WinEvent -LogName 'Microsoft-Windows-iSCSITarget/Operational' -MaxEvents 30

Root Cause Analysis

The defect stems from misaligned iscsi target settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Get-IscsiServerTarget -TargetName 'target01' | Format-List
Get-Counter 'iSCSI Target(*)*'

Step-by-Step Diagnosis

Walk the storage stack from configuration to runtime, collecting logs and counters that point at the failing component.

Get-IscsiConnection
Get-WinEvent -LogName 'Microsoft-Windows-iSCSITarget/Admin' | Where LevelDisplayName -eq 'Error'

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the iscsi target component re-initialises cleanly.

Stop-Service WinTarget
Set-IscsiServerTarget -TargetName 'target01' -EnableChap $true -Chap (Get-Credential)
Set-IscsiServerTarget -TargetName 'target01' -MaxReceiveDataSegmentLength 262144
Start-Service WinTarget

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

Disconnect-IscsiTarget -NodeAddress 'iqn.target01' -Confirm:$false
Connect-IscsiTarget -NodeAddress 'iqn.target01' -IsPersistent $true -IsMultipathEnabled $true

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Get-IscsiConnection | Select ConnectionIdentifier,InitiatorAddress,TargetAddress
Get-Counter 'iSCSI Target(*)Total Bytes/sec' -SampleInterval 5 -MaxSamples 12

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

Remove-IscsiServerTarget -TargetName 'target01' -Force
Restart-Service WinTarget

Prevention & Hardening

Bake the validated iscsi target configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Set-IscsiServerTarget -TargetName 'target01' -EnableChap $true -ReverseChap (Get-Credential)
Set-Counter -Counter 'iSCSI Target(*)*' -SampleInterval 60 -MaxSamples 1440

Related Errors & Cross-Refs

Related: other storage failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.