LockDown32
asked on
Windows 10 Peer to Peer Access
I know. Not my idea... very odd. Sue cannot ping (by name or IP) Larry's computer but Larry can ping Sue's computer. Same story. It use to work fine but today it doesn't. I shut the firewall service off on both. No joy. Any ideas?
ASKER
Their peer to peer is set up fine. Something changed between yesterday and today. Looking for ideas...
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Turning off the firewall service does not open ports. Turning off the firewall (through the firewall GUI) does and should be tried.
ASKER
I have to ask. Throughout the years the biggest fix to connectivity has been to stop the firewall service. Turning off the firewall via the GUI has not work. Stopping the service has. EE is littered with this solution. If the firewall service is off what process is blocking ports?
No, since Vista (came out late 2006), this is no longer true. You need to disable the firewall through the GUI, not the service.
" If the firewall service is off what process is blocking ports?" - I have no idea, but I don't care, I have to say.
" If the firewall service is off what process is blocking ports?" - I have no idea, but I don't care, I have to say.
ASKER
I'll find out and let you know.....
ASKER
The netsh does about 5 resets and on the sixth one it comes back with a failed, access denied. Ideas?
"The netsh"... what did you do with netsh?
There are predefined firewall setting for ping (="ICMP echo request"), just use these.
There are predefined firewall setting for ping (="ICMP echo request"), just use these.
ASKER
John's suggestion above was to reset TCP/IP. It happened to another one today. P2P is bad enough with just 2 or 3 computers. They have 7. Then throw in Windows 10...
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Pinging was just one of the symptoms. Not the only symptom. One computer could browse the shares on the other but now visa versa. One could ping the other but not visa versa. The way the other people set up the shares was by giving "everyone" full access to the shares and not using passwords. Then the just has to browse via File Explorer and open other computers at will
Then all of a sudden the other day when this lady tried browsing another workstation it popped up for the first time and started asking for credentials. Then yesterday they couldn't scan from the copy machine to a workstation. Just basic W10 P2P issues. It doesn't appear to be Firewall related but I haven't put my finger on it yet.
Resetting the TCP/IP Stack, disabling IPV6, enabling Netbios , setting Advanced Sharing to use passwords and editing the registry to allow blank passwords seems to fix it but know one know why it started happening or which "fix" actually did the trick.
Then all of a sudden the other day when this lady tried browsing another workstation it popped up for the first time and started asking for credentials. Then yesterday they couldn't scan from the copy machine to a workstation. Just basic W10 P2P issues. It doesn't appear to be Firewall related but I haven't put my finger on it yet.
Resetting the TCP/IP Stack, disabling IPV6, enabling Netbios , setting Advanced Sharing to use passwords and editing the registry to allow blank passwords seems to fix it but know one know why it started happening or which "fix" actually did the trick.
setting Advanced Sharing to use passwords <-- This option is related to Homegroup. The machine either uses Homegroup or it uses password protected sharing. The options are mutually exclusive.
ASKER
The implication was password protected sharing. Homegroup is dangerous. Never use it. Did you see my question regarding netsh?
The netsh does about 5 resets and on the sixth one it comes back with a failed, access denied. Ideas?
That does not happen on my machines or any client machine, so I am not sure why that happened, or indeed, if it is related to making things work.
That does not happen on my machines or any client machine, so I am not sure why that happened, or indeed, if it is related to making things work.
ASKER
I hate to be the bearer of bad news but it happens on my computer and all my client's computers (Windows 10). At the least Windows 10 computers. See screen shot.....
Capture.PNG
Capture.PNG
Sorry about my confusion over "5 times". Your screen shot clarifies things. That is the way NETSH works and always has for me. It still resets the stack.
So back to the password / homegroup change as the variable that fixed things
So back to the password / homegroup change as the variable that fixed things
ASKER
Still no definitive answer on which step actually fixed things. The options was under Homegroup and "Use User Accounts and Passwords to connect to other computers" but since Homegroup wasn't being used that option is moot.
This is basically normal Windows 10 P2P issues. No rhyme or reason. No definitive fix (yet). You just try enough things and all of a sudden it starts working again.....
This is basically normal Windows 10 P2P issues. No rhyme or reason. No definitive fix (yet). You just try enough things and all of a sudden it starts working again.....
That is because more than one variable can cause issues.
ASKER
There you go. The real question is "which variable changed and caused the problem". That is what I meant above by "This is basically normal Windows 10 P2P issues. No rhyme or reason. No definitive fix (yet). You just try enough things and all of a sudden it starts working again....."
I have my two personal machines set up for peer to peer access and it works great.
Last week we were at our cottage for a week and I assisted a person here with Homegroup issues (making it work). To do that, I was in Control Panel, Homegroup and also Services.
All was well and I thought nothing more about it until Monday at a client and I could not connect to their server. Since networking was fine, the first port of call here was Advanced Sharing Settings in Network and Sharing Center. The password setting had been disabled.
I enabled Passwords, restarted and all was normal again.
Last week we were at our cottage for a week and I assisted a person here with Homegroup issues (making it work). To do that, I was in Control Panel, Homegroup and also Services.
All was well and I thought nothing more about it until Monday at a client and I could not connect to their server. Since networking was fine, the first port of call here was Advanced Sharing Settings in Network and Sharing Center. The password setting had been disabled.
I enabled Passwords, restarted and all was normal again.
ASKER
John, you keep using the phrase "I do it on mine and it works great". Well.... as a rule things do but not always. I know peer to peer works. Has for a long time and it does work great when it works. I am happy it is working great for you but the problem is that it isn't working great for this one customer. If everything worked great all the time there would be no need for EE :)
I don't use home Homegroup and neither did the IT place that initially set up this network. Something changes and as is sometimes the case with Windows there is no definitive answer. This appears to be one of those cases. All you can do it ask others what can be tried....
I don't use home Homegroup and neither did the IT place that initially set up this network. Something changes and as is sometimes the case with Windows there is no definitive answer. This appears to be one of those cases. All you can do it ask others what can be tried....
This appears to be one of those cases. All you can do it ask others what can be tried....
Yes. I keep a list of fixes in One Note for easy access if I need to troubleshoot.
Yes. I keep a list of fixes in One Note for easy access if I need to troubleshoot.
https://www.experts-exchange.com/articles/16639/Folder-sharing-on-modern-machines.html
and make the settings changes on both machines and then restart both.
Then test again.