Serving access to windows
by Scribtor from LinuxQuestions.org on (#52XMV)
I'm posting here since SO failed me, with 10 days running a question and not a single mad, or less mad, much less sane idea or hint or possible clue as to where to look for culprits
https://stackoverflow.com/questions/...side-localhost
This probably isn't related to Slackware, or Linux in general, but I'm out of options where else to turn for help:
https://github.com/Scribtor/ngV2
You can git clone it and try to reproduce the issue I'm facing
https://www.vpn.net/
The VPN in question, although I'm pretty sure it's got nothing to do with this.
For the last couple of weeks, I've been working on an Angular tutorial and having completed a couple of basic chapters, I wanted to share my "accomplishments" with a couple of friends over a VPN.
What happened?
When serving this app from my slackware-boot, certain two remote windows machines (win7 and win10) can't access the "website"
Everywhere else, including a couple of Android smartphones, an IPhone and another Windows machine (albeit win8) works flawlessly
BUT
When I serve the exact same app from my windows-boot (I do have to have it, unfortunately) then even those two remote Win machines (win7 and win10) can access my app.
Worth mentioning:
I tried running the come-with-slackware apache httpd webserver and that, when configured to either vpn.address.x.y or simply to 0.0.0.0 is accessible from the Win7&Win10 machines in question
(The infamous "It works" message)
My question is this:
Does Slackware/Linux have a certain behaviour when serving files over a network? Does a default-deny behaviour exist for having network-members access its filesystem?
(The Angular "app" in question does have some pre-compiled .js files that ought to be working, perhaps they are being blocked somehow?)
Please do let me know if any such properties or policies exist and how would I remedy them?
There are admittedly many variables in this equation, and because of this I'm trying to eliminate them until I resolve this issue.
https://stackoverflow.com/questions/...side-localhost
This probably isn't related to Slackware, or Linux in general, but I'm out of options where else to turn for help:
https://github.com/Scribtor/ngV2
You can git clone it and try to reproduce the issue I'm facing
https://www.vpn.net/
The VPN in question, although I'm pretty sure it's got nothing to do with this.
For the last couple of weeks, I've been working on an Angular tutorial and having completed a couple of basic chapters, I wanted to share my "accomplishments" with a couple of friends over a VPN.
What happened?
When serving this app from my slackware-boot, certain two remote windows machines (win7 and win10) can't access the "website"
Everywhere else, including a couple of Android smartphones, an IPhone and another Windows machine (albeit win8) works flawlessly
BUT
When I serve the exact same app from my windows-boot (I do have to have it, unfortunately) then even those two remote Win machines (win7 and win10) can access my app.
Worth mentioning:
I tried running the come-with-slackware apache httpd webserver and that, when configured to either vpn.address.x.y or simply to 0.0.0.0 is accessible from the Win7&Win10 machines in question
(The infamous "It works" message)
My question is this:
Does Slackware/Linux have a certain behaviour when serving files over a network? Does a default-deny behaviour exist for having network-members access its filesystem?
(The Angular "app" in question does have some pre-compiled .js files that ought to be working, perhaps they are being blocked somehow?)
Please do let me know if any such properties or policies exist and how would I remedy them?
There are admittedly many variables in this equation, and because of this I'm trying to eliminate them until I resolve this issue.