 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : W10: Fighting F-ing W10 networking....again....
| Author | Message | ||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
New machine for a chum who has a Puppy Linux server sitting at 192.168.1.200 Every other machine on his network can see the server, including his Mint machine. The other Windoze machines are Win7 and Win8 - both of those can see and talk to the Linux server just fine. W10 flatly REFUSES to talk to this box. I can ping the server IP address from the W10 box and get a normal reply, so it IS accessible, just Windoze won't allow it. File and print sharing is on. Network discovery is on. IPv4 is enabled. IPv6 is DISABLED to prevent it trying to screw with things. IP address used as part of the MAP NETWORK DRIVE syntax, eg: \\192.168.1.200\NAS\SHARES\sda1 At this stage, I have not enabled SAMBA v1, as I should not need it, as the Linux box is running SAMBA2. I might try enabling SMB1 in W10 settings tomorrow if anyone would think that is a good idea, but I don't see the point as the server does not use SMB1, and SMB2 is normally happy enough to co-operate with Windoze and vise-versa. W10 just keeps saying the path cannot be found - no matter what I try. The path and IP address ARE correct - I copied it from the Win8 box mapped drive to make sure I had everything 100% correct and no typo. I tried re-enabling IPv6 just to see if that helped, but it didn't, so I disabled it again. NORMALLY, you can get difficult W10 boxes to see Linux servers by using the IP address in the path as above, but not with this build. Latest W10 with all updates applied. That might be part of the bloody problem. Would not put it past the bastards to make it difficult to see NON Windows Server machines as part of one of MS's many 'Updates'. Anyone got any other hints OTHER then throwing a claw-hammer at the f-ing thing? Smoke makes things work. When the smoke gets out, it stops! |
||||
CaptainBoing Guru  Joined: 07/09/2016 Location: United KingdomPosts: 2171 |
I would have gone straight to SMB V1. for all it's ills, (not really an issue on a properly secured private network) it is pretty bombproof go into add/remove windows components and you'll find it there. Edited 2022-04-23 17:32 by CaptainBoing |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
OK, I will try enabling that and let you know what happens. Might be a few days till I can get back to my chums house. Smoke makes things work. When the smoke gets out, it stops! |
||||
phil99 Guru Joined: 11/02/2018 Location: AustraliaPosts: 2832 |
It is not just other OSs W10 won't talk to, older versions of Windows are ignored too. Had all the computers at the local fire station connected and working fine until a W10 update messed it all up. |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
I WOULD have installed W8 Pro for my chum - which connects fine to the server - but the new setup using new hardware does not support anything older then W10, so my hand was forced. My chum WANTED Win8, but as the board does not support it..... W10 on the whole, is stable and useful enough, but the networking is a total female sexual organ. Smoke makes things work. When the smoke gets out, it stops! |
||||
Chopperp Guru Joined: 03/01/2018 Location: AustraliaPosts: 1106 |
When my W10 PC's fail to connect to my server HDD attached to my broadband modem, the only way to solve the problem is with a reboot of the W10 PC. ChopperP |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2466 |
trying to use windows 10 causes me to have chest pains, so i now avoid it like the plague. had the misfortune to have to try and set up an amazon fire stick TV recently, and it caused similar issues - 40 hours later and it was finally working right, then the (made of unobtainium) remote control packed up  cheers, rob :-) |
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 8298 |
Puppy is an interesting choice to use as a server. It's certainly not intended to do that. :) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
No, it isn't, but it is very simple to setup and has a GUI for easy configuration. There are so many different Linux-based NAS distros you can choose from though. I like Puppy, cos it has the "SAMBA simple management" app. You just set a couple of things there, use the console to set a logon and SAMBA password, and away it goes. Been running a couple of Puppy servers here at my place for several years now, and they never give any issues. It's only f-ing W10 that gives me trouble these days, and 99% of the time, it is f-ing network issues. Issues that you simply don't see on older Windozes or Linux machines. Those other machines, even older Windoze ones like 7 and 8, the NAS shows up in Network Neighborhood, so click and follow your nose to map to a drive letter - done. Linux is pretty much the same. W10 on the other hand.... One would think that by ensuring that you have print and file sharing enabled, and also network discovery is turned on, that W10 would ALSO be able to see the NAS, but noooooooo...... My go-to solution for W10 when it refused to see the NAS in network neighborhood was always to just use the IP address as part of the path, and away you go, but it would seem that during various updates, MS has taken it upon themselves to seal up that method of access also. I have no doubt, if you were running Windows Server(and paying through the nose for a license for that), then W10 would probably see that OK. Windoze seems to have major issues talking to a non-MS based server, so anything built on Linux in other words, becomes a major pain in the arse to get to work. But only on W10. I have not played much with W11, so I don't know if its networking is any better or worse the W10. Does anyone here use W11 and networking? If so, can you comment on how good or bad it is compared to the nightmare that is W10 in that department? I also need to check and see if this W10 has the workgroup set as 'Workgroup' as I was never asked to specify that, but that is usually the default setting. I guess if that was different for whatever reason, that would mean it would not talk to or allow you to see all the other machines that ARE on that default workgroup. Smoke makes things work. When the smoke gets out, it stops! |
||||
| morgs67 Regular Member  Joined: 10/07/2019 Location: AustraliaPosts: 78 |
From another forum - It turns out this that this Samba mounting problem appears on some Windows 10 machines, but not others - Windows ...... SIGH. The solution is simply to specifically include the login credentials for the T4(video recorder) [or any other Samba mount giving you problems, NAS etc] into the Windows Credential Manager. Problem solved - I can now access the T4 Samba mount from my desktop ( windows 10) . Posted in case this this can help any other poor souls lost in the mysteries of windows networking - The network error from windows, that I had posted earlier, really gives you no indication that this is a simple credentials issue. - The SAMBA mount password also needs to be a win10 complex password. win10 wants all networked deviced to have a name and password that it recognises. Hope this helps. |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
Thanks - never considered the credential manager, I will check that out when I am next at my chums house(probably this weekend). I most certainly DO put a tick in the box "Remember my credentials" during the initial connecting attempt, but if you can't even get W10 to bring up the logon window cos it just complains the path cannot be found, then I don't know if CM will help.(cos you only do that AFTER you have successfully connected) I'm also going to research this a bit more now I have something to look up. Thanks for the post.  Edited 2022-04-26 17:19 by Grogster Smoke makes things work. When the smoke gets out, it stops! |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
