2013R2_11.1.4.55331 SRD Network Issue

Does this apply? https://www.veritas.com/support/en_US/article.000100493

I'm afraid it doesn't.

The Windows 10 Pro was a clean install and not an upgrade from other versions of Windows.

Plus I have no problems creating the SRD, the problems only occur when trying to use the SRD with networking.

Is there a difference in the output when running IPCONFIG via each SRD? It maybe that the Win 10 based SRD is picking up the wrong NIC driver.

Hello,

The ipconfig I posted in the original post was for the Win 10 based SRD.

Here is the ipconfig from the Win 8 based SRD.

Windows IP Configuration

   Host Name . . . . . . . . . . . . : minint-p114p9b
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : home.gateway

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : home.gateway
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-1D-7D-04-88-93
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4900:3174:677b:e939%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, February 2, 2016 10:16:36 AM
   Lease Expires . . . . . . . . . . : Wednesday, February 3, 2016 10:16:35 AM
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 50339197
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-41-B4-C4-00-1D-7D-04-88-93
   DNS Servers . . . . . . . . . . . : 192.168.1.254
   NetBIOS over Tcpip. . . . . . . . : Enabled

That all looks fine to me.

Despite the error you see when trying to map a drive, have you tested that ping works? So ping from the recovery environment to the NAS. Also ping from another machine to the recovery environment IP address.

Do both work?

Hello,

I've just pinged from my recovery environment to my NAS and from my NAS to my recovery environment. Both were successful.

I again tried mapping using the GUI which continued to fail.

However I have just tried entering the "net use" command from the command shell which successfully mapped the drive, so I suspect there is a bug in the GUI implementation.

Glad to hear it's working.

I found this which may explain the issue you are seeing: https://forum.synology.com/enu/viewtopic.php?f=49&t=106924&start=15

I've been looking at that but I'm not sure if it is the cause of my issue (bit I could be wrong) as I can mount shares with the "net use" command but not the GUI.

Is there anyway I can include a custom command file in my SRD boot so I can automatically run the net use command everytime it boots up? This would then be a workaround for me.

I will check what command is run in the background when using the GUI option to map a drive.

There is nothing within the product that will allow you to do what you are asking with a custom command file. You will probably need to look to see what you can do using DISM (https://technet.microsoft.com/en-gb/library/hh825236.aspx).

Hi,

If I am recalling correctly,  I have seen the error  "A specified logon session does not exist. It may already have been terminated."  many times over the years on various versions of the SRD environment when trying to map a network drive.  The error occurs after entering the user credentials for the share.  The problem disappeared on the version before SP4 (SP3 I think) but resurfaced with SP4. Historically, I simply choose "Connect using different credentials" and the mapping is always successful.

This problem has been around for a while.  I also use a Synology NAS.

CQ