Can only connect to network share using IPaddress


  1. Posts : 4
    Windows 10
       #1

    Can only connect to network share using IPaddress


    HI there.

    New to the group so Hi everyone and I hope you can shed some light on this....

    I have 2 new PC's set up and running, connected to a NAS via a Switch. Internet is available via a router.

    I need to be able to access folders on and from both machines. I have shared C: on both, given permissions on both (everyone = Full control)

    I can see the relevant machines in the network section of Windows Explorer (master & backoffice). Sometimes I can see C: on the other machine but I can not connect to it. If I Double click I get "path not found" error ( 80070035 I think )..... \\master\c

    If I type in using the IPaddress it connects and works fine.... \\192.168.1.69\c

    It seems that once I've used the IPaddress method, it can sometimes use the name method ( But this is hit and miss )

    What have I missed....?? it's driving me nuts.
      My Computer


  2. Posts : 4
    Windows 10
    Thread Starter
       #2

    Well... Looks like it's something to do with DNS.. It doesn't resolve properly.

    The first PC (master) is now working but the other refuses to resolve the master name.

    Ping master now resolves to the wrong ipaddress and therefore fails.

    Ping ipaddress works fine.

    Seeing alot of people with this and similar issues but not alot of fixes...

    Still looking for help and advice.
      My Computer


  3. Posts : 193
    Windows 10 Pro
       #3

    Firstly the correct address with the IP is: \\192.168.1.69\c$
    Secondly, if you have no local name resolution method (DNS for example) then you have to use IP address. You could edit your hosts file if this is a permanent name designation.
      My Computer


  4. Posts : 4
    Windows 10
    Thread Starter
       #4

    Thanks for the reply.....

    Looks like i've found the issue.... Nothing wrong with the machine after all. 'twas the router at fault . It had the DNS Names resolution table and this table had the wrong information..... Hostnames pointing to incorrect ip addresses.

    Ended up having to do a factory reset because there is no other way of deleting old/incorrect listings.

    Once this was done, all worked as expected.
      My Computer


 

  Related Discussions
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:34.
Find Us




Windows 10 Forums