Page 1 of 2 12 LastLast

  1. Joined : May 2016
    Connectiicut - USA
    Posts : 15
    Window 10 Professional 64
       18 Oct 2016 #1

    “The specified network name is no longer available”


    I have six systems in my home, five running Windows 10 with the Anniversary update and a sixth that just won’t take it yet, and is stuck with the original Win 10.

    All of these are somewhat networked together, along with several more that are not in our home. (I use Hamachi to connect these.) The home systems are ALSO linked to shared storage off the Linksys router.

    Recently, my Qosmio 870 developed amnesia when it came to Cortana. Nothing I tried would recover the search engine. Today I tried re-installing Windows 10 Pro from the most current installation download.

    Cortana is back in full bloom, and aside for those pesky shortcut arrows returning, all seemed right with the world…

    Except!! My router-shared storage is unreachable. I can no longer map to the router. I attempt mapping (\\RouterName\Sharestorage) and get … “The specified network name is no longer available”. All the other systems are fine and I AM online to/with my router.

    I reverted the system to “Before the update”, and all is well with the router, but of course I don’t have Cortana.

    I’d welcome any advice anyone might offer. I’m not sure what to try next.

    Thanks.
    JLOB
      My System SpecsSystem Spec

  2.    18 Oct 2016 #2

    Have you tried using the IP address UNC syntax? It just tried it on my network and was able to type

    net use \\192.168.0.2\<sharename>

    and immediately got access that way. If you're having trouble with name resolution maybe you can use the IP address instead.
    HTH,
    --Ed--
      My System SpecsSystem Spec


  3. Joined : Aug 2016
    S/E England
    Posts : 815
    10 Home x64 (1607), Pro x86 (1511)
       18 Oct 2016 #3

    JLOB said: View Post
    I can no longer map to the router. I attempt mapping (\\RouterName\Sharestorage) and get … “The specified network name is no longer available”.
    For a Windows 10 PC to be able to see a UNC resource of the form \\<device name>\<share name> then both devices should be in the same Workgroup and Network Discovery should be turned on. It may well be that when you reinstalled Windows 10 it was set to a default Workgroup name different from that of your router.

    My router came pre-configured with a Workgroup of HOME. There are no user settings to change this, so all PC on my network (W10, W7, XP and on rare occasions W95) have to be set to be in the HOME Workgroup. They can all see each other's shares and a USB HDD shared by plugging it into the USB port on my router.

    To check/change the Workgroup of a W10 system, go to Control Panel\All Control Panel Items\System and click 'Advanced system settings' (or just type Workgroup in the Search box). Look on the 'Computer name' tab.

    For Network Discovery settings, go to Control Panel\All Control Panel Items\Network and Sharing Centre\Advanced sharing settings
      My System SpecsSystem Spec


  4. Joined : May 2015
    Central IL
    Posts : 2,951
    EL Capitan
       18 Oct 2016 #4

    Sounds like the Router needs to be turned off and back on to clear its temporary storing of the network info, same as the devices need to have the cache, etc. cleared to flush out old information.
      My System SpecsSystem Spec


  5. Joined : Nov 2014
    The Netherlands
    Posts : 144
    Win 10 Pro x64 1607 (Build 14393.447)
       19 Oct 2016 #5

    EdTittel said: View Post
    Have you tried using the IP address UNC syntax? It just tried it on my network and was able to type

    net use \\192.168.0.2\<sharename>

    and immediately got access that way. If you're having trouble with name resolution maybe you can use the IP address instead.
    HTH,
    --Ed--
    Hi Ed, worked for me, as both my Windows 10 and NAS DS1812 are in "WORKGROUP",but in Windows 10 Finder I have no luck conncting to it. I reset the Credential Managers login (Enterprise)

    Code:
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    C:\Windows\system32>net use \\DS1812
    System error 53 has occurred.
    The network path was not found.
    
    C:\Windows\system32>net use \\DS1812.local
    System error 53 has occurred.
    The network path was not found.
    
    C:\Windows\system32>net use \\192.168.178.125
    The password or user name is invalid for \\192.168.178.125.
    Enter the user name for '192.168.178.125': *****
    Enter the password for 192.168.178.125:
    The command completed successfully.
    
    C:\Windows\system32>

    EDIT: some more basic network tests:

    Code:
    C:\Windows\system32>ping 192.168.178.125
    
    
    Pinging 192.168.178.125 with 32 bytes of data:
    Reply from 192.168.178.125: bytes=32 time<1ms TTL=64
    Reply from 192.168.178.125: bytes=32 time<1ms TTL=64
    Reply from 192.168.178.125: bytes=32 time<1ms TTL=64
    Reply from 192.168.178.125: bytes=32 time<1ms TTL=64
    
    
    Ping statistics for 192.168.178.125:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    Code:
    C:\Windows\system32>net view 192.168.178.125
    Shared resources at 192.168.178.125
    
    Share name    Type  Used as  Comment
    -------------------------------------------------------------------------------
    backup        Disk           Backups
    home          Disk           home
    homes         Disk           user home
    music         Disk           System default shared folder
    photo         Disk           System default shared folder
    Plex          Disk           Plex Media Library
    surveillance  Disk           System default shared folder
    Time Machine  Disk           Apple Time Machine Backups
    video         Disk           System default shared folder
    web           Disk           System default shared folder
    The command completed successfully.
    
    C:\Windows\system32>

    So I (and a lot more users) are stil left SUFFERING from this crazy error. I also have some very strange issues with the NVidia 373.06 WHQL drivers. NO, these late updates DON'T JUST WORK!!! /rant

    Overall very disappointed in these latest flaws in M$ updates/grades!

    Cheers
      My System SpecsSystem Spec


  6. Joined : Nov 2014
    The Netherlands
    Posts : 144
    Win 10 Pro x64 1607 (Build 14393.447)
       19 Oct 2016 #6

    RESOLVED my network issue!


    FWIW to others users: RESOLVED my network issue!

    It seems that the latest AE 1607 build and updates KILLED my bridge (2 GB/s) of 2 NIC's in my Mac Pro. Deleted the bridge, disabled 1/2 NIC's in Device Manager and set up a new WLAN:

    Click image for larger version. 

Name:	2016-10-19_16-45-33.png 
Views:	4 
Size:	27.1 KB 
ID:	106654

    Code:
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    C:\Windows\system32>net view
    
    Server Name            Remark
    -------------------------------------------------------------------------------
    \\DS1812
    \\WIN10PROX64          Windows 10 Professional x64 - 1607
    \\ZIGGO-NAS            TC7200-DMS Gateway
    The command completed successfully.
    
    
    C:\Windows\system32>net view \\DS1812
    
    Shared resources at \\DS1812
    
    Share name    Type  Used as  Comment
    -------------------------------------------------------------------------------
    backup        Disk           Backups
    home          Disk           home
    homes         Disk           user home
    music         Disk           System default shared folder
    photo         Disk           System default shared folder
    Plex          Disk           Plex Media Library
    surveillance  Disk           System default shared folder
    Time Machine  Disk           Apple Time Machine Backups
    video         Disk           System default shared folder
    web           Disk           System default shared folder
    
    The command completed successfully.
    
    
    C:\Windows\system32>

    Cheers
      My System SpecsSystem Spec


  7. Joined : May 2016
    Connectiicut - USA
    Posts : 15
    Window 10 Professional 64
       19 Oct 2016 #7

    Ed,

    Thanks but that didn't do it.

    JLOB
    Attached Thumbnails Attached Thumbnails Image3.jpg   Image1.jpg   Image2.jpg  
      My System SpecsSystem Spec


  8. Joined : May 2016
    Connectiicut - USA
    Posts : 15
    Window 10 Professional 64
       19 Oct 2016 #8

    bro67 said: View Post
    Sounds like the Router needs to be turned off and back on to clear its temporary storing of the network info, same as the devices need to have the cache, etc. cleared to flush out old information.
    Tried that. No joy. Thanks for trying, however.
      My System SpecsSystem Spec

  9.    19 Oct 2016 #9

    Are you sure you have the right IP address for the remote device with the shared resource? In my experience if you haven't changed the default address, it's 192.168.0.1 for most routers (but sometimes 192.168.1.1). Get yourself an IP scanning utility and confirm that the address is correct, or run ipconfig and use the address for the "default gateway" as shown here:
    Click image for larger version. 

Name:	defgate.jpg 
Views:	29 
Size:	58.2 KB 
ID:	106718
    The address I gave you was just an example (it's actually the address from my wife's PC on my LAN, to which I navigated to make sure the syntax was correct and acceptable to Windows 10).
    HTH,
    --Ed--
      My System SpecsSystem Spec


  10. Joined : May 2016
    Connectiicut - USA
    Posts : 15
    Window 10 Professional 64
       20 Oct 2016 #10

    Ed,

    This gets curiouser and curiouser! The default gateway is 192.168.1.1. I CANNOT connect using that IP and the latest update. I reverted to my previous Win 10 build and can easily connect using the IP rather than the \\Shamrock-2. Of course, there’s no Cortana. I'm missing something somewhere.

    JLOB

    Click image for larger version. 

Name:	try4.jpg 
Views:	23 
Size:	31.6 KB 
ID:	106831
      My System SpecsSystem Spec


 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Network bridge no longer working
Hi, I'm having major problems bridging 2 network connections.... I usually run a bridge between the 2 onboard lan ports on my pc which connect to a second pc to give it internet and it has worked perfectly fine since I moved to windows 10 however...
Network and Sharing
Desktop no longer in network
Hi guys - here goes: Upgraded win7 to win10 yesterday on my desktop (free from MS). So far so good, EXCEPT - I can no longer print from my win10 laptop - it cannot see the printer connected to my desktop. Nor can I see my desktop in the network...
Network and Sharing
Open network no longer works
Prior to W10 I had a network NOT using Homegroup. Network worked who needs it? Now, I see some of my devices on the network, but when I try to share files I get a window requesting user name and password. Never used passwords before. I think...
Network and Sharing
Solved Network was fine - no longer working
EDIT FOR SOLUTION: My friend came over this morning and fixed this for me. The problem was the (1) Laptop was logged into my Windows Live account and the (2) Desktops were logged into Local Accounts. For some reason, this now prevents my laptop...
Network and Sharing
No longer see Network Attached Storage in Network View on Build 10049
I can no longer see my Network Attached Storage in this build(10049) Enterprise. I have Network Discovery enabled and can get to the device by IP Address in a browser but am unable to map a drive to any share. Anyone else having these issues. I have...
Network and Sharing
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:07.
Find Us
Twitter Facebook Google+



Windows 10 Forums