Windows, network, or server issue??

Soldato
Joined
17 May 2013
Posts
2,943
Location
West Sussex, UK
I have a home server running unRaid.

When I boot my PC it won't connect the mapped network drive.

Wheb navigating to the server in Windows Explorer I get
"Windows cannot access \\SERVER" "Error code 0x80070035, The network path was not found".

I click 'Diagnose', it runs the troubleshooter for 5 seconds than says it can't identify the problem.

I close the window and access is returned, and everything works as it should.

PS. Before writing this I didn't originally see that error code. I'll do some searching now.
 
It's probably a DNS issue. You don't have anything to resolve local DNS, so it takes a minute or two to realise. If you have a static IP address on the home server, I would simply add a host file entry to the Windows machine.
 
I had a similar issue at the start of the year, network drives would show disconnected and would have to double click on them all to open them and reconnect them. Apparently it was a Win10 patch that broke it (to do with your network card not being ready when windows wants to mount the drives) I discovered a script that would do the trick and just have it to run at logon.

Code:
@echo off
PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%\StartupLog.txt"  2>&1
PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" >> "%TEMP%\StartupLog.txt" 2>&1

Create a CMD file with the above in it at the following location

C:\Users\(Your User Profile name)\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

At the location C:\scripts

create a file called MapDrives.ps1 with the following in it

Code:
$i=3
while($True){
    $error.clear()
    $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath
    foreach( $MappedDrive in $MappedDrives)
    {
        try {
            New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
        } catch {
            Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
        }
    }
    $i = $i - 1
    if($error.Count -eq 0 -Or $i -eq 0) {break}

    Start-Sleep -Seconds 30

}

It looks like the most recent Win10 update (2004) has fixed it for me.
 
Thanks both, I'll try this when I can use it again. Currently having HDD problems with the server. Seemed like a good idea at the time
 
Back
Top Bottom