I am developing an UWP Application that should be able to accept incomming TCP connections.
I have given it the following capabilities in the package manifest:
Internet (Client)
Internet (Client/Server)
Private Networks (Client/Server)
I am using the StreamSocketListener from Windows.Networking.Sockets
Connections from other devices are established just fine.
Hovever: I can not connect from my own device over the loopback interface
As per this document from Microsoft, UWP does indeed restrict connections over the loopback interface, but:
Apps installed and run in Visual Studio will automatically be registered as being exempt from the loopback restrictions.
This is the scenario I'm in. And checking the Debug section in the application properties reveals that the Allow local network loopback is checked.
I checked the loopback excemptions on the system via
CheckNetIsolation.exe LoopbackExempt -s
My apps SID does appear in the list.
A comment under this SO answer suggested clearing the list and adding each entry manually. This did not resolve the problem.
Other things I have attempted:
Changing the release version of the App (Did not help)
Uninstalling and redeploying the App (Didi not help)
Setting up a fresh project. (Did not help)
Rebooting the system. (Did not help)
Using my LAN IP Address instead of the Loopback Address (Did not help)
Bashing my head against the wall (Did not help)
So the final question:
How can I enable loopback connections to a UWP app despite doing every step nescessary
Has anybody further experience with this? Is there some hidden trick I need to perform so I can connect from the local device?
If you have more than 682 records CheckNetIsolation.exe LoopbackExempt -s none of your app will be exempted. I don't know why. Try to delete temp apps with PowerShell:
Get-AppxPackage *app.a* | Remove-AppxPackage
This helped me a lot.
I had also come across a similar situation, I had resolved this using Fiddler which comes with a tool WinConfig in its menubar to restrict LoopbackExempt.
Related
Good day to all,
I am trying to create my website locally, and perhaps access the website through my phone from the localhost. Forgive me I am just a beginner.
So I used ipconfig -all to find my IPV4 address and it was e.g
192.168.1.102
And on the ASP.net webapplication I ran, the address was:
https://localhost:44337
Hence, I was trying to access this Web Application of mine created on my PC, to be accessed on my phone. On my phone, I entered the address:
192.168.1.102:44337
I went into my firewall setting to add a new rule for inbound connection to allow all ports to be connected as well. But it still don't work. Both my PC and phone is connected to the same wifi.
Does anyone know the fix? Thank you in advance.
You might have to configure an IIS server. This tool comes default in Windows (professional?), and there's lots of good resources on how to do this, all of which do a better job of explaining the process than I could do.
Essentially, you will need to:
Publish your site (Done through visual studio or cli)
Enable and configure your IIS
Create a new website in the IIS manager and point it towards the output of your web app publish
After opening the neccessary firewall ports, check to see in which IP address your web application is running. I am assuming you are using some sort of HTTP webserver software like IIS(windows) or Apache(Linux). In IIS to do that you must go to your site bindings and where it says "IP Address", select "All Unassigned" (NOT localhost or 127.0.0.1)so that the web application runs in all network adapters and IP addresses.
See full IIS documentation here: https://learn.microsoft.com/en-us/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8
Follow the guide: https://medium.com/#manujsdeveloper/debug-a-website-local-or-remote-hosted-on-an-android-mobile-device-ff2c43527be1
You will need to set your phone in developer mode and get the OEM USB driver specific for your phone. and get a ADB running on your computer
I suggest supplement your knowledge with with links below, as some things are left out in the above guide and vice versa:
https://developer.android.com/studio/command-line/adb
https://developers.google.com/web/tools/chrome-devtools/remote-debugging
I'm experiencing a strange issue with Microsoft Edge not loading a local Craft CMS website hosted inside a vagrant virtual machine. Any attempt to load the locally configured host name or IP, returns the "Hmm, we can't reach this page." error.
I have a line in my hosts file:
192.168.10.12 test.craft.dev
I've read various resources about Microsoft Edge not properly handling the hosts file properly, however not even the IPv4 address works either. I've tried several of the recommendations related to Internet Options tweaks but nothing works, it does seem however the hosts file is not the issue.
The network configuration uses NAT and sets an IP in the range of 192.168.10.x (defined by Homestead.yaml, if I assign a public_network and get an IP with my LAN network DHCP range, Edge can access this IP, but it doesn't explain why all other browsers work and Edge doesn't without it.
It's worth mentioning that the local Craft hostname will load fine in every other browser (including IE). Does Microsoft Edge have specific issues with loading local websites inside VirtualBox due to some network level issue?
Install and run fiddler. It will do everything automatically.
Edge browser seems to pay attention to the interface you are using to access your sites. My guess is that you are using Vagrant to launch a Virtualbox VM. My answer below assumes that you are accessing via a Virtualbox host-only network, or some other network interface that has an NdisDeviceType of 1.
What didn't work
None of the following worked for me:
Using about:flags and confirming that "allow localhost loopback" was on
Control panel, Network and Internet, Internet Options, Security and adding my site explicitly to Trusted Sites or Local Internet.
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"
My environment
In my case, I have VirtualBox 5.2.18 running on Windows 10 build 1803 "Spring Creators Update". Using Edge 42.17134.1.0. I have a host-only network for my VM guests. e.g. 192.168.7.0/24. I couldn't access addresses from my Edge on the VM host such as http://192.168.7.0. This site was hosted by a web server running in my VM guest. Note that this address worked just fine in Google Chrome, Internet Explorer 11 etc.
What worked
The solution is as follows:
Find the interface number for the host only network. I ran "route print" from the Windows command line and the first number shown in the "interface list" in my case was 17.
Use regedit to change the interface type from 1 to 0. The key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e972-e325-11ce-bfc1-08002be10318}\XXXX
In my case XXXX was 0016 because my interface number was 17. I had to change *NdisDeviceType from 0 to 1. The * in that key name is a literal asterisk. I had to reboot for the changes to take effect.
The answer was gleaned from a post by "Jani L" dated Oct 3, 2017, on the first URL referenced below, but it didn't give a clue as to how to determine the interface number. The second reference below was the thread on which I originally posted this solution.
References:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10142843/
https://social.technet.microsoft.com/Forums/en-US/0face535-3c7a-4658-be34-6c376322ca34/microsoft-edge-cant-open-local-domains
https://www.virtualbox.org/ticket/15565
It seems you are using Laravel Homestead box. If so, you can forward one of your host ports to the 80 port of your VM. Thus, you will be able to access your web sites hosted on your VM on MS Edge.
Here is what I've done:
ports:
- send: 8000
to: 80
If you don't want to have to type yourdomain.dev:8000 you may use fiddler. Thus, you will be able to only type yourdain.dev. :D
I have been using genymotion emulator for a while now. It was working fine, but after installing Visual Studio Community on windows 10 I am getting the following
I have set the ip of the device as show
Under virtualbox>file>preferences>network I have the following
And After selecting the device settings>network I have the following
After installing Visual Studio I have the following Hyper-v adapters under network
I also uninstalled virtual box and genymotion and did a fresh install. After which I download a new device as well.
Also i tried reducing the memory of the virtual device as it was mentioned as a solution for this on the web.
I can't figure out what is the problem.
Kindly point me in the right direction
-Regards
I think, it's because you installed Windows Phone SDK and his emulators.
If you don't need Hyper-V, disable it and all will work again.
A link to disable hyper-v : http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/how-do-i-uninstall-hyper-v/7d268911-47cd-4c52-bfe5-ea41e58067ab?auth=1
The responsible thing that is assigning dynamic IPs for you is called DHCP server so you have to enable it to resolve this issue.
Try the following:
Solution1 :-
Open VirtualBox's Preferences and under Network section, check the adapter named "vboxnet0" in "Host-Only Networks", double click on it and make sure to apply the following configuration there.
6- Double click on that name and apple the following configuration
Adapter Tab:
IPv4 Adapter: 192.168.65.1
IPV4 Network Mask: 255.255.255.0
DHCP Server Tab:
Check "Enable Server"
HINT: THIS RESOLVES YOUR PROBLEM, BUT OTHERS IS REQUIRED TO AVOID OTHER PROBLEMS
Server Address: 192.168.65.100
Server Mask: 255.255.255.0
Lower Address Bound: 192.168.65.101
Higher Address Bound: 192.168.65.255
Note: make sure you don't have any other adapter with the same configuration that might cause conflicts . revise all of adapters in that section, "Host-Only Networks" I mean, and delete the same ones there.
you can check out these tutorial also genymotionissue.
Solution2 :-
Reduce the memory below 50% of the total memory. And now it will works.Here i had found one more solution to your problem http://androidcodex.net/unable-to-start-the-virtual-device-genymotion/
Deployment failed: 1
Error: Cannot connect: Connection to https://192.168.79.131 refused. Please check IP address settings for the target. You may have to reboot the target.
My app deploys fine in Air, but I can't get it to push to the simulator. Whenever it gets to the point where it tries to install the app, I get the above error. I've checked and made sure that the IP adress is correct. I've searched high and low on the internet, and nothing I've found has worked. So, if anyone has any ideas how I can install the app on the simulator please let me know. By the way, it used to work fine with Burrito, if that means anything. Thank you. :)
Have you tried ping 192.168.79.131
And checked there is no firewall rule preventing access to that IP address from your host (i.e. PC)?
Check if your PlayBook is on the same networks as your PC.
if your PlayBook is 192.168.79.131, your PC migh be 192.168.79.xxx, else you wont access it.
What you can try to do is change your network settings of your vmware to use a bridged network instead of NAT.
Shutdown the simulator and then locate the settings option. Under network settings select bridged. Resart the simulator. refer the below link
http://supportforums.blackberry.com/t5/Native-Development/Deployment-setup-wizard-issue/m-p/1388315#M173
I am trying out a conferencing application (BigBlueButton).
For this I created an Ubuntu virtual machine that functions as the application server. On this machine I can test the application by navigating to the app url (for example http://10.0.2.15).
I also created a second virtual machine that should function as a client. On this machine I want to be able to navigate to the server as well, but that doesn't seem to be working. If I try to navigate from the client to the server by using the app-url I get nothing, followed by a timeout.
To establish a network between the two machines I tried the following solutions:
Create a second network adapter on each virtual machine and attach to "Host-only Adapter" with name "vboxnet0"
Create a second adapter on each machine and attach to "Internal network" named "intnet".
I thought that either of above options would be a good solutions, but none of them works.
Can anyone help me out here?
FYI I am using MacOS X as host system.
EDIT:
I created my second machine by cloning the first one (using the clone utility). Maybe this causes both machines to be identical which makes them indistinguishable on a network. Would this cause a problem? (As a desktop developer I'm a bit of a noob when it comes to I.T.)
I just got this to work. What I did was the internal network with the tasteful name on both VMs, but THEN I went to Advanced and set the Promiscuous Mode to "Allow All". I connect just fine now. Try it!
OK, just looked at the dates and it was last updated 2009, but for anyone looking for the answer, here you go!
IF you cloned the machine and didn't change the ip, they will never connect...
Also - make sure there is something listening on the url that you're trying to reach.
each machine should have a different ip
(but on the same network of-course)
Set the interfaces you created to internal networking. Choose a tasteful and interesting name, like "mynet". Use that name as the network name for both of the virtual machines and they will automatically be able to talk to each other over those interfaces.
Sorry, I see you already did that. In this case just give those two machines static IP addresses on the interfaces of "internal networking" type. Like, 192.168.0.2 and 192.168.0.3.
Also, once you've changed the IPs make sure the server is listening on the right interface.
I realize this is long overdue... But I just got mine set up and am able to ping each virtual machine from one another.
Assuming you're running boot2docker like I am, simply right-click the boot2docker VM in VirtualBox and click clone. In the box that pops up, be sure to check the box that says "Reinitialize the MAC address of all network cards" so that the two virtual machines don't have the same MAC address.
That's it, seems to be working for me. I can ping, scan (via nmap) and even SSH into the virtual machines from one another or from my host machine.