|
| 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 |
|
#1
October 28th 18, 02:53 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
Networking problem
I have two computers on my home network, Corsair which is fairly new
running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? -- Regards, Eric Stevens 
|
| Ads |
|
#2
October 28th 18, 04:30 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
Eric Stevens wrote:
I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? The difference between Home and Pro, is Pro supports domains. In a domain, there is a central server. Authentication is against this central server, instead of against the local machine. It means there is the possibility of a consistent Eric Stevens, along with a SID to match. In a domain, all the computers have workgroup=StevensHousehold, and when set that way, they know which machines belong to the group and that those machines will be authenticated against the domain server. Run this in a command prompt on two machines you plan to network (non-domain situation). whoami /user User Name SID ==================== ============================================= corsair\eric stevens S-1-5-21-111111111-2222222222-3333333333-1001 whoami /user User Name SID ==================== ============================================= dell\eric stevens S-1-5-21-444444444-5555555555-6666666666-1000 While the account name on "loose" non-domain machines may have been set by the user to be identical, the machine uses a SID for the job. The SID is generated when the OS is installed, and the SID is random. Thus, the Corsair machine has a different bunch of "large digit groups" than the Dell machine. When you bring the Dell hard drive over to the Corsair machine, and access the Eric Stevens Downloads folder, you'll notice a green bar fly across the Explorer status bar. That's TakeOwn happening. Now, the Downloads folder will have two owners, an entry for 1000 and an entry for 1001. The foreign SID won't have a symbolic name, while the "local" Eric Stevens will be the local owner. Note that, user accounts start at 1000, the "real administrator" is 500. You are not the real administrator. You belong to the administrator group, which is a different property. The difference between the two machines could be, that the first machine used an MSA, and it required the accounting logic to temporarily use two account numbers, and the number ended up being 1001. I think you can see there is a conundrum here. It appears by all standards, the equipment is in no condition to transfer files at all. The identification methods are not set up to make it easy. A domain might have been simpler. ******* This is why the answerers in this thread, are trying to explain the process of changing the properties of the shared folder (on the serving end) so that "Everyone" has "Full Control". This allows a person, once they're nominally authenticated (they've entered a username and password that exists on the serving machine), the "Everyone" property on the folder makes the folder "open season". Now, the files will transfer. https://www.tenforums.com/network-sh...computers.html Basic network settings and radio buttons, are shown here. You've already done this part. https://www.howtogeek.com/howto/9040...s-7-and-vista/ It's theoretically possible to gimp a Win10 machine, by not turning on the SMBV1 features in "Windows Features" of "Programs and Features". This would be the case, if you also happened to disable the registry settings for SMBV2 and SMBV3. By default, we might expect to see SMBV2 and SMBV3 enabled after a new install. On SMBV1, name serving is via NetBIOS. That's how I can have Dell and Corsair machine, and the machines convert the names to 192.168.1.2 and 192.168.1.3. But I can also use numeric identifiers, if NetBIOS is not working. You use the right hand syntax, if NetBIOS is borked. You can use "ipconfig" on the machine in question, to get its current IP address. (This works well when all the computers are in the same room.) \\corsair\corsairshare \\192.168.1.3\corsairshare \\dell\dellshare \\192.168.1.2\dellshare On Linux, it might be smb://corsair/corsairshare, so there is a similarity there. Linux would accept smb://192.168.1.3/corsairshare as well. There is also a nameserving subsystem for IPV6 situations, and there are a few other services (from the HomeGroup days), that actually function in the nameserving capacity. IPV6 used to be mandatory on HomeGroups, but it may also come in handy when the only working nameserving is the modern flavor and not the NetBIOS flavor. When you set the machines up, you assigned a workgroup. On my LAN, this is workgroup=WORKGROUP, which is a more or less defacto standard that home users might use. This conflicts with the workgroup=MSHOME that HomeGroups might have used. But you can use any string you want like workgroup=StevensHousehold if you want - it just has to be used consistently on all the machine that you want sharing with one another. You can run "control" to get Control Panels running, then select the System control panel to find things like machine name and workgroup value. That's where you can make adjustments, then reboot. Rebooting is necessary to establish a new identity for the machine via NetBIOS or similar (the machine has to "register" on the LAN). With Windows itself, it doesn't go out of its way to tell you everything about the net that it might. That's why there are tools like this. http://www.unixwiz.net/tools/nbtscan.html http://www.unixwiz.net/tools/nbtscan-1.0.35.exe nbtscan 192.168.1.0/24 That will scan the 256 addresses with that netmask, and list the workgroup of each machine found. If you had some MSHOME machines and some WORKGROUP machines, it should show you that. Then you can go around and remedy the situation as you see fit. In my travels on the net, I've seen very few individuals who have the "flow chart" in their brain, to debug each and every file sharing issue successfully. I suppose doing such a thing is part of attaining a "cert", but I don't see too many discussion threads, where an answerer consistently tracks down an issue and fixes it every time. And I'm certainly not one of those people, because I've run into a few headscratching moments here with my small collection of gear. Like the people in that Tenforums thread, I know a few tricks, but I "don't have the flow chart", and don't know "what to do next". I often wonder why there isn't a multi-node "Troubleshooter" for this stuff. I know that third party companies have successfully written network maintenance software in the past, which works better than the Microsoft stuff. About all the Microsoft software does, is the two stack reset commands that some of the scripts on tenforums tutorials use. Which might not be enough to fix every problem. Especially if a user has been hacking away at their Services settings using advice from the BlackViper site. Paul
|
|
#3
October 28th 18, 05:32 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
|
|
#4
October 28th 18, 05:47 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On 10/28/2018 8:53 AM, KenW wrote:
On Sun, 28 Oct 2018 15:53:30 +1300, Eric Stevens wrote: I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? When I have had this situation I have found that I did not have the permission set correctly, nor the owner. As I remember there are two places where the sharing parameters must be set. Both are in the folder properties. The obvious is in the Sharing tab. The one that messed me up was in the Security tab Advanced. At the top of the popup page the owner shown in that position must be the one that has the rights to share the folder. (It took me some time to work it out so I am not going to try to explain what I did. You can search and find the infromation online.) -- 2018: The year we learn to play the great game of Euchre
|
|
#5
October 28th 18, 08:25 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On 28/10/2018 02:53, Eric Stevens wrote:
Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. Go to the machine where you have a problem and then right-click on the folder that needs to be shared. Then choose Properties Sharing. There is an option to make it Read/Write. First make sure you have selected "Everyone" from the drop down list. Then make Read/Write permission. Go and do this for both machines - Dell as well as Corsair. Make sure you are sharing a folder only. You don't want to share the entire machine. For example, I have two folders shared - Downloads & htdocs. htdocs is a web server I run locally on apache for testing purposes. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? Probably but I don't have any W10 Home on my machines; They are all professional or Enterprise. The enterprise machines are running on trial versions of the OS but they seem to be going on and on. There is no expiration for reasons I don't know. It could be that previous version of W10 professional was activated so enterprise got it confused although it was a clean installation.
|
|
#7
October 28th 18, 10:59 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
|
|
#8
October 28th 18, 11:15 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On Sun, 28 Oct 2018 00:30:28 -0400, Paul
wrote: Eric Stevens wrote: I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? The difference between Home and Pro, is Pro supports domains. In a domain, there is a central server. Authentication is against this central server, instead of against the local machine. It means there is the possibility of a consistent Eric Stevens, along with a SID to match. In a domain, all the computers have workgroup=StevensHousehold, and when set that way, they know which machines belong to the group and that those machines will be authenticated against the domain server. Run this in a command prompt on two machines you plan to network (non-domain situation). whoami /user User Name SID ==================== ============================================= corsair\eric stevens S-1-5-21-111111111-2222222222-3333333333-1001 whoami /user User Name SID ==================== ============================================= dell\eric stevens S-1-5-21-444444444-5555555555-6666666666-1000 This sounds like a possible cause to the problem. I have tried this command on both machines and while I get a response from each it comes and goes so quickly that it its just a barely noticable flicker with no chance of reading it at all. While the account name on "loose" non-domain machines may have been set by the user to be identical, the machine uses a SID for the job. The SID is generated when the OS is installed, and the SID is random. Thus, the Corsair machine has a different bunch of "large digit groups" than the Dell machine. When you bring the Dell hard drive over to the Corsair machine, and access the Eric Stevens Downloads folder, you'll notice a green bar fly across the Explorer status bar. That's TakeOwn happening. I always wondered what that was. Now, the Downloads folder will have two owners, an entry for 1000 and an entry for 1001. The foreign SID won't have a symbolic name, while the "local" Eric Stevens will be the local owner. Note that, user accounts start at 1000, the "real administrator" is 500. You are not the real administrator. You belong to the administrator group, which is a different property. The difference between the two machines could be, that the first machine used an MSA, and it required the accounting logic to temporarily use two account numbers, and the number ended up being 1001. I think you can see there is a conundrum here. It appears by all standards, the equipment is in no condition to transfer files at all. The identification methods are not set up to make it easy. A domain might have been simpler. ******* This is why the answerers in this thread, are trying to explain the process of changing the properties of the shared folder (on the serving end) so that "Everyone" has "Full Control". I've already done that. This allows a person, once they're nominally authenticated (they've entered a username and password that exists on the serving machine), the "Everyone" property on the folder makes the folder "open season". Now, the files will transfer. https://www.tenforums.com/network-sh...computers.html Basic network settings and radio buttons, are shown here. You've already done this part. Yep. https://www.howtogeek.com/howto/9040...s-7-and-vista/ It's theoretically possible to gimp a Win10 machine, by not turning on the SMBV1 features in "Windows Features" of "Programs and Features". This would be the case, if you also happened to disable the registry settings for SMBV2 and SMBV3. By default, we might expect to see SMBV2 and SMBV3 enabled after a new install. On SMBV1, name serving is via NetBIOS. That's how I can have Dell and Corsair machine, and the machines convert the names to 192.168.1.2 and 192.168.1.3. But I can also use numeric identifiers, if NetBIOS is not working. You use the right hand syntax, if NetBIOS is borked. You can use "ipconfig" on the machine in question, to get its current IP address. (This works well when all the computers are in the same room.) \\corsair\corsairshare \\192.168.1.3\corsairshare \\dell\dellshare \\192.168.1.2\dellshare Haven't been anywhere near this as yet. I'm not sure that I want to. On Linux, it might be smb://corsair/corsairshare, so there is a similarity there. Linux would accept smb://192.168.1.3/corsairshare as well. --- snip --- I'm not ignoring the stuff I have snipped - quite the reverse. My office has two computers and two printers all on the same ethernet network. I have a feed from the router where the fibre cable comes in. Originally this link was wifi but now it too is via ethernet. As part of the recent change I replaced my old wifi Netgear switch in the office with a Netgear GS105 switch. Shortly before this Dell was auto-updated to 1803.and a bit later I updated Corsair with the buggy 1809 update. I was not aware of any problems at the time I made these changes but I now find my old office network has vanished and the GS105 is undiscoverable and I can't set up a new network based on that. In the meantime the two computers are still communicating with each other although Corsair rejects Dell's approaches. I don't think the communication problem is related to the physical network so I am carefully skirting around the stuff I have snipped. In the meantime, why is the response to whoami so brief and what can I do about it? -- Regards, Eric Stevens
|
|
#9
October 28th 18, 11:16 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On Sun, 28 Oct 2018 13:47:07 -0400, Keith Nuttle
wrote: On 10/28/2018 8:53 AM, KenW wrote: On Sun, 28 Oct 2018 15:53:30 +1300, Eric Stevens wrote: I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? When I have had this situation I have found that I did not have the permission set correctly, nor the owner. As I remember there are two places where the sharing parameters must be set. Both are in the folder properties. The obvious is in the Sharing tab. The one that messed me up was in the Security tab Advanced. At the top of the popup page the owner shown in that position must be the one that has the rights to share the folder. (It took me some time to work it out so I am not going to try to explain what I did. You can search and find the infromation online.) I think I have done all that (?). -- Regards, Eric Stevens
|
|
#10
October 28th 18, 11:17 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On Sun, 28 Oct 2018 14:32:48 -0300, pjp
wrote: In article , says... I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? I've run across this numerous times because I forget step 2 until error message appears when setting up a new install etc. so here goes. 1 - I setup every share that includes an "Everyone" name which I add if need be. I setup the share as required, e.g. Read or Read/Write. 2 - I then go into Networking and Sharing Center and under Advanced I turn Off "Require Password" setting. That's all I've ever needed to do and I run a lot of shares across 13 pcs in this house. They all connect without issue and do Read versus Read/Write as expected. I've done all that (except buy 11 more PCs). -- Regards, Eric Stevens
|
|
#11
October 28th 18, 11:18 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
In article , Eric Stevens
wrote: As part of the recent change I replaced my old wifi Netgear switch in the office with a Netgear GS105 switch. Shortly before this Dell was auto-updated to 1803.and a bit later I updated Corsair with the buggy 1809 update. I was not aware of any problems at the time I made these changes but I now find my old office network has vanished and the GS105 is undiscoverable and I can't set up a new network based on that. the gs105 is unmanaged. there's nothing to discover. the problem is elsewhere.
|
|
#12
October 28th 18, 11:32 PM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On Sun, 28 Oct 2018 14:32:48 -0300, pjp
wrote: I've run across this numerous times because I forget step 2 until error message appears when setting up a new install etc. so here goes. 1 - I setup every share that includes an "Everyone" name which I add if need be. I setup the share as required, e.g. Read or Read/Write. 2 - I then go into Networking and Sharing Center and under Advanced I turn Off "Require Password" setting. That's all I've ever needed to do and I run a lot of shares across 13 pcs in this house. They all connect without issue and do Read versus Read/Write as expected. I do almost exactly the same, except exactly the opposite. ;-) 1. I create an account on each PC that uses my user  ass credentials. Inever log into that account on those other PCs; it's only there to enable the third step below. 2. I share one or more folders on the respective PCs. 3. Then, from my local PC, I access a remote PC by its IP address and share name*. My local PC sends the credentials of the currently logged in user, (me), they match an account on the remote PC, and dinner is served. I don't set any shared folders for 'Everyone' access. I'm opposed to that on general principles. *This sidesteps anything related to PC names, NetBIOS, and Workgroup names. All of that stuff becomes completely irrelevant. I've been doing it that way since at least the early XP days without any issues. It's possible that I started in the 98 days, but it's too far back to be sure. Summary: Step 1 above is the important one. I see a lot of people skip over it and then they end up using the Everyone permission set. Ugh.
|
|
#13
October 29th 18, 12:05 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
On 10/28/2018 7:16 PM, Eric Stevens wrote:
When I have had this situation I have found that I did not have the permission set correctly, nor the owner. As I remember there are two places where the sharing parameters must be set. Both are in the folder properties. The obvious is in the Sharing tab. The one that messed me up was in the Security tab Advanced. At the top of the popup page the owner shown in that position must be the one that has the rights to share the folder. (It took me some time to work it out so I am not going to try to explain what I did. You can search and find the infromation online.) I think I have done all that (?). Sometime the ownership while appearing correct, is wrong. I beleive you said one of your computers, did access the net, check the owner of each shared folder, and then set the other computer to the same owner. The owner on all of my computers for all of my shared folders is Administrator (computername\administrator) Make sure the permissions for the above owner is set to full contro, applies to all folders. My permissions are Allow Everyone Full Control None This folder, subfolders and files Allow System Full Control None This folder, subfolders and files Allow Administrator (computername\administrator) Full Control None This folder, subfolders and files -- 2018: The year we learn to play the great game of Euchre
|
|
#14
October 29th 18, 12:35 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
Eric Stevens wrote:
On Sun, 28 Oct 2018 00:30:28 -0400, Paul wrote: Eric Stevens wrote: I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? The difference between Home and Pro, is Pro supports domains. In a domain, there is a central server. Authentication is against this central server, instead of against the local machine. It means there is the possibility of a consistent Eric Stevens, along with a SID to match. In a domain, all the computers have workgroup=StevensHousehold, and when set that way, they know which machines belong to the group and that those machines will be authenticated against the domain server. Run this in a command prompt on two machines you plan to network (non-domain situation). whoami /user User Name SID ==================== ============================================= corsair\eric stevens S-1-5-21-111111111-2222222222-3333333333-1001 whoami /user User Name SID ==================== ============================================= dell\eric stevens S-1-5-21-444444444-5555555555-6666666666-1000 This sounds like a possible cause to the problem. I have tried this command on both machines and while I get a response from each it comes and goes so quickly that it its just a barely noticable flicker with no chance of reading it at all. While the account name on "loose" non-domain machines may have been set by the user to be identical, the machine uses a SID for the job. The SID is generated when the OS is installed, and the SID is random. Thus, the Corsair machine has a different bunch of "large digit groups" than the Dell machine. When you bring the Dell hard drive over to the Corsair machine, and access the Eric Stevens Downloads folder, you'll notice a green bar fly across the Explorer status bar. That's TakeOwn happening. I always wondered what that was. Now, the Downloads folder will have two owners, an entry for 1000 and an entry for 1001. The foreign SID won't have a symbolic name, while the "local" Eric Stevens will be the local owner. Note that, user accounts start at 1000, the "real administrator" is 500. You are not the real administrator. You belong to the administrator group, which is a different property. The difference between the two machines could be, that the first machine used an MSA, and it required the accounting logic to temporarily use two account numbers, and the number ended up being 1001. I think you can see there is a conundrum here. It appears by all standards, the equipment is in no condition to transfer files at all. The identification methods are not set up to make it easy. A domain might have been simpler. ******* This is why the answerers in this thread, are trying to explain the process of changing the properties of the shared folder (on the serving end) so that "Everyone" has "Full Control". I've already done that. This allows a person, once they're nominally authenticated (they've entered a username and password that exists on the serving machine), the "Everyone" property on the folder makes the folder "open season". Now, the files will transfer. https://www.tenforums.com/network-sh...computers.html Basic network settings and radio buttons, are shown here. You've already done this part. Yep. https://www.howtogeek.com/howto/9040...s-7-and-vista/ It's theoretically possible to gimp a Win10 machine, by not turning on the SMBV1 features in "Windows Features" of "Programs and Features". This would be the case, if you also happened to disable the registry settings for SMBV2 and SMBV3. By default, we might expect to see SMBV2 and SMBV3 enabled after a new install. On SMBV1, name serving is via NetBIOS. That's how I can have Dell and Corsair machine, and the machines convert the names to 192.168.1.2 and 192.168.1.3. But I can also use numeric identifiers, if NetBIOS is not working. You use the right hand syntax, if NetBIOS is borked. You can use "ipconfig" on the machine in question, to get its current IP address. (This works well when all the computers are in the same room.) \\corsair\corsairshare \\192.168.1.3\corsairshare \\dell\dellshare \\192.168.1.2\dellshare Haven't been anywhere near this as yet. I'm not sure that I want to. On Linux, it might be smb://corsair/corsairshare, so there is a similarity there. Linux would accept smb://192.168.1.3/corsairshare as well. --- snip --- I'm not ignoring the stuff I have snipped - quite the reverse. My office has two computers and two printers all on the same ethernet network. I have a feed from the router where the fibre cable comes in. Originally this link was wifi but now it too is via ethernet. As part of the recent change I replaced my old wifi Netgear switch in the office with a Netgear GS105 switch. Shortly before this Dell was auto-updated to 1803.and a bit later I updated Corsair with the buggy 1809 update. I was not aware of any problems at the time I made these changes but I now find my old office network has vanished and the GS105 is undiscoverable and I can't set up a new network based on that. In the meantime the two computers are still communicating with each other although Corsair rejects Dell's approaches. I don't think the communication problem is related to the physical network so I am carefully skirting around the stuff I have snipped. In the meantime, why is the response to whoami so brief and what can I do about it? Right click "Start", select Powershell, when the powershell window appears, type "cmd". This converts the session into Command Prompt syntax, and is the fastest way I can get you ready. Now, type in the command whoami /user And then it should stay put. If you survey the network with nbtscan, it may notice the workgroup values are not the same. Or, you can visit each machine manually and check the System control panel for the information. Your choice. http://www.unixwiz.net/tools/nbtscan.html http://www.unixwiz.net/tools/nbtscan-1.0.35.exe nbtscan 192.168.1.0/24 You can redirect the nbtscan to a text file: cd /d C:\users\Eric Stevens\Downloads nbtscan 192.168.1.0/24 nbt_out.txt === adjust network address as appropriate for your LAN notepad nbt_out.txt You can go to the Settings wheel, as there is a setting to remove the two Powershell entries in the right-click Start menu and change them to Command Prompt and Command Prompt (Administrator). You can start Powershell and type "cmd". Or start Command Prompt and type "powershell". Which gives you the ability to use either shell, no matter which shell is in the menu. You can switch them, as desired. They stack, so typing "exit", closes your last choice, and brings you back to the previous shell. The working directory doesn't get carted around for free, so occasionally you'll need to CD to where ever you need to be. I specified your Downloads directory above, on the assumption the copy of nbtscan will be sitting there. The syntax of "cd" does not require double quotes around the path, and many many other things you do on the computer, require double quotes to help handle the "space" characters in the path. Adding space characters to filenames or paths was just a bad idea, whoever thought that one up. Hyphens or underscores are much less annoying. HTH, Paul
|
|
#15
October 29th 18, 12:40 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
Networking problem
pjp wrote:
In article , says... On Sun, 28 Oct 2018 14:32:48 -0300, pjp wrote: In article , says... I have two computers on my home network, Corsair which is fairly new running Windows 10 Home (1809 17763.55) and Dell which is running Windows 10 Pro (1803 17134.285). For a long time I have had problems networking the two computers. Dell could access Corsair and move files backwards and forwards but while Corsair could see Dell's shared folders it could not move anything either in or out of them. Not only that but password and credentials for file sharing was driving me nuts. Today I sat down and decided to tidy up the whole mess. First thing I did was turn off password file sharing. Then I went through both machines giving them identical settings for anything to do with networking and file sharing. As far as I can see the networking setup of both machines is identical. I now have the reverse of the previous situation. Corsair seems to be able to access and do anything inside the shared folders on Dell, but while Dell can see the shared folders on Corsair any attempt to access them is met by "You do not have permission etc ...". I need help. Its always possible that there is something basic that I have missed that will make all the difference. Please feel free to make suggestions to which I will respond. More to the point, I have several times read that problems of this kind are most common amongst W10 Home vs W10 Pro. Could it be that there is something going on in the way that the two different W10 machines handle Group Policies? I've run across this numerous times because I forget step 2 until error message appears when setting up a new install etc. so here goes. 1 - I setup every share that includes an "Everyone" name which I add if need be. I setup the share as required, e.g. Read or Read/Write. 2 - I then go into Networking and Sharing Center and under Advanced I turn Off "Require Password" setting. That's all I've ever needed to do and I run a lot of shares across 13 pcs in this house. They all connect without issue and do Read versus Well I only have tried Win 10 on one pc here but it was a netbook (since revereted back to Win7, no thank you 10). It acted exactly the same way as any of the others running Win7 and one even running XP. On Win10, go to Control Panels : Programs and Features : Windows Features, and turn on two of the three SMBV1 entries. That will allow Win10 to talk to WinXP. I have no problem here, with the Win10 and WinXP machines seeing and sharing with one another. Both have RAMDisks and files regularly pass from RAMdisk to RAMdisk. They're just convenient as "scratch" storage, and get cleaned out on a reboot (like, if the power goes off). My one problem was, I couldn't leave the wannacrypt patch on the WinXP machine, as that broke networking for me. But many other people didn't have a problem with that patch. It was just me. Removing the patch fixed it. I don't think that patch is even available in Windows Update for WinXP, so it's not like you can easily get the patch anyway. It takes a concerted effort to find it. Paul
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
