File Sharing
-
Update I Went into computer management>shared folders> shares and created a share,
Still same error. -
From what I have seen this is typically caused by windows firewall corruption
-
@murpheous said in File Sharing:
From what I have seen this is typically caused by windows firewall corruption
even though firewall is shut off?
-
@wrcombs I missed that part. My apologies.
-
@murpheous said in File Sharing:
@wrcombs I missed that part. My apologies.
That's why I was checking, No biggie.. Thanks regardless
-
You’re unable to access shared files and printers because sharing is blocked by Windows Firewall
Can’t hurt to try even though the firewall is off.
-
Quick search, looks like This Guy had the same problem, and it seems he resolved it. Either registry or malware. I'd check malware first.
-
@fiyafly said in File Sharing:
Quick search, looks like This Guy had the same problem, and it seems he resolved it. Either registry or malware. I'd check malware first.
I found that page as well, But only did phase 2 to check.
-
@wrcombs said in File Sharing:
@fiyafly said in File Sharing:
Quick search, looks like This Guy had the same problem, and it seems he resolved it. Either registry or malware. I'd check malware first.
I found that page as well, But only did phase 2 to check.
Maybe the registry entries referenced in Phase 1 are borked?
-
@fiyafly said in File Sharing:
@wrcombs said in File Sharing:
@fiyafly said in File Sharing:
Quick search, looks like This Guy had the same problem, and it seems he resolved it. Either registry or malware. I'd check malware first.
I found that page as well, But only did phase 2 to check.
Maybe the registry entries referenced in Phase 1 are borked?
possibly
-
Windows Desktop OS only allows a very limited number of inbound access points. Maybe that's the limiter? Too many incoming?
Instead of turning the firewall off, leave it on with logging enabled and outbound pop-up enabled. Then, if there's a problem, the log indicates whether the firewall is indeed at fault.
The Windows firewall is never off. It goes into a form of limp mode that in and of itself can cause problems.
Group Policy is the best way to set up the Windows Firewall and its rules IMNSHO.
-
@phlipelder said in File Sharing:
Windows Desktop OS only allows a very limited number of inbound access points. Maybe that's the limiter? Too many incoming?
Limit is 20, and theres nothing else
Instead of turning the firewall off, leave it on with logging enabled and outbound pop-up enabled. Then, if there's a problem, the log indicates whether the firewall is indeed at fault.
The Windows firewall is never off. It goes into a form of limp mode that in and of itself can cause problems.
Group Policy is the best way to set up the Windows Firewall and its rules IMNSHO.
Something to look at as well, Thanks
-
@phlipelder said in File Sharing:
Windows Desktop OS only allows a very limited number of inbound access points. Maybe that's the limiter? Too many incoming?
Old number was 10, new number is 20, depending on the OS version. It's connections, which is often misread as "users", but a single user might use several connections at once. So depending on usage, could be more than 10 users, or fewer than.
-
@scottalanmiller said in File Sharing:
@phlipelder said in File Sharing:
Windows Desktop OS only allows a very limited number of inbound access points. Maybe that's the limiter? Too many incoming?
Old number was 10, new number is 20, depending on the OS version. It's connections, which is often misread as "users", but a single user might use several connections at once. So depending on usage, could be more than 10 users, or fewer than.
Even with the 20 connections, It was terminal trying for the share.
-
@wrcombs said in File Sharing:
@scottalanmiller said in File Sharing:
@phlipelder said in File Sharing:
Windows Desktop OS only allows a very limited number of inbound access points. Maybe that's the limiter? Too many incoming?
Old number was 10, new number is 20, depending on the OS version. It's connections, which is often misread as "users", but a single user might use several connections at once. So depending on usage, could be more than 10 users, or fewer than.
Even with the 20 connections, It was terminal trying for the share.
Terminal could try a lot of connections at once.
-
Have you tried running File Explorer elevated?
Tried to share the folder via a 'net use' command?
Tried renaming the folder and then sharing it? -
@siringo said in File Sharing:
Have you tried running File Explorer elevated?
Same error
Tried to share the folder via a 'net use' command?
No dice
Tried renaming the folder and then sharing it?
I tried sharing a different folder and Same error
-
@fiyafly said in File Sharing:
Quick search, looks like This Guy had the same problem, and it seems he resolved it. Either registry or malware. I'd check malware first.
This fixed it!
-
What Fixed this issue:
I downloaded : Mspsvc.reg
and BFE.RegAfter download : Right click and select merge
repeat with second file,
Restart PCthe advanced sharing settings were set correctly.
Shared the file and Watch the Point of sale start up as normal.
Thanks for all the help. -
@wrcombs said in File Sharing:
What Fixed this issue:
I downloaded : Mspsvc.reg
and BFE.RegAfter download : Right click and select merge
repeat with second file,
Restart PCthe advanced sharing settings were set correctly.
Shared the file and Watch the Point of sale start up as normal.
Thanks for all the help.Hell yeah. Glad we could help!
