If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Win10 pc not visible in the network
On 13/04/2018 09:50, Paul wrote:
Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke On Windows, the URI would be similar to \\192.168.1.2\Waldo to reach a SMB server on the machine with IP 192.168.1.2. Yes, Paul. When I type "\\192.168.1.xxx"in my explorer, I can see my shared folders instantly. Strange enough, when I open "Network" I can see all pc's (icons) exept mine. And all this since I moved to W10. If doing this from a Linux LiveCD, it might be similar to smb://192.168.1.2/Waldo with the usual password prompts or whatever. Using the IP address method, gets around NetBIOS problems. Paul OK, but I have Netbios enabled! Fokke |
Ads |
#17
|
|||
|
|||
Win10 pc not visible in the network
Fokke Nauta wrote:
On 13/04/2018 09:50, Paul wrote: Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke On Windows, the URI would be similar to \\192.168.1.2\Waldo to reach a SMB server on the machine with IP 192.168.1.2. Yes, Paul. When I type "\\192.168.1.xxx"in my explorer, I can see my shared folders instantly. Strange enough, when I open "Network" I can see all pc's (icons) exept mine. And all this since I moved to W10. If doing this from a Linux LiveCD, it might be similar to smb://192.168.1.2/Waldo with the usual password prompts or whatever. Using the IP address method, gets around NetBIOS problems. Paul OK, but I have Netbios enabled! Fokke Are you using HomeGroup at the same time ? Paul |
#18
|
|||
|
|||
Win10 pc not visible in the network
On 13/04/2018 10:48, Paul wrote:
Fokke Nauta wrote: On 13/04/2018 09:50, Paul wrote: Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke On Windows, the URI would be similar to \\192.168.1.2\Waldo to reach a SMB server on the machine with IP 192.168.1.2. Yes, Paul. When I type "\\192.168.1.xxx"in my explorer, I can see my shared folders instantly. Strange enough, when I open "Network" I can see all pc's (icons) exept mine. And all this since I moved to W10. If doing this from a Linux LiveCD, it might be similar to smb://192.168.1.2/Waldo with the usual password prompts or whatever. Using the IP address method, gets around NetBIOS problems. Paul OK, but I have Netbios enabled! Fokke Are you using HomeGroup at the same time ? Paul No, I never used Homegroup. Didn't initiate it. Should I disable it somehow? BTW, I enabled Netbios on all other pc's (W7 Pro) and now I can see the icon of my pc in their network area's. But still no shared folders, although I have shared several folders on my pc. Fokke |
#19
|
|||
|
|||
Win10 pc not visible in the network
On 4/13/2018 3:33 AM, Fokke Nauta wrote:
On 11/04/2018 23:58, Keith Nuttle wrote: On 4/11/2018 4:35 PM, Paul wrote: Fokke Nauta wrote: On 11/04/2018 17:56, Keith Nuttle wrote: On 4/11/2018 10:41 AM, Wolf K wrote: On 2018-04-11 10:11, Fokke Nauta wrote: Hi all, Have a small LAN at home. Mixed W7 and W10 pc's. When my pc was Win7, it and its shares were clearly viible in the network. Moved over to W10 (fresh install, W10 pro 64b) and now the others can't see my pc. I have quite a lot of IT experience, but I can't find a reason why my pc is now invisible. Thought I got all the settings right. Is there a hidden "something" in W10 that hides my pc? Any ideas? Thanks, Fokke FWIW, the last time I had this problem (2xW8.1 one fresh install and 1xW7 machines) I destroyed the Homegoup, and set up a new one. Best, Destroy the Homegroup, and set your network up by going to each computer and sharing the desired folders. I never used a home group, and sharing folders is what I always did. And mapping shared folders. Â*Then in the File Explorer on all of the other computers that you wish to see the shared folder, map that folder to drive letter. That's what I used to do. But since W10 my pc is not visible on other pc's when looking on the network, let alone my shares. I gave up on the home group years ago, and went to the mapped drives. While I am not sure how they are changing it I have read the MS is abandoning the Homegroup function As I said, never used home groups, always shares and mapped drives. Fokke When every thing else fails you must take ownership of the folders you are sharing.Â* This is an involved process, that starts in Advanced Sharing in the Folder properties, you then have to go into Security, Permissions, and make sure that same user name is in that window for the user that shared the folder,Â* As I do it this is trial and error. Make sure that user has the appropriate permission. Make sure the appropriate user is shown as Owner at the top of the Advance Windows. and the user have proper access. This is an involved process, that when I do it, it gets done with a lot of websearches and trial and error.Â* I am not going to attempt to give you a tutorial.Â*Â*Â* I do know once you get all of this correct you will be able to access the shared folders through the LAN I don't think taking ownership is the issue. I can't even see the icon of my pc in the network. Fokke That is why you have to have the owner ship of the folder in Security Advance. When I finally found this and made the changes in the Ownership and permissions I finally got the icon and it appeared. I used the settings in a computer that worked, to set the parameters in the computer that did not. -- 2018: The year we learn to play the great game of Euchre |
#20
|
|||
|
|||
Win10 pc not visible in the network
Fokke Nauta wrote:
On 13/04/2018 10:48, Paul wrote: Fokke Nauta wrote: On 13/04/2018 09:50, Paul wrote: Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke On Windows, the URI would be similar to \\192.168.1.2\Waldo to reach a SMB server on the machine with IP 192.168.1.2. Yes, Paul. When I type "\\192.168.1.xxx"in my explorer, I can see my shared folders instantly. Strange enough, when I open "Network" I can see all pc's (icons) exept mine. And all this since I moved to W10. If doing this from a Linux LiveCD, it might be similar to smb://192.168.1.2/Waldo with the usual password prompts or whatever. Using the IP address method, gets around NetBIOS problems. Paul OK, but I have Netbios enabled! Fokke Are you using HomeGroup at the same time ? Paul No, I never used Homegroup. Didn't initiate it. Should I disable it somehow? BTW, I enabled Netbios on all other pc's (W7 Pro) and now I can see the icon of my pc in their network area's. But still no shared folders, although I have shared several folders on my pc. Fokke You can see an example here, of someone going the extra mile to make their NetBIOS work. https://social.technet.microsoft.com...tpronetworking * DNS Client === turning this off probably isn't a good idea... * Function Discovery Provider Host \ * Function Discovery Resource Publication \___ Try Googling on these, and see if * Peer Networking Grouping / there is another list of HG * HomeGroup Provider / specific services. These five * HomeGroup Listener / at least, might be related * SSDP Discovery * UPnP Device Host And in the end, the only thing that worked, was a Restore Point or something. There are advocates for disabling of some HomeGroup services. While two of the services have HomeGroup in the name, there are other services that HomeGroup relies on, as well as IPV6. When 1803 Upgrade arrives, Microsoft is removing HomeGroups, and I think there are fairly good odds it'll cause a whole *new* set of symptoms. I can't wait. Someone who is running 17133.1 may be able to see whether that's making a difference or not. That might be the release candidate, not sure (i.e. some content will be the same as 1803). Paul |
#21
|
|||
|
|||
Win10 pc not visible in the network
Paul wrote:
Fokke Nauta wrote: On 13/04/2018 10:48, Paul wrote: Fokke Nauta wrote: On 13/04/2018 09:50, Paul wrote: Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke On Windows, the URI would be similar to \\192.168.1.2\Waldo to reach a SMB server on the machine with IP 192.168.1.2. Yes, Paul. When I type "\\192.168.1.xxx"in my explorer, I can see my shared folders instantly. Strange enough, when I open "Network" I can see all pc's (icons) exept mine. And all this since I moved to W10. If doing this from a Linux LiveCD, it might be similar to smb://192.168.1.2/Waldo with the usual password prompts or whatever. Using the IP address method, gets around NetBIOS problems. Paul OK, but I have Netbios enabled! Fokke Are you using HomeGroup at the same time ? Paul No, I never used Homegroup. Didn't initiate it. Should I disable it somehow? BTW, I enabled Netbios on all other pc's (W7 Pro) and now I can see the icon of my pc in their network area's. But still no shared folders, although I have shared several folders on my pc. Fokke You can see an example here, of someone going the extra mile to make their NetBIOS work. https://social.technet.microsoft.com...tpronetworking * DNS Client === turning this off probably isn't a good idea... * Function Discovery Provider Host \ * Function Discovery Resource Publication \___ Try Googling on these, and see if * Peer Networking Grouping / there is another list of HG * HomeGroup Provider / specific services. These five * HomeGroup Listener / at least, might be related * SSDP Discovery * UPnP Device Host And in the end, the only thing that worked, was a Restore Point or something. There are advocates for disabling of some HomeGroup services. While two of the services have HomeGroup in the name, there are other services that HomeGroup relies on, as well as IPV6. When 1803 Upgrade arrives, Microsoft is removing HomeGroups, and I think there are fairly good odds it'll cause a whole *new* set of symptoms. I can't wait. Someone who is running 17133.1 may be able to see whether that's making a difference or not. That might be the release candidate, not sure (i.e. some content will be the same as 1803). Paul I don't know what this fixation with automatic is, but here's yet another list of services to check. https://www.tenforums.com/network-sh...g-network.html Paul |
#22
|
|||
|
|||
Win10 pc not visible in the network
On 11/04/2018 16:11, Fokke Nauta wrote:
Hi all, Have a small LAN at home. Mixed W7 and W10 pc's. When my pc was Win7, it and its shares were clearly viible in the network. Moved over to W10 (fresh install, W10 pro 64b) and now the others can't see my pc. I have quite a lot of IT experience, but I can't find a reason why my pc is now invisible. Thought I got all the settings right. Is there a hidden "something" in W10 that hides my pc? Any ideas? Thanks, Fokke Hi all, Good news! I got my problem solved! First of all I enabled Netbios on all PC's. Then I found out that the icon of my pc was visable in the network area of other pc's, but there were no shares. I found out that is was my Kaspersky, which blocked incoming TCP. After sorting that out, I could see and open all my shares on the other pc's. Thanks very much for all your help, hints and suggestions. Fokke |
#23
|
|||
|
|||
Win10 pc not visible in the network
On 2018-04-13 03:31, Fokke Nauta wrote:
Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke Can you \\YourPcName in explorer from another PC? Or is ping and using the \\IP-Address the only thing that works? I would try to DISABLE SMB2 and SMB3, as I suggested earlier. And make sure Computer Browser is running, I think it not only grabs list of existing machines but also advertises your own. https://support.microsoft.com/en-us/...in-windows-and Regards, -- ! _\|/_ Sylvain / ! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society oO-( )-Oo I tried sniffing Coke once, but the ice cubes froze my nose. |
#24
|
|||
|
|||
Win10 pc not visible in the network
On 14/04/2018 05:22, B00ze wrote:
On 2018-04-13 03:31, Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke Can you \\YourPcName in explorer from another PC? Or is ping and using the \\IP-Address the only thing that works? I would try to DISABLE SMB2 and SMB3, as I suggested earlier. And make sure Computer Browser is running, I think it not only grabs list of existing machines but also advertises your own. https://support.microsoft.com/en-us/...in-windows-and Regards, Thanks! Good news! I got my problem solved! First of all I enabled Netbios on all PC's. Then I found out that the icon of my pc was visable in the network area of other pc's, but there were no shares. I found out that is was my Kaspersky, which blocked incoming TCP. After sorting that out, I could see and open all my shares on the other pc's. Fokke |
#25
|
|||
|
|||
Win10 pc not visible in the network
On 2018-04-14 02:22, Fokke Nauta wrote:
On 14/04/2018 05:22, B00ze wrote: On 2018-04-13 03:31, Fokke Nauta wrote: Thanks! I enabled SMB1 and Netbios. Did note make a difference. I can ping my IP4 addres and get a reply. I can ping my pc's address and get a reply (the IP6 address). Fokke Can you \\YourPcName in explorer from another PC? Or is ping and using the \\IP-Address the only thing that works? I would try to DISABLE SMB2 and SMB3, as I suggested earlier. And make sure Computer Browser is running, I think it not only grabs list of existing machines but also advertises your own. https://support.microsoft.com/en-us/...in-windows-and Regards, Thanks! Good news! I got my problem solved! First of all I enabled Netbios on all PC's. Then I found out that the icon of my pc was visable in the network area of other pc's, but there were no shares. I found out that is was my Kaspersky, which blocked incoming TCP. After sorting that out, I could see and open all my shares on the other pc's. Fokke Well that is good news! Maybe we do NOT have to disable SMB3 lol, as that guy who was here previously had to do. I'm still using Anniversary Edition, I'm afraid of moving up, because my WD TvLive only does SMB1. Firewall Issue, lol, we should've thought of that first! Best Regards, -- ! _\|/_ Sylvain / ! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society oO-( )-Oo Ah forget the docs, just see if it blows up! |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|