Computer not appearing in Network, but is accessible

[jon paterson]

I am running windows 10 Home version 1803 (OS build 17134.590) on my desktop computer.

From my desktop I can see the laptops in the house that are connected to the network. However, from the laptops I cannot see the desktop computer. Should I specifically give the host name for the Desktop to the laptop it will connect to it, but always requires me to enter the username and password for the admin account on the desktop.

Previously with the homegroup functionality I could access (read/write) all the files on any computer in the house from any computer in the house, but no longer.

What settings do I need to check to make my desktop visible on the network and remove the necessity to continually enter the username and password every time I want to connect to the desktop?

Thanks

 

[TechFreak1]

I am running windows 10 Home version 1803 (OS build 17134.590) on my desktop computer.

From my desktop I can see the laptops in the house that are connected to the network. However, from the laptops I cannot see the desktop computer. Should I specifically give the host name for the Desktop to the laptop it will connect to it, but always requires me to enter the username and password for the admin account on the desktop.

Previously with the homegroup functionality I could access (read/write) all the files on any computer in the house from any computer in the house, but no longer.

What settings do I need to check to make my desktop visible on the network and remove the necessity to continually enter the username and password every time I want to connect to the desktop?

Thanks

Have you tried re-enabling network discovery?

 

[jon paterson]

Yes network discovery is on, and I have told my desktop to share the printer and files from the users directory on down the tree

 

[TechFreak1]

Yes network discovery is on, and I have told my desktop to share the printer and files from the users directory on down the tree

Hmm, are the networks on the laptops set to public?

Also did this start happening after a cumulative update?

There have been issues with cumulative updates for awhile now...

 

[jon paterson]

All the networks are set to private. I eventried changing them to public then back to private.

It all happened after a cumulative update. My hard drive died and I had to do a fresh install of windows 10, after reinstalling windows 7. Since then I have been having this problem.

I know it should work, since it has worked, so it's a configuration problem. I'm just not sure what to configure.

 

[skcusime]

A couple of links to try....

https://www.youtube.com/watch?v=iHCu6lCWgSI

https://www.youtube.com/watch?v=5bIcJluf-0Q

 

[TechFreak1]

All the networks are set to private. I eventried changing them to public then back to private.

It all happened after a cumulative update. My hard drive died and I had to do a fresh install of windows 10, after reinstalling windows 7. Since then I have been having this problem.

I know it should work, since it has worked, so it's a configuration problem. I'm just not sure what to configure.

Hmm, have you checked your windows firewall settings?

Also have you checked the services.msc if the workstation service is running or not?

 

[jon paterson]

I actually turned off Windows Firewall completely because it was causing all sorts of problems with my networking, but the problem still persists.

I did check the Workstation service and it was running and was set to automatic.

 

[jon paterson]

THanks! The computer is now appearing in the Network Section, but it is still asking me for the login information when I try to access anything on the desktop computer. Is there any way around that?

 

[midnightfrolic]

go into network sharing and disable require password. should be same place where you enable network discovery. should be under the ALL NETWORK section, under.

otherwise try 'guest' and no password

 

[flycaster1]

Interestingly, I have had the same problem when networking a new Surface Pro 6 to an HP Envy desktop. I did everything except that which is recommended in the first video tutorial (make some services automatic.) So, initially, my surface pro listed both computers under Network. But, the HP never listed the surface pro or itself, while both computers were listed with the surface pro...even though everything I had done, up to the video, was correct. However, I knew that the two computers were networked as I was able to use Logitech's M570 mouse's Flow function (can cut/paste between computers with just using this mouse) and was able to view files/folders on both computers.

So, I just want to say that the video solved the problem. And, of course, thanks guys...

EDIT: Spoke a little too soon. Both computer can communicate back and forth, and both are listed under Network. However, when selected under Network in either computer, only the desktop shows Users and Windows Apps. There is nothing under the Surface Pro???

 

[TechFreak1]

THanks! The computer is now appearing in the Network Section, but it is still asking me for the login information when I try to access anything on the desktop computer. Is there any way around that?

What are you trying to access?

Just media files?

If so, check the media streaming options in the network + sharing centre.

If you are trying to access all files types, I would suggest setting up a fileserver or network access storage - as it's much more safer and secure.

Lastly, I would not recommend turning of your firewall. To properly tune a firewall, open the task manager -> performance -> resource monitor -> Network -> Scroll all the way down to TCP connections then listening ports. Here you can see what ports are open and being used.

The network activities are dependent on what you have installed and what services are running. It's important to note System, SVChost, Spoolsv, winint, Isass are key system process.

However, generally windows firewall settings are setup correctly for most people. It's often a case of simply re-enabling windows firewall policy by turning it off and on again.