One PC Can't find others on the same network

I have 3 PC's and a laptop on a homegroup/network

All computers were able to see and access files and external
hard drives - until a power failure.

Now, one computer displays the other 3 computers / by name
under "network"

However, when I click on any of the icons in network, this error
message comes up:
*********************************
Network Error
Windows cannot access \\Supercomputer (or any of the other
computers)

Check the spelling of the name. Otherwise, there might be a
problem with your network. To try to identify network problems
,click Diagnose.

It also shows Error Code: 0x80070035 - the network path was not
found

(I do not understand why we cannot "right click/copy" error messages?????)

the message reads something to the affect of... can't find it..
make sure it's turned on and connected to the network..
****************************************

If the little computer can't find the other computers, how/why
is it displaying their names in "Network"??

I have 2 external drives that I use between all of the computers
and it's a royal PITB to not be able to access them from this one
PC.

Someone made a work around for me (unfortunately, I don't
remember what they did) - and during the last power outage,
the work around broke

I have tried turning the firewalls off... no difference

I have dumped all computers from homegroup and set a new one
up... no difference...

I will greatly appreciate a solution or work around for this issue.

OS - Windows 10/64 on all computers.
3 on DSL
Laptop on wifi

Thank you
Karen

Check that the names map to the correct IP addresses.

On an invisible computer, open a command window and get the IP address using

> ipconfig

The active IP will probably be found in the entry for 'Local Area Connection', it will be something like 192.168.0.<something>. The 0 could be a 1. The address you're looking for is the IPv4 address.

Now go to the computer that can't see the others and ping the name through a command window:

> ping <invisible>

The ping will return the IP address for the name. If the IP listed for the name does not match the IP of the lost computer, then try

> ping <invisible's real IP>

If you get a response then you have a DNS issue.

> ipconfig /flushdns

The open in notepad : C:\Windows\system32\drivers\etc\hosts

and add to that file the entry for your invisible computer

192.168.0.<whatever> myinvisiblecomputer

Save the file, then try your connection through the name.

This will be a 'permanent' fix only if the invisible computer has a static IP. If you are using DHCP then you may have an issue after rebooting the invisible computer.

Hi Karen. If you get this fixed I hope you will either post the fix or mark a response as being the fix. I have been chasing this problem for a week now. I won't say that I've tried everything since I clearly haven't tried the thing that fixes it. I'm beginning to think my problem is with the Win10 Creator Update (1703) and I just recently noticed it because I don't open the Network folder very often.

hymanwallace said:

Check that the names map to the correct IP addresses.

On an invisible computer, open a command window and get the IP address using

> ipconfig

The active IP will probably be found in the entry for 'Local Area Connection', it will be something like 192.168.0.<something>. The 0 could be a 1. The address you're looking for is the IPv4 address.

Now go to the computer that can't see the others and ping the name through a command window:

> ping <invisible>

The ping will return the IP address for the name. If the IP listed for the name does not match the IP of the lost computer, then try

> ping <invisible's real IP>

If you get a response then you have a DNS issue.

> ipconfig /flushdns

The open in notepad : C:\Windows\system32\drivers\etc\hosts

and add to that file the entry for your invisible computer

192.168.0.<whatever> myinvisiblecomputer

Save the file, then try your connection through the name.

This will be a 'permanent' fix only if the invisible computer has a static IP. If you are using DHCP then you may have an issue after rebooting the invisible computer.

********************************
I did the ipconfig for "supercomputer" (one with the external
hard drives that need to be used by all PC's)

This is what came back:

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::79d9:dacd:dfbc:b239%11
IPv4 Address. . . . . . . . . . . : 192.168.1.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

I copied 192.168.1.16 and went to "little computer"
and pinged that IP address and this is what came
back:


C:\WINDOWS\system32>ping 192.168.1.16

Pinging 192.168.1.16 with 32 bytes of data:
Reply from 192.168.1.16: bytes=32 time=1ms TTL=64
Reply from 192.168.1.16: bytes=32 time<1ms TTL=64
Reply from 192.168.1.16: bytes=32 time<1ms TTL=64
Reply from 192.168.1.16: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

and this is sort of where I get lost with your directions.

I will greatly appreciate more clairification....

"Little Computer" - one that cannot access other PC/hard drives
In the network
"Super Computer" - one that has the external hard drives necessary
for ALL computers <== "invisible computer" ???

"If the IP listed for the name does not match the IP of the lost computer, then try..."

Thank you so very much for your help

Karen

I may have misunderstood ....

I just went to little computer and entered

>ping supercomputer and the result
Ping request could not find host SuperComputer. Please check
the name and try again.

I did the same on supercomputer for little computer
and this is what came back

C:\WINDOWS\system32>ping little-computer

Pinging Little-computer [fe80::148a:8903:dd95:15b4%11] with 32 bytes of data:
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms

Ping statistics for fe80::148a:8903:dd95:15b4%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

To the best of my knowledge, the IP addresses are
static

do I flush dns cache on both?

**this goes in Little-Computer: ?????

Then open in notepad : C:\Windows\system32\drivers\etc\hosts
and Add this: 192.168.1.16 SuperComputer ???

I just followed the path and took a look at hosts

I have a vague recollection of hearing the easiest way
to edit "hosts" is to drag it over to your desktop - add
what you want to add / save and drop it back into the
etc folder????

and, is this what the line should read:

# 192.168.1.16 SuperComputer

and, does it matter where this is placed on the
hosts page?

If I want to access the other two computers, I will
do the same process for them?

thank you many bunches... I hope I've got this straight

I'll wait for your confirmation or correction before
proceeding.

ginormous hugs to you
Karen

Yes. If we are on track, then the addition to your hosts file should do the trick. The line you suggest is correct.

You can put it anywhere in the hosts file though it is standard to put it after the first group of entries. It is important that the modified file be in the same location. Do not save it to your desktop.

If you navigate via command file to the etc directory and then

>notepad hosts

Then change and save the file in notepad you will leave the file in the correct place.

Good luck.

kstavert said:

I may have misunderstood ....

I just went to little computer and entered

>ping supercomputer and the result
Ping request could not find host SuperComputer. Please check
the name and try again.

I did the same on supercomputer for little computer
and this is what came back

C:\WINDOWS\system32>ping little-computer

Pinging Little-computer [fe80::148a:8903:dd95:15b4%11] with 32 bytes of data:
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms

Ping statistics for fe80::148a:8903:dd95:15b4%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

To the best of my knowledge, the IP addresses are
static

do I flush dns cache on both?

**this goes in Little-Computer: ?????

Then open in notepad : C:\Windows\system32\drivers\etc\hosts
and Add this: 192.168.1.16 SuperComputer ???

I just followed the path and took a look at hosts

I have a vague recollection of hearing the easiest way
to edit "hosts" is to drag it over to your desktop - add
what you want to add / save and drop it back into the
etc folder????

and, is this what the line should read:

# 192.168.1.16 SuperComputer

and, does it matter where this is placed on the
hosts page?

If I want to access the other two computers, I will
do the same process for them?

thank you many bunches... I hope I've got this straight

I'll wait for your confirmation or correction before
proceeding.

ginormous hugs to you
Karen

Yes. If we are on track, then the addition to your hosts file should do the trick. The line you suggest is correct.

You can put it anywhere in the hosts file though it is standard to put it after the first group of entries. It is important that the modified file be in the same location. Do not save it to your desktop.

If you navigate via command line to the etc directory and then

>notepad hosts

Then change and save the file in notepad you will leave the file in the correct place.

Good luck.

kstavert said:

I may have misunderstood ....

I just went to little computer and entered

>ping supercomputer and the result
Ping request could not find host SuperComputer. Please check
the name and try again.

I did the same on supercomputer for little computer
and this is what came back

C:\WINDOWS\system32>ping little-computer

Pinging Little-computer [fe80::148a:8903:dd95:15b4%11] with 32 bytes of data:
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms
Reply from fe80::148a:8903:dd95:15b4%11: time<1ms

Ping statistics for fe80::148a:8903:dd95:15b4%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>

To the best of my knowledge, the IP addresses are
static

do I flush dns cache on both?

**this goes in Little-Computer: ?????

Then open in notepad : C:\Windows\system32\drivers\etc\hosts
and Add this: 192.168.1.16 SuperComputer ???

I just followed the path and took a look at hosts

I have a vague recollection of hearing the easiest way
to edit "hosts" is to drag it over to your desktop - add
what you want to add / save and drop it back into the
etc folder????

and, is this what the line should read:

# 192.168.1.16 SuperComputer

and, does it matter where this is placed on the
hosts page?

If I want to access the other two computers, I will
do the same process for them?

thank you many bunches... I hope I've got this straight

I'll wait for your confirmation or correction before
proceeding.

ginormous hugs to you
Karen

kstavert said:

I have 3 PC's and a laptop on a homegroup/network

All computers were able to see and access files and external
hard drives - until a power failure.

Now, one computer displays the other 3 computers / by name
under "network"

However, when I click on any of the icons in network, this error
message comes up:
*********************************
Network Error
Windows cannot access \\Supercomputer (or any of the other
computers)

Check the spelling of the name. Otherwise, there might be a
problem with your network. To try to identify network problems
,click Diagnose.

It also shows Error Code: 0x80070035 - the network path was not
found

(I do not understand why we cannot "right click/copy" error messages?????)

the message reads something to the affect of... can't find it..
make sure it's turned on and connected to the network..
****************************************

If the little computer can't find the other computers, how/why
is it displaying their names in "Network"??

I have 2 external drives that I use between all of the computers
and it's a royal PITB to not be able to access them from this one
PC.

Someone made a work around for me (unfortunately, I don't
remember what they did) - and during the last power outage,
the work around broke

I have tried turning the firewalls off... no difference

I have dumped all computers from homegroup and set a new one
up... no difference...

I will greatly appreciate a solution or work around for this issue.

OS - Windows 10/64 on all computers.
3 on DSL
Laptop on wifi

Thank you
Karen

Karen,
if you haven't found a solution I suggest this:

drop the homegroup

enroll all computers in a workgroup.......... MSHOME... is fine

each machine should issue a Welcome to MSHOME

reboot each machine

all shares in all machines should appear under computer names in Network folder on each machine

to add the external drives dbl click Network and use Add Devices from the menu

if any device is not listed...............

go to This PC and use Add Network location

this should give you a shortcut on C:\ for that device

Your post from ipconfig seems incomplete
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::79d9:dacd:dfbc:b239%11
IPv4 Address. . . . . . . . . . . : 192.168.1.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Doesnt it state dns

Does it have netbios running if it doesnt then it wont be seen by pcs as thats whats used on lan to find pcs