Windows 10: 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.

:)

 

All computer have disappeared in Network category

FYI do know anything about 'Creator's' edition discussed in your link. I am Win 10 home. Perhaps something related is in there I wWill try to digest the link its a long exchange, make take me a bit.

Here is what I got when I ran the nbstat -N command.

Not sure what I am looking for.

Ethernet:

Node IpAddress: [169.254.142.219] Scope Id: []

NetBIOS Local Name Table

Name Type Status

---------------------------------------------

ALBERT-ASUS <20> UNIQUE Registered

Wi-Fi:

Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Ethernet 3:

Node IpAddress: [10.0.0.10] Scope Id: []

NetBIOS Local Name Table

Name Type Status

---------------------------------------------

ALBERT-ASUS <20> UNIQUE Registered

Bluetooth Network Connection:

Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 5:

Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 6:

Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Wi-Fi 2:

Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Users\Albert>

 

HOTSPOT

Microsoft Hosted Network Virtual Adapter hosts a hotspot with an invalid ipaddress. What is the problem and how can one solve it?

 

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.

 

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.

 

Thanks for the reply.....

Looks like i've found the issue.... Nothing wrong with the machine after all. 'twas the router at fault *Mad. 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.