When running appengine tests with windows10 I continually get firewall popups. Since the origin path of the file making the call changes on every test I get popups everytime.
Is there a way to eliminate the firewall popups without fully disabling the firewall.
Yes, you can disable the popups. In the Windows Firewall control panel, go to Advanced Settings, then select Windows Firewall Properties.
For each relevant firewall profile, select Customize from the Settings box. Change the "Display a notification" option to "No".
(In a domain environment, you can also do this via group policy if you need to reconfigure many machines at once.)
Related
for webdev purposes, especially in the phase where websites gets moved from one to another server it's nice to be able to keep the website as is on the old host and setup the system with the production domain on the new host. For this it's nice to change the ip resolution for my own computer for the specific domain to the new webervers ip address.
Up until now that worked by editing the hosts file on Windows 10 or to use a small external dns service like a pi-hole. However that doesn't seem to work anymore. Is there any nice plugin with which I can step into the dns resolution of firefox to provide a new ip address when a specific domain is requested?
You can turn off DNS-over-HTTPS and revert to traditional DNS lookup:
Manually enabling and disabling DNS-over-HTTPS
You can enable or disable DoH in your Firefox connection settings:
In the Menu bar at the top of the screen, click Firefox and select Preferences.
In the General panel, scroll down to Network Settings and click the Settings… button.
In the dialog box that opens, scroll down to Enable DNS over HTTPS and select "Off"
Click OK to save your changes and close the box.
I have this code in my WinJS default.html:
<x-ms-webview src="http://localhost/"></x-ms-webview>
<x-ms-webview src="http://display/"></x-ms-webview>
<x-ms-webview src="http://192.168.1.2/"></x-ms-webview>
display is defined in the hosts file:
127.0.0.1 display
and 192.168.1.2 -- the one that is successful -- is another computer on the network.
This is in my appx.manifest:
display and localhost successfully load in IE on the desktop and metro.
My OS is Windows 8.1 Enterprise. I have also completely disabled the Windows Firewall and this has had no effect.
What else can I do?
Microsoft blocks connections to the local machine except while running from the Visual Studio debugger.[1]
There is, however, a workaround tool. Quoting from this post on an MSDN blog:
Immersive applications (and IE11 on the Desktop) run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback).
[...]
I have built a GUI tool that allows you to very easily reconfigure an AppContainer to enable loopback traffic. This tool requires Windows 8 and runs on the .NET Framework v4. When launched, the utility scans your computer’s AppContainers and displays them in a list view. Each entry has a checkbox to the left of it, indicating whether the AppContainer may send loopback traffic. You can toggle these checkboxes individually, or use the buttons at the top to set all of the checkboxes at once. Click Save Changes to commit the configuration changes you’ve made, or click Refresh to reload the current configuration settings.
The aforementioned standalone tool is available from here.
I am trying to install and run my Windows Store app on a real Surface RT device. I have installed the Remote Debugger for ARM and its running, with no authentication on 4018.
Visual Studio fails to see the device, fails to connect and deploy.
In Windows on the desktop, I cannot ping and my port-query tool says 4018 is down, the host is unreachable.
What can I do? Why didn't they just use USB like Windows Phone development?
Microsoft don't tell you this, but you need to configure some firewall rules for the device to become visible on the network. Of course, you won't find anything by searching for "firewall" from the Start screen, but it can be found as a Snap-in for MMC.
You could turn the firewall off for the Private Profile, i.e. your local, private home network, since your home router already has a firewall and the one in Windows is just there to annoy people; cause family members to call and interrupt your dinner while they struggle to get things working on their budget new Windows 8 laptops (with no touch screen), or you could set the right rules manually.
However there's an easier way, turn on the oh-so-discoverable - especially on a tablet that's not even supposed to even have a desktop - "Network discovery and file sharing" by opening Windows (file) Explorer and clicking on the Network node on the left. A bar will pop up to remind you that Windows is getting in the way and that you can click it to make stuff work again; this configures the firewall for you.
Note that turning on "Network discovery..." via the option under Control Panel > Network Sharing Blah > Instantly-forgettable Name doesn't work. No one knows why.
By now you should be able to ping you device and the port is open, just in time for your battery to have gone flat.
Important Edit
Today, its not working again and pop-up doesn't appear again so I cannot try the same trick. My port query tool says the port is not open (it was the other day).
So I tried this, but its not working for me.
# Elevated Command Prompt #
netsh advfirewall firewall add rule name="RemoteDebugger" dir=in action=allow protocol=TCP port=4018
That says 'Ok.' but the port isn't open.
So I went into MMC and added the Firewall snap-in and its enabled itself again for the Private profile.
Then I noticed that it doesn't turn off. If you flip it to Off and hit Apply, it does nothing!!
There are now two inbound rules for the Remote Debugger, the one I setup and another for the executable. Still, doesn't work.
This thread:
http://answers.microsoft.com/en-us/windows/forum/windows_rt-networking/possible-windows-firewall-bug-on-surface-rt-blocks/caa8b40c-dacc-4d19-a751-7a04f8ef00e4
There's an answer stating:
Open Control Panel -> Administrative Tools -> Windows Firewall with Advanced Security.
Click "Windows Firewall Properties" in the main frame
In each of the three tabs of Domain, Private and Public Profile:
1) Note that: If you change "Firewall state", or change "Inbound connections" to "Allow" (inbound connections that do not match a rule are allowed), it is not going to work. The change is immediately lost after you click "OK" or "Apply" to close the dialog box.
2) What you need to do is: click Protected network connections: "Customize", it will show another dialog box, in which you can deselect some network connections. In this case, you can uncheck "Wireless" and leave "Bluetooth" on.
Once you finish step 3, Action Center will pop up an alert, saying Windows Firewall is off or not using recommended settings. You can ignore this alert, or turn it off in "Change Action Center settings".
Though someone on that thread confirm it had worked, it hasn't for me.
Luke
I am doing firewall related work.
I can turn ON/OFF windows firewall programatically using COM interface but I want to disable turn ON/OFF options.
Is there any COM interface, Windows API present for that?
You can Turn off windows firewall through command line.Just paste this command in your command prompt.
netsh advfirewall set currentprofile state off
This behavior is triggered by the presence of Group Policy for the firewall, specifically the Windows Firewall: Protect all Network connections setting.
As per How to disable Windows Firewall using python, you need to enable this setting in any of the available ways outlined there.
OK, at first I thought it was a Norton 360 problem so I deleted Norton 360. The Windows firewall is no longer being controlled by it.
Windows firewall is turned off, it's a public location, printer and file sharing is turned on, discovery is on, I reloaded the default settings for the firewall, the owner is administrator which my login is set for. Didn't matter if the Windows firewall was turned on or off, I still got the error message above.
I used to have D shared but took it off. Now when I try to create the share I get the error message above.
I have another Win 7 Pro computer with the same settings as above and I can share everything just fine.
Any ideas on how I can fix this would be greatly appreciated.
I found something nice that fixed my problem...
See solution on: Firewall and sharing folders
I did what he recommend:
export firewall polices from a Windows 7 computer that does not have this problem. (Option on the right most panel of the 3 panel screen for Windows Firewall - advanced)
Copy the .wfw file you exported to your bad firewall computer.
Use the "import Policy" option in Windows Firewall to replace the firewall policy on the bad computer.
It fixed my issue. Firewall is working - so are home groups.