Windows 10: Network source is not accessible via name

Discus and support Network source is not accessible via name in Windows 10 Network and Sharing to solve the problem; Hi All! I would like to reach one of our linux servers via computer name with AD users credantial, but it doesn't work: C:\Users\a>net use... Discussion in 'Windows 10 Network and Sharing' started by Alex8000, Nov 30, 2020.

  1. Alex8000 Win User

    Network source is not accessible via name


    Hi All!



    I would like to reach one of our linux servers via computer name with AD users credantial, but it doesn't work:


    C:\Users\a>net use \\jean-dev

    System error 1396 has occurred.
    The target account name is incorrect.



    But via ip address works correctly:
    C:\Users\a>net use \\192.168.1.219
    The command completed successfully.



    I can ping or telnet this linux server via computer name , dns records are good.




    What is the problem the "account name" via computer name?

    Is it a Windows or linux problem?


    Thanks in advance!

    :)
     
    Alex8000, Nov 30, 2020
    #1
  2. taward Win User

    One computer cannot access other network computers.


    So I've tried every troubleshooting step I know:
    • Double checked that Net Bios was enabled
    • Ran a bunch of network commands:
      • flushed DNS
      • registered dns
      • pinged and located the named computers successfully
    • Reset my router to factory settings

    Nothing works when I try to access via explorer. I'm still baffled by the fact that every other computer can access each other AND access this computer. It's just the outgoing connection from this machine that doesn't work.

    Any thoughts?
     
    taward, Nov 30, 2020
    #2
  3. Office 365 Word: Mail Merge - Is it Supported for editing if the Source file is Saved in a Network Shared Drive?

    Hi RaiO365,

    I tested on my side step by step according to the steps you provided for me, and the result was same with you.
    It may be because the way to access local files and access files on the network drive is different, so it can be saved after changing the source file locally, but not on the network drive.

    My suggestion is that you can update source file first, then mail merge file.

    Regards,
    Jazlyn
     
    Jazlyn Xu MSFT, Nov 30, 2020
    #3
  4. Network source is not accessible via name

    Edge Search Does Not Permit Change of Region


    I got these suggestions from the Microsoft Community forum.No. 1 worked for me:

    Thank you for posting the query on Microsoft Community. I am glad to assist you on this.
    We have reproduce the issue here and we are able to access non-regional search for google using Microsoft Edge.
    I would suggest you to try the below steps and check if it helps.
    Step 1:
    Clear browsing data option of Microsoft Edge and check if you face the issue. To do so perform the steps below.

    1. Click on the More actions icon next to the feedback icon present on top right corner of the Project Spartan homepage.
    2. Select Settings and click on Choose what to clear.
    3. Check the boxes Browsing history, Cookies and saved website data and Cached data and files and click on Clear.
    Step 2:
    I suggest you to create a new user account and check if the issue occurs.

    1. Go to Settings.
    2. Choose Accounts and then select Family and other users.
    3. Select add someone else on this PC.
    4. Enter a user name and hit next.
    5. Click on Finish.
    6. Sign out from the current Account and Log into the new account.
    Step 3:
    It could also happen because of network issue. I suggest you to try with different network connection and check if it helps.
     
    hurricane51, Nov 30, 2020
    #4
Thema:

Network source is not accessible via name

Loading...
  1. Network source is not accessible via name - Similar Threads - Network source accessible

  2. Unable to access Server via Server Name but can via IP

    in Windows 10 Gaming
    Unable to access Server via Server Name but can via IP: I have a Windows Server 2019 Domain. I'm not able to acces the Server from Windows 10 Domain Clients by its Name but can do so with IP. When I ping Server name from problem computers I get the correct Server IP. I have tried ipconfig /flushdns with no success.When I try to...
  3. Unable to access Server via Server Name but can via IP

    in Windows 10 Software and Apps
    Unable to access Server via Server Name but can via IP: I have a Windows Server 2019 Domain. I'm not able to acces the Server from Windows 10 Domain Clients by its Name but can do so with IP. When I ping Server name from problem computers I get the correct Server IP. I have tried ipconfig /flushdns with no success.When I try to...
  4. Unable to access Server via Server Name but can via IP

    in Windows 10 Network and Sharing
    Unable to access Server via Server Name but can via IP: I have a Windows Server 2019 Domain. I'm not able to acces the Server from Windows 10 Domain Clients by its Name but can do so with IP. When I ping Server name from problem computers I get the correct Server IP. I have tried ipconfig /flushdns with no success.When I try to...
  5. Networked PC's on Windows 10: Can access via //computer name, but not in file explorer

    in Windows 10 Gaming
    Networked PC's on Windows 10: Can access via //computer name, but not in file explorer: Seems many encounter difficulties with networking with Windows 10. After a review of multiple web site posts, I remain confused.I have three PC's 1 Windows 7, 2 Windows 10 hard wired to a router, and one notebook via WiFi. All have the same network name.The only PC which...
  6. Networked PC's on Windows 10: Can access via //computer name, but not in file explorer

    in Windows 10 Software and Apps
    Networked PC's on Windows 10: Can access via //computer name, but not in file explorer: Seems many encounter difficulties with networking with Windows 10. After a review of multiple web site posts, I remain confused.I have three PC's 1 Windows 7, 2 Windows 10 hard wired to a router, and one notebook via WiFi. All have the same network name.The only PC which...
  7. Networked PC's on Windows 10: Can access via //computer name, but not in file explorer

    in Windows 10 Network and Sharing
    Networked PC's on Windows 10: Can access via //computer name, but not in file explorer: Seems many encounter difficulties with networking with Windows 10. After a review of multiple web site posts, I remain confused.I have three PC's 1 Windows 7, 2 Windows 10 hard wired to a router, and one notebook via WiFi. All have the same network name.The only PC which...
  8. NAS only accessible via WINS name, but not via IP address

    in Windows 10 Network and Sharing
    NAS only accessible via WINS name, but not via IP address: In one network I manage I sometimes get this strange error. The NAS is perfectly accessible via its name \\LAGRING but using its IP address \\172.24.57.3 gives an error the error message suggests it is unavailable or that you don't have access rights. I have not found a...
  9. Server network cannot access with name but accessible with ip

    in Windows 10 Network and Sharing
    Server network cannot access with name but accessible with ip: I have a Server and a few windows 10 computers in my office. Usually i can access the server network from all computers by typing \\"servername". I restarted the server today morning and after that two of my windows 10 computers dont connect to server when I type...
  10. source of network credentials

    in Windows 10 Network and Sharing
    source of network credentials: When trying to connect back to my desktop commuter from my laptop I am required to ENTER NETWORK CREDENTIALS. My MS account password does not work. Is there another password for my desktop?...