| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 147646 | 2019-02-17 04:04:00 | computer is inaccessible | Tony (4941) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1458376 | 2019-02-17 04:04:00 | I have just reset my old laptop (why? - don't ask). It is running fully updated Win10. I have 4 pcs on the networks, and the reset laptop can see all of them bar one, and they can all see it, bar the same one. So I have the situation where if I try to access the two pcs from each other I get the "xxx is not accessible" message, and some stuff possible permission problems. I have file and printer sharing turned on, and as I say, there is no problem with any of the other PCs. The only thing that is different is that the "other" PC is running Windows Home Server, not Win10. Any ideas? |
Tony (4941) | ||
| 1458377 | 2019-02-17 07:40:00 | If I read and understand the post correctly --you have to remember that WHS is NOT a standard OS like Windows 10. Its SERVER 2003 with more user friendly interface, designed for people who don't have knowledge of how servers work or their requirements, but the under laying OS still works as a full server Also make sure they are all on the same Workgroup. By default W10 uses "Workgroup" With a real server you are not meant to have blank passwords or rouge users. WHS was meant to be used with the connector software. What you can try is on the WHS, open regedit - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa to change limitblankpassworduse to "0" instead of "1" While you should still be able to access WHS without a dedicated / connected account you HAVE too use one that does exist. Sorry If I got your problem wrong, but the way its written is a little confusing. ?? |
wainuitech (129) | ||
| 1458378 | 2019-02-17 07:50:00 | If I read and understand the post correctly --you have to remember that WHS is NOT a standard OS like Windows 10 . Its SERVER 2003 with more user friendly interface, designed for people who don't have knowledge of how servers work or their requirements, but the under laying OS still works as a full server Also make sure they are all on the same Workgroup . By default W10 uses "Workgroup" With a real server you are not meant to have blank passwords or rouge users . WHS was meant to be used with the connector software . What you can try is on the WHS, open regedit - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa to change limitblankpassworduse to "0" instead of "1" While you should still be able to access WHS without a dedicated / connected account you HAVE too use one that does exist . Sorry If I got your problem wrong, but the way its written is a little confusing . ?? Confusing - moi? I'll check out what you suggest . They are definitely in the same workgroup - as I say, the server PC plays nicely with the other PCs on the network, and the other PCs are OK with the laptop - it is only the laptop and server PCs that have a problem . |
Tony (4941) | ||
| 1458379 | 2019-02-17 08:36:00 | Confusing - moi? I'll check out what you suggest. They are definitely in the same workgroup - as I say, the server PC plays nicely with the other PCs on the network, and the other PCs are OK with the laptop - it is only the laptop and server PCs that have a problem. Does the Server have a login (user name and password) for the laptop ? Also on the W10, make sure SMb1 & 2 are enabled, WHS wont know the new versions on W10. www.windowscentral.com WHS used SMb1 ( remember its very old networking setup / requirements) |
wainuitech (129) | ||
| 1458380 | 2019-02-17 09:07:00 | Also on the W10, make sure SMb1 & 2 are enabled...Bingo! That was it. As soon as I read your post I remembered it was an issue from way back. It all seems OK now. Thanks. This seems like a great example of pressf1 at its best - quick help from a knowledgeable member with no trolling (though the night is still young...) |
Tony (4941) | ||
| 1 | |||||