diff --git a/Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md b/Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md
index 1fdecef..cd81ce7 100644
--- a/Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md	
+++ b/Servers & Workflows/Windows/Windows Server/Virtualization/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md	
@@ -65,7 +65,7 @@ You may be booted out of the Remote Desktop session at this time due to how the
 
 | IP ADDRESS  | SUBNET MASK   | GATEWAY     | PRIMARY DNS  | SECONDARY DNS | 
 | ----------- | ------------- | ----------- | ------------ | ------------- |
-| 192.168.3.4 | 255.255.255.0 | 192.168.3.1 | 192.168.3.25 | 192.168.3.26  |
+| 192.168.3.5 | 255.255.255.0 | 192.168.3.1 | 192.168.3.25 | 192.168.3.26  |
 
 ### Configure iSCSI Initiator to Connect to TrueNAS Core Server
 At this point, now that we have verified that the 10GbE NICs can ping their respective iSCSI target server IP addresses, we can add them to the iSCSI Initiator in Server Manager which will allow us to mount the cluster storage for the Hyper-V Failover Cluster.