netapp 建立iscsi 並掛載到windows

 netapp(8.2.3P3 )建立iscsi磁碟步驟(web console操作)，並在windows server掛載:

1 在netapp的Storage -> Volumes ，執行Create，建立過程要選iscsi，並設定容量。

2 在netapp的Configuration-> iSCSI，啟用iscsi服務，要輸入目標節點名稱，會是iqn開頭的值。

3 在Windows 執行iscsi啟動器，輸入netapp的IP進行連線，連線成功，此時會在目標的頁籤看到netapp的節點名稱，如果剛剛在第二步沒找到節點名稱，就是輸入這個。

4 在設定這個頁籤，可以看到Windows 的啟動器名稱，也是iqn開頭的值，但跟netapp的節點名稱不一樣。

5 在netapp的Storage-> LUN，LUN管理裡執行Create一個LUN，這邊會連結到第一步建立的Volumes。

6 在netapp的Storage-> LUN，Initiator Group建立一個Group，建立時，會需要輸入第四步的Windows 的啟動器名稱。

7 在netapp的Storage-> LUN，LUN管理裡剛剛建立的LUN，連結到第六步建立的Initiator Group。

8 回到Windows 執行iscsi啟動器，重新連線，這時後再去磁碟管理中，就會看到多了一個新的磁碟，就是Netapp上iscsi分享出來的空間。

NetApp (8.2.3P3) iSCSI Disk Creation Steps (Web Console) and Mounting on Windows Server

1. Create a Volume on NetApp

   • Go to Storage → Volumes → Create

   • Select iSCSI during the creation process and set the desired capacity.

2. Enable iSCSI Service on NetApp

   • Go to Configuration → iSCSI → Enable iSCSI

   • Enter the Target Name, which will start with iqn.

3. Connect from Windows using iSCSI Initiator

   • Open the iSCSI Initiator on Windows and enter the NetApp IP to connect.

   • Once connected, you will see the NetApp Target Name under the Targets tab.

   • If you couldn’t find the Target Name in step 2, enter the one displayed here.

4. Check Windows Initiator Name

   • In the Configuration tab of the iSCSI Initiator, you can see the Windows Initiator Name, which also starts with iqn but is different from the NetApp Target Name.

5. Create a LUN on NetApp

   • Go to Storage → LUNs → Create

   • Link the new LUN to the Volume created in step 1.

6. Create an Initiator Group (igroup) on NetApp

   • Go to Storage → LUNs → Initiator Groups → Create

   • Enter the Windows Initiator Name from step 4 when creating the igroup.

7. Map the LUN to the Initiator Group

   • In Storage → LUNs, select the newly created LUN and map it to the igroup created in step 6.

8. Mount the LUN on Windows

   • Go back to Windows and reconnect using the iSCSI Initiator.

   • Then open Disk Management, and you should see a new disk representing the iSCSI space shared from NetApp.

WINDOWS11連線WINDOWS2003共用資料夾錯誤碼:0x80004005

 原本WINDOWS11連線WINDOWS2003共用資料夾都正常，但突然有一天卻無法連線，錯誤碼:0x80004005 。

利用WINDOWS7, 10, 2008, 2025都可以，非常奇怪。

最後解決方法是把WINDOWS11裡的SMB1.0 用戶端移除後重新安裝一次，就好了。

Originally, Windows 11 could connect to the Windows 2003 shared folder without any issues, but suddenly one day it stopped working, showing error code: 0x80004005.

Strangely, Windows 7, 10, 2008, and 2025 could all connect normally.

The final solution was to remove the SMB 1.0 client feature on Windows 11 and reinstall it, which fixed the problem.

DNS 有不同主機對應相同IP

網域的DNS主機中，發現有一些電腦已取到其他IP，但DNS上還會保留舊記錄，不會自動清除，其他電腦後來取得該IP時，DNS上就有兩台電腦對應同一個IP。

這就會造成連線電腦時，會連錯電腦。

檢查過DHCP，已經設定成動態更新DNS了，還是不會更新DNS記錄，後來查發現，DNS的設定中，也要把啟用動清除過時的記錄打勾，DNS裡的舊記錄才會被清除。

On the domain DNS server, it was found that some computers had already obtained new IP addresses, but the DNS still kept their old records without automatically clearing them. When another computer later obtained that same IP, the DNS ended up showing two computers mapped to the same IP address.

This caused connection issues, as attempts to connect to one computer could actually connect to the wrong one.

After checking the DHCP settings, it was confirmed that dynamic DNS update was already enabled, but the DNS records were still not being updated. Further investigation revealed that in the DNS settings, the option “Enable scavenging of stale records” must also be checked; only then will outdated DNS records be cleared.

SYNOLOGY 共用資料夾 誰在連線的資訊

 如果使用SYNOLOGY 當共用資料夾，想看目前誰有連線，開啟了什麼檔案:

開啟"資源監控"，進到"連線"，裡面就可以查看到相關訊息。

If you are using SYNOLOGY as a shared folder and want to see who is currently connected and which files are open:

Open Resource Monitor, go to Connections, and you will be able to view the relevant information there.