Server Shares become unshared if source volume is unavailable at Boot-up. Is this normal?


hello,

 

my windows server 2003 std, sp2   file server has iscsi connector our san.  recently, during routine maintenance, technician reconnected nic's incorrectly, causing file server unable contact san during boot-up.

as far tell shares pointing volume disappeared os. multiple other shares hosted on local disk volumes remained intact.

we recreated shares, , have remained stable through few multiple warm boots since then. unable find corresponding event log entries indicating shares removed, except 2 system errors confirming server failed contact other side of iscsi connector.

my question has 2 parts:

1. is behavior normal , expected?    

 2. also, there chance action disrupt existing ntfs permissions?

 

thanks in advance!



hi,

as drive letter , folder path not change after reconnecting iscsi lun, may able restore shares restoring related registry keys. see:

saving , restoring existing windows shares

http://support.microsoft.com/kb/125996


technet subscriber support in forum |if have feedback on our support, please contact tnmff@microsoft.com.


Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL