AirConsole Unity package error on MacOS: SocketException No such host is known - airconsole

Disclaimer: I know almost nothing about Unity\C# networking
The script located in the Unity air console package at Airconsole/scripts/editor/Extensions.cs contains the method GetLocalAddress().
This method results in a runtime error on my Mac (MacOS 10.12.1, Unity 5.5.0f3), but not on a friend's Windows machine (Win10, Unity 5.5.0f3).
The error is: SocketException: No such host is known, System.Net.Dns.GetHostByName (System.String hostName)
The line causing the error is:
foreach (IPAddress ip in Dns.GetHostEntry(Dns.GetHostName()).AddressList) {
Dns.GetHostName() returns my computer name : "MacMini", but passing it as an argument to Dns.GetHostEntry() results in the error.
To work around this while developing, I have replaced the code contained in the GetLocalAddress() method with a single line:
return UnityEngine.Network.player.ipAddress.ToString();
and the Unity project runs with the virtual controllers working correctly in my browser.
Any ideas as to what would cause this problem?

Disclaimer - I am not too confident that this will help but I was having the same problem.
It turned out that it would't work in the uni network and when I used my phone as a hot spot it worked no problem.
I think the issue lies with getting the local ip from the uni network. We ended up solving this by setting up our own local network which was connected to the net via a laptop using the same uni network. It connects fine however we are suffering some really bad lag currently.
I hope this is some sort of help.


How to make react native app communicate with local machine (ios)

I need to know ALL the things I need to do in order to allow a react native app communicate with a local server running on my mac. (I'm running react native on an ios device).
This is what I know of/have tried:
Using the actual IP address of my machine instead of localhost
Set up signing & capabilities in xcode
Make sure both the iphone and computer are on the same network
Make sure there are no firewalls up on the computer running the api
Set the info.plist to "AllowArbitraryLoads = true"
Here's my full info.plist if you want to check it
I have been trying to get this simple react native app to communicate with a bare-bones flask app on my computer for like a week now, and I'm starting to lose my mind.
Assume I'm a complete moron. If there's something that "everybody knows and isn't worth mentioning", please mention it. If I didn't list it above, then I don't know about it. I feel like I'm missing a very simple step here but I cannot for the life of me figure out what it is.
Here are the error logs (i've tried googling the Flipper errors, with little success, so if you know anything about that please share):
Here's a link to a demo project I'm using to test this:
Finally figured out the last step I was missing...
When you run the flask app, you have to run it to be hosted on rather than which are both ways of referencing your local machine, but are treated slightly differently on the network. and windows 10 error?

I'm having a very strange problem with an application in windows 10. It consists of several .exe in the same computer communicating between them with sockets using library.
The problem I have is that after installing Windows 10 in a new computer, install all windows updates and then installing that application, connection to sockets doesn't work correctly and the application fails. The strangest thing is that if you leave the computer alone for 1-2 days the applications starts working just fine. The same has happened after installing version 1803 update, it stops working and then works one or two days later.
Any idea of what can it be? Has anyone seen something similar?
It really seems to be related to the 1803 update you mentioned.
Running an application from a network share will fail when creating a socket;
Copying the very same application to a local drive/path will work just fine, without any further modification.
We are also struggling with this while connecting to an Oracle database (both ODBC and ODP.NET) and it seems the issue has recently been acknowledged:
It also seems this is a recurrent Windows bug:
Win Socket Creation fails with Error code 10022 if non super user
Sorry, no effective solution at the time (other than copying the app binaries to a local folder). I'll update this answer once we get a better solution.
OK, looking a little further I found here in SO that this might be related to a SMBv1 network share, which describes the environment we had here (the network share was disabled because of another bug we faced - thanks MSFT).
Re-enabling SMBv2 / SMBv3 on the server solved the issue.
Related post:
After Windows 10 update 1803 my program can't open a socket when running from network share

The hosted network couldn't be started

i use HUAWEI USB internet connection (3G, HSPA+)
i tried to set a new virtual Hosted network but it was useless.
I made a batch file to insert orders (programming CMD) to make a virtual hosted network, it worked for only two days, then when i tried to start the virtual hosted network ("netsh wlan start hostednetwork") it giving me an error :
The hosted network couldn't be started. A device attached to the system is not functioning.
I encountered this error as well. But restarting my computer fixed it. Its probably a stupid thing to ask but it works sometimes.

VB 6.0 Out of Memory Error

One of my VB 6.0 application throws an error "Out of memory" when loading the form in a particular system, but works fine in other machines. But other vb 6.0 application works fine in the same Machine.
Problematic Machine Details:
Windows XP, HP load runner installed
Other Machines:
Windows 2003
I tried so many ways to find the root cause but i couldn't. Please help me out to find the root cause..
Gunasekaran Sambandhan
Finally i found the solution for this issue. One specific dll (MSSTDFMT.DLL) of this project is missing in this particular machine. I have placed and registered the dll. Now it is working fine.
Gunasekaran Sambandhan
Want to add our fix since it took us days to figure out what was going on.
We were trying to get an old VB6 program to run on Windows 7, we'd gotten it to work on other PCs but this one was giving us problems. Apparently we were missing a dependency, and often this misleading error can be due to missing dependencies.
The particular dependency we were missing was FM20.DLL which we got by installing Microsoft ActiveX Control Pad (
Sometimes if the registration of one or more modules gets messed up, the message "[7] Out of Memory" may occur. Unregistering and then registering the DLL(s) will fix the problem in that case. (Just encountered this on a machine that was "scrubbed" by a network push - IT could not tell me what they scrubbed exactly.)

VS 2010 Remote debugging not working

Hey everyone, I'm having trouble configuring my remote debugging set up. I've been searching and reading for a while, but I can't figure it out. I'm running windows 7 as the pc I'm running VS on and then have windows 7 running in virtual box as the pc that is running the program I'm trying to debug. I'm trying to debug a .NET 4 project.
Both computers are not part of a domain (I'm not sure if that matters). I'm running the debug monitor on the virtual pc via a shared folder on the non-virtual pc.
When I try to connect to the remote pc in the attach to process window in VS it connects, but fails to launch, and I get an error that says
Error while trying to run project: Unable to start debugging.
The specified network name is no longer available.
Let me know if I need to say anything else about my set-up.
Thanks for the help!
I finally figured out my problem(s).
I was using the wrong PC name to connect to the host machine. I was using the Server name that you can type in the VS remote debugging monitor. I had it working when I did the server as 'Stephen#192.168...' where that was the actual ip address on my subnet
Windows didn't properly configure the firewall ports for me. I had to manually open the DCOM ports to get it connecting.
I had to clear the existing credentials for each machine once everything else was set up as is shown here
Thanks everyone for your help and pointers.