Share via

win 8.1 cannot see win 10 computer on workgroup network but the opposite works

Question

Monday, January 14, 2019 6:50 PM

I added a Win 10 computer to my WORKGROUP network which consist of Win XP computer and Win 8.1 computer. I can see the Win 8.1 computer from my Win 10 computer and access its folders. I can also see the Win XP computer and access its folders from the Win 10 computer. I can also access the Win 8.1 folders from my Win XP computer. However I do not see either computers on my Win 8.1 computer.

I tried everything, including disabling the anti virus on my Win 8.1 computer but with no success.

All replies (28)

Monday, January 14, 2019 7:09 PM | 1 vote

Hi,

I have seen this issue in couple of client station. Most of the windows upgrade sometimes mess up the Network Discovery is not working as a result of which Work group computers or Network places are missing or not showing up

Please do the following (Especially the 4 & 5)

  1. Update Network Adapter Driver
  2. Reset Winsock, etc.
  3. Check Function Discovery Resource Publication Service
  4. Ensure that SMB 1.0 is manually enabled
  5. Network Reset

Please refer

https://www.thewindowsclub.com/network-computers-not-showing-in-windows-10

Hope this helps!

Please don't forget to “mark the replies as answers” if they helped, also set "like" it’s a boost for us to keep blogging J

Click here to learn more. Visit the dedicated Community forum to share, explore and talk to experts about Microsoft Kaizala.

Monday, January 14, 2019 11:11 PM | 1 vote

  If you still have an XP machine (or Linux machines using Samba shares) you have to use the old NT-style of file sharing using SMB1 and the computer browser service. It still works. I have my network running that way with everything from Windows 10 back to NT4 and Windows 98 (the latter in virtual machines).

  The modern systems (ie Vista on) use the new network discovery method but they are backward compatible with the old system. However you get the problems that are part and parcel of that old system. You must have at least one of the PCs running the computer browser service (unless you have a Samba server on the network or in your router). Machines can be slow to appear in the browse list and can remain in the browse list for some time after they are shut down. (This happens immediately in the network discovery mode). You may also need to enable Netbios over TCP/IP on the Window 8.1 and 10 machines as well as SMB1.

Bill

Wednesday, January 16, 2019 9:42 AM

Hi,

Just checking in to see if the information provided was helpful. 
Please let us know if you would like further assistance.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, January 16, 2019 2:55 PM

I am now able to see the Win 10 from my WIN 8.1 - the problem was that the Function Discovery was not enabled on the WIN 10 computer.

AS a side note to your answer, you do not say on which machine I should do these 5 actions, so I checked on both Win 81 and Win 10 machines, (The XP connection I'll do once my Win 8.1 works with the Win 10). For example step 5 does not exist in my Win 8.1 computer.

The problem now is that I do not see the folders I shared in my Win 10 computer. When I click on the Win 10 computer from my Win 8.1 computer, under Network, I get a message that it is not accessible. I turned on sharing in my Win 10 machine under  Network and Sharing Center but still not working. Off course I added a share to my folder and checked that it says that the folder is shared.

Wednesday, January 16, 2019 4:00 PM

All my 3 computers (XP, Win 8.1 and Win 10) has the Computer Browser service running. I also have NetBios over TCP/IP running on both Win 8.1 and Win 10 machines and SMB1. On the XP machine everything is on except that there is no SMB1 (which if I understand it is built it)

on my XP I can see now the Win 10 computer and also the folders I shared and have access to them, and the same the WIN 10 sees the XP computer and can access its shared folders.

The problem is the Win 8.1 computer. It does not see the XP machine and does not see the Win 10 folders/

Friday, January 18, 2019 9:29 AM

Hi,

Go to Windows Firewall->Allow apps to communicate through Windows Firewall, please check this in firewall.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, January 18, 2019 11:41 AM

It is on in my Win 8.1 machine

Monday, January 21, 2019 7:36 AM

Hi Zvi_B,

You can see Win 10 from Win 8.1, but you can't access the share in Win 10, right?

What is the error message when you can't access the share?

Trying disable your firewall to see if it works.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, January 21, 2019 1:45 PM

Yes I can see Win 10 from Win 81. but can't access the share in Win 10.

I disabled all Window Firewall and Anti Virus but still the same.
For your info: I shared the folders in Win 10 and gave full permission to everyone (Read/Write)

The error message I get is:

\TALIA-OFFICE is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.  The specified network provider name is invalid.

Tuesday, January 22, 2019 1:53 AM

Hello Zvi_B,

Can your Win 8.1 ping Win 10 successfully?

When you use "nslookup Win 10" in CMD, will it be resolved to the correct IP address?

If that's OK, then can you access the share on Win 10 via \IPaddress?

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, January 22, 2019 9:26 AM

ping ip 192.168.2.31 works fine

I am not familiar on how to use NSLOOKUP so I typed exactly as you wrote "NSLOOKUP WIN 10" and got error messages *** Can't find server address for '10':

*** server1.ddlaw.lo can't find WIN: Server failed

I also tried on the WIN8.1 computer \192.168.2.31 in the folder name of File Explorer but it failed.

Strangely, I also tried the local computer \NAME and \ip and both failed too.

But when I did the same on the WIN10 computer the File Explorer worked fine. Only  on the WIN8.1 it failed.

Tuesday, January 22, 2019 11:05 AM

Hello Zvi_B,

Type "nslookup computer name of Win 10" in CMD on Win 8.1 to see if it will be resolved to correct IP address.

And please ensure that the following services are enabled on both Win 8.1 and Win 10:

Computer Browser; Network Connections; Network Location Awareness; Function Discovery Provider Host; Function Discovery Resource Publication; UPnP Device Host; Server; SSDP Discovery; Workstation.

If it still doesn't work, then try this:

Use the win+r keyboard combination and enter "gpedit.msc" to enter the Group Policy Editor.

In Local Group Policy Editor, go to Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options->Network security: LAN Manager authentication level->Local Security Setting.

In the drop down box, select Send LM&NTLM responses.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, January 22, 2019 11:38 AM

nslookup failed, on the win 8.1 computer, both with the Win 10 computer name and of the local win 8.1 computer

"nslookup taliah-office" and "nslookup drbarak-office"

All the services were running on WIN 8.1 and I turned on those that were not running on the WIN 10 computer but still no success.

The command gpedit.msc could not be run on the WIN 8.1

I made the change on the WIN 10 computer but still no success.

I do not think the problem is with my WIN 10 computer because on my WIN 8.1 I can not resolve even my own computer. I mentioned already that I get the same error when I type my local ip or my local computer name in the File Explorer' preceded by 2 back slashes (error code 0x0004005).

However if I type the computer name without the 2 backslashes I see my drives, and when I typed my local ip without the 2 backslashes a web page is opened to the local homepage of Wampserver

On the otherhand, typing with or without the 2 backslashes works fin on the WIN 10 computer, both with computer name (WIN 10 or WIN 8.1) or ip addresses

Wednesday, January 23, 2019 2:10 AM

Hello Zvi_B,

Is the network configuration of your Win 8.1 and Win10 machines the same? How is the IP address, gateway, and DNS configured?

If they are on the same network segment (192.168.2.x and the same netmask) and only have different IP addresses, then disable IPv6 in the NIC properties of the two machines (go to Control Panel->Network and Internet->Network and Sharing Center->Change adapter settings. Right click on the NIC, select Properties, uncheck TCP/IPv6, and click OK. Do it on both Win 8.1 and Win 10). And also do the following changes.

On the Win 8.1 machine, click the Windows button in the lower left corner, click the Search button in the upper right corner, and type Edit Group Policy in the text box to enter the Local Group Policy Editor. Then change the LAN Manager authentication level.

BTW, if you want to access a share on a machine, you must use \IPadress or \ComputerName in the search bar.Or you are able to see other machines in the network folder, then directly access the share on that machine. 

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, January 23, 2019 12:00 PM

Both Win 8.1 and Win 10 are configured the same, using WORKGROUP.

IP address and DNS server addresses are obtained automatically from a main server in the office.

When I type IPCONFIG on both machines they show to be on the same segment 192.168.2.x and the same netmask 255.255.255.0 and the same gateway 192.168.2.254

I disabled IPV6 on both machines

No success.

I could not any Edit Group Policy on the WIN 8.1 using the Search Button, as you instructed. I found a post saying that Group Policy is available only on Win 8.1 Pro and mine is not the Pro version.

Regarding "access a share" both ways you suggested are not working on the WIN 8.1 (works on Win 10).

That is what I complained before, that the \IPadress or \ComputerName is not working on the Win 8.1 even if I use my local WIN 8.1 \ipadress or \ComputerName. I think we should concentrate on this problem first.

Of course also clicking on the Win 10 machine in the Network folder is not working, and also clicking on the local Win 8.1 machine in the Network folder does not work.

Thursday, January 24, 2019 7:05 AM

Hello Zvi_B,

Please refer to this post, it does solve many people's problems.

Try it to see if it works for your issue.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, January 24, 2019 3:18 PM

Tried but no success.

Please note that in that post he was able to access \ComputerName but not \IPaddress, but I cannot access none of them.

Also, let me repeat, since I cannot do it for my local computer I think the problem is with the WIN 8.1 computer itself and nothing to do with the network.

To test it I went to the WIN 10 computer and unplugged if from the network. I then opened the Network Folder and it was empty. I entered in the Search bar the local name of the computer \TALIA-OFFICE  and \196.168.2.31 and both cases worked fine and the drives and folder of the Win 10 local computer were listed. None of these 2 ways works on the WIN 8.1 computer, whether it is plugged to the network or not.

Friday, January 25, 2019 3:32 AM

Hello Zvi_B,

Win 8 can't access Win 10, this is the previous problem. Now you can't even access Win 8's own share via \Win 8's IPaddress or \Win 8's ComputerName.

The post in the last reply helped some people solve both problems at the same time, so I think it might be useful to you.

For your second problem, please check the settings below:

Can your Win 8 access its share via \127.0.0.1 and \localhost?

Type " netstat -ano | find "445" " in CMD to check if the TCP port 445 is enabled.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, January 25, 2019 2:59 PM

I did try the suggestions in the post but with no success, as I said in my lat reply.

As per your latest post I was not able to access the Win 8 computer via \127/0/0/1 or \localhost

I run netstat and port 445 is enabled and it's status is LISTENING

I would like to add that my WIN 8.1 pc is a portable one that has alos Wifi and Bluetooth connections. I am not sure whether it matter but just to make sure.

Also, I changed the workgroup on the WIN 8.1 to MSHOME and rebooted it. It did not change anything on the WIN 8.1 pc and to my surprise also the WIN 10 pc still sees the WIN 8.1 shared folders although it belongs to WORKGROUP

Monday, January 28, 2019 8:40 AM

Hello Zvi_B,

Reproduce your problem first, then enter "Event Viewer" in the search box and click "View Event Logs" below to enter Event Viewer.

Go to Applications and Services Logs->Microsoft->Windows->SMBClient. Please upload the screenshots of the logs in these three tabs based on the time the problem is reproducing, and take care to protect your privacy.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, January 28, 2019 4:32 PM

No event was registered due to trying \localhost or \127.0.0.1

BTW: the error message that appear in the Network Error window, under See Details, is 0x80004005

Tuesday, January 29, 2019 7:13 AM

Hi Zvi_B,

Try disabling and then enabling your network adapter (or uninstalling and reinstalling your network adapter) to see if the situation has changed.

Your Win 8.1 can't access shares on Win 10, and it even can't access itself.

In both processes, it is the role of the Client. And I mean to reproduce the problem first, then go to the event viewer to find the log. The error description in the log is detailed and useful. And if there is really no log in SMBClient, is there any logs in SMBServer?

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, January 29, 2019 11:18 AM

I already tried disabling and enabling the network adapter with no change. I also uninstalled it and then let the "scan" for hardware change to install it. it failed! even after rebooting. Thus now when I open Device Manager->Network adapters the adapter is not listed, only the Realtek PCIe FE Family Controller. However when I open (right click on the network icon on the task bar) Network and Sharing Center->Change adapter settings I see the adapter listed under Ethernet and I am able to change it's settings.

May be the above problem will give us a clue as to what is the problem.

There are no events in the Event viewer, not under SMB Client or SMB Server that are created after I reproduced the problem. Please note that the error is related to the double back slash I enter in the Network folder bar. I tried entering a random number and I've got the same error as with \127.0.0.1

The only event that is from today, but 15 minutes ago, is in SMBclient->Operational as listed below:

The server does not support multichannel.

Server name: \MYCLOUDEX2ULTRA

Guidance:
The client attempted to use SMB Multichannel, but an administrator has disabled multichannel support on the server. This may also be a non-Microsoft file server that does not support multichannel or has multichannel disabled. You can enable SMB Multichannel on the server using this Windows PowerShell cmdlet: Set-SmbServerConfiguration -EnableMultiChannel:$true. This event does not apply to the multichannel settings of SMB client, which are controlled by the Set-SmbClientConfiguration Windows PowerShell cmdlet. Enabling or disabling client multichannel support does not affect server multichannel support. 

Wednesday, January 30, 2019 8:15 AM

Hi Zvi_B,

Is MYCLOUDEX2ULTRA the computer name for your Windows 8.1?

What changes have you made to this Win8.1 machine? SMB Multichannel is enabled by default.

Please use " Set-SmbServerConfiguration -EnableMultiChannel $true " and " Set-SmbClientConfiguration -EnableMultiChannel $true " in PowerShell to enable SMB Multichannel on Win8.1 machine.

And please also make sure the "Server" and "WorkStation" services on your Win 8.1 machine are enabled.

I also recommend that you install the latest patches for Windows 8 and install the latest drivers for your network adapter (please install them on the official website).

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, January 30, 2019 12:10 PM

The name of my WIN 8.1 is DRBARAK-OFFICE. I do not know which computer is  MYCLOUDEX2ULTRA

I do not know what changes I made that disabled it.

Services "Server" and "Workstation" are enabled and running.

My Windows update is set to Automatic install update. There 9 optional updates available but all other updates are installed.

I could not run the 2 Set scripts using Powershell - I've got an error access denied on the SMBServer one and  and wrong parameter EnableMultiChannel for SMBClient.

I run Update Driver Software from the adapter properties and after it run windows reported that the driver software for the adapter is up to date.

However, I also looked at the Sharing tab of the adapter properties and was told that Windows cannot display the properties of this connection, because the WMI might be corrupted. I do not know what does it mean but it maybe related.

The problem still exists - can not run \127.0.0.1 in the Network folder of File Explorer

Thursday, January 31, 2019 9:21 AM

Hi Zvi_B,

Run PowerShell as administrator and run these two commands: "Get-SmbServerConfiguration" and "Get-SmbClientConfiguration". Then check if the EnableMultiChannel column is followed by "true".

However, I also looked at the Sharing tab of the adapter properties and was told that Windows cannot display the properties of this connection, because the WMI might be corrupted. I do not know what does it mean but it maybe related.

Are you referring to the function marked in the picture below?

If so, then leave it alone, that feature is not relevant to your problem.

By the way, if conditions permit, please replace your network adapter to see if the problem persists.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, January 31, 2019 5:43 PM

Both client and server EnableMultiChannel  is True.

Yes, I was referring to that function marked.

I cannot change the adapter because I am using a portable computer by HP so it is on the motherboard.

What to do now?

Friday, February 1, 2019 9:38 AM

Hello Zvi_B,

I think the next step is to analyze the problem further by capturing the package. See if there is a problem with the SMB version negotiation or a problem with the authentication, or something else.

So I recommend that you contact Microsoft Customer Support and Services for a more in-depth investigation so that you can get a more satisfactory explanation and solution.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].