I have my Windows 7 and all was working fine, and a samsung duos phone. i cant connect my phone to my hostednetwork coz it says 'no internet access'
netsh wlan set hostednetwork mode=allow ssid=name key=name
netsh wlan start hostednetwork
i use this command i created virtual wi-fi successfully with "no internet access" ...
I already tried editing the services.msc
application layer gateway service - automatic
network connections - automatic
Network Location Awareness (NLA) - automatic
Plug And Play - automatic
Remote Access Auto Connection Manager - automatic
Remote Access Connection Manager - automatic
Remote Procedure Call (RPC) - automatic
Telephony - automatic
Still no internet access
can any one help me...!!!
You can find it yourself via Google easily!
You need to share a working internet connection to the Virtual Lan Adaptor Created by Adaptor to provide you internet access virtually. Additionally, if there are DNS failures, then you might as well need to configure manual IP and respective subnet.
For ease; visit this page
Hope it helps.
Related
I have installed control room and client successfully and also able to work on it. But, whenever I connect VPN, the control room disconnects automatically with the message "The requested address could not be resolved".
It seems that the control room binds with the system IP, and when connected over VPN system IP changes. As per my understanding, this could be the reason for the disconnection of Control Room over VPN.
Do you have any idea how to resolve this?
Please let me know if you have a solution for this or let me know where can I get help with this issue
yes, this is correct. and this is not an error.
Once the machine is connected to the VPN, then it is effectively on the remote network... so all local resources (including the control room) will not be reachable. most likely you are connecting to the control room using its FQDN.
so you can do one of these things:
while connecting the AA client to the control room, use its IP address instead of hostname
use split DNS on ur VPN or split tunneling
I've bought a Wireless IBeacon Receiver BLE 4.0 WI-FI Sniffer here installed Node Red on my Synology DS414j. I've been able to configure the sniffer to use my local WLAN and I can access the webpages on the sniffer. So far so good.
Now I'm trying to connect MQTT node from Node Red to the device. Maybe I'm not understanding thing correctly but I would have expected this to work.
There is a Wiki here but that does not contain a lot of information. I tried signing on the forum but the confirmation mails never arrives.
Configuration of the sniffer:
I've added my SSID, security token for my WLAN. That works.
Device mode is configured to 'Station'
MQTT is configured to the IP of the NAS port 1883. With credentials. Topic is set to '/beacons'.
Node Red node is configured to IP of device port 1883, with credentials.
Questions:
Does it work the way I think this should work. Is it possible to have the MQTT Node Red node to connect to the device or do I need something else?
The sniffer can be put into 3 modes. Station, P2P and Access Point. I've now configured it at Station. Does anyone know what this setting means?
Node Red says 'connecting' but never connects. I've also installed a MQTT Dashboard on my Samsung Phone. It says 'connection failed'. What am I doing wrong? Do I need SSL/TLS? to be activated?
By the sound of things you have not installed a MQTT broker.
MQTT is not Point to Point you need a broker that the clients all connect to.
Node-RED does NOT contain a MQTT broker (there is node to add one, but it's not really the best approach), it is just another MQTT client.
I have a very simple TCP client/server implementation using GCDAsyncSocket (7.5.0) and I'm using NSNetService for service discovery.
It's used only on a local wifi network and it works for 2 years with no problem (just to say : I have a proper use of GCDAsyncSocket).
...Until I tried using a third iOS device as access point providing the wifi network to which the client and server connect.
Same when the third iOS device connects both client and server by sharing its connection via Bluetooth.
The service discovery is OK, but once I get the ip address and port, I can't connect and get this error :
Error Domain=NSPOSIXErrorDomain Code=64 "Host is down" UserInfo={NSLocalizedDescription=Host is down, NSLocalizedFailureReason=Error in connect() function}
I tried restricting to IPv4 and IPv6 (both are provided by the service discovery), I also tried using the ipv6 git branch of the GCDAsyncSocket repository and various parameters.
My primary question is : is establishing a simple TCP connexion over a wifi or bluetooth iOS access point possible, if so how ?
My secondary question is : why does the NSNetService service discovery work and not the simple TCP connection ? I know that the protocols are not comparable but still, it confuses me.
It sounds like to me, that your problem lies in connection from the cellular network. When connected to cell network, it causes issues with ip address. Refer to this discussion from the Cocoaasyncsocket Github page.
I'm building an application that will run in a museum with a local area wifi network without internet access, for some strange reason I'm not able to fully "join" this network with an iOS device. Enabling internet access on this network solves the problem...
The network should provide only a web server and a DNS server, the access point has a DHCP server, android devices can connect to the network without problems.
When I try to join the network with the device it remains in a "spinning wheel" status, the DHCP server log on the debian server says it has assigned an address to the iOS device, and if I check for the wifi address with an application (like iSys o SBSettings) I see the WIFI DHCP assigned address.
But when my app (or safari) tries to connect to the web server the request is routed through the 3G connection and not completed.
In my app I'm using the standard "Reachability" framework from Apple to check the reachability of a provided host name through the wifi connection and I get 0 on the SCNetworkReachabilityFlags mask....
I'm quite sure the problem is due to the fact iOS (5.1 in my case) tries to check the reachability for some "standard" host in the network, before routing traffic through the WIFI connection.
Anyone knows what an iOS device do to "validate" a WIFI network? I can add hostnames or simple dummy services to the server machine if this can help me connect the device to a LOCAL-only network :)
It seems that iOS doesn't like to join networks without a gateway, also if the network is local you have to setup a correct gateway address.
Setting the gateway as the server itself did the trick and the device started to route TCP/IP over my local area wifi network.
Device is 8900 OS version 4.6.1
Getting this exception/message
The application atempted to open a connection to a location inside the firewall and outside the firewall which is not allowed by your security policy
when trying to open an http connection when firewall is on (allowed HTTP connections for the app when prompted). Exact same code works fine on other devices with firewall on.
any ideas?
The firewall in this case is actually the BES firewall - what you're encountering is known as the "split-pipe" scenario where the device is detecting that connections are being made both inside the firewall (via MDS) and outside the firewall (via Wi-Fi, Direct TCP, etc.) There are IT policies that can be enabled by the BES administrator to prevent "split-pipes" from happening. Here's a good forum post with more information:
http://supportforums.blackberry.com/t5/Java-Development/Connecting-your-BlackBerry-http-and-socket-connections-to-the/m-p/206252#M29108