Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It allows windows explorer through the firewall to view files
What would cause it to stop working as I haven't change anything since yesterday's success?
I like that. Good idea.Honestly the best way to solve your problems is to create one entry of allow all ports/services to source ip your local subnet (example 192.168.1.0); so long as all the devices on your local lan are trusted.
Tks for the recommendation. My list is made up of what I saw several others doing on videos. So some of my rules are undoubtedly superfluous.windows file server ports should only be allowed for the local lan, unless you have a bit more of an advanced thing going on.
Yikes, you guys are way beyond me. Anyway after an hour, I tried it again and it worked without changing a thing. I'll post what I have below, pretty basic I think.
View attachment 12196
I think his issue is mostly firewall. Aside from the 2 ws discovery there’s no opening for local connections such as smb; unless that’s ticked off in rules 1 and or 2 where source ip is all (meaning internal ips and external ips)@Cyberwasp Make sure you have "Enabled Windows network discovery ..." in Control panel > File Services > [SMB] > WS-Discovery.
View attachment 12200
If you set it up that way you can eliminate rules 1,2,3,4,7. For rules 5&6 is this for your local lan; if so then it’s covered by my first rule, if it’s for your external access and need it only for your country as a source ip then add it to the my 2nd rule I listed.
But what about shared Drive or Calendar links? Wouldn't the recipient of a shared link outside of my LAN need access? In this case, Some services should have the Source IP set to "All" or "USA"
Hmmmm... Good to know.I found out when you disable the vpn from the package it removes the rule from the fw.
Hmmmm... Good to know.
@Cyberwasp If I am following @Gerard correctly, you should add a #1 rule that looks something like this...
View attachment 12202
Instead of using 192.168.1.1, you should use yours LAN Gateway IP. This rule will allow your LAN devices to access your NAS including your LAN PC for an SMB connection.
We use essential cookies to make this site work, and optional cookies to enhance your experience.