I am trying to run netsh commands to activate a tunnelbroker tunnel in Windows 10. The first command works fine. When I attempt the second command (netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=xxxxxxx remoteaddress= 216.66.22.2) I get the error "There is no driver selected for the device information set or element."
I cannot find an answer for this, even from tunnelbroker. Does anyone have a suggestion? This is driving me up a wall.
It's not an Insider issue. Microsoft decided to step down on IPv6 transition technologies as of Redstone 4 (1803). Unfortuntely, instead of just deactivating it, they stopped providing the tunnel driver at all (nettun.inf, tunnel.sys). It's unclear at this point whether Microsoft intents to fix this or not.
Found the answer: Don't use Windows 10 insider builds for IPv6. It seems they broke IPv6 with some of the more recent builds. I started out from scratch with the current version (Fall Creators, I believe), and the commands ran without issue.
Related
I was using WSL to run ROS commands, and at a point i had to enable system to respond to broadcast icmp requests (for a multi master kind of a setup) i.e. on linux i had to make sure
cat /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
returns 0. but WSL does not contain such a file, so i was thinking of enabling it on windows. All the sources i have gone through suggest me to add a rule to firewall but my system is not responding to broadcast ping even when my system's firewall is turned off(domain, private and public have been turned off same with my buddy who is no the same network). i am using an android phone's mobile hotspot to check this.
it would be great if someone could help me on this.
thanks in advance.
I asked something similar
I don't know how to do it purely on WSL. But on windows you have to start the "TCPSVCS.EXE" process. located on System32
Searched all over the place for a fix for this or even a good way to troubleshoot it. I've read the previous SO threads that seem to cover this issue but nothing in any of them has worked in my case.
Basically, I can't get access to anything that is being served via localhost on my mac in any browser on my Android device.
This is happening despite the fact they are connected to the same WIFI network and I am using the correct network address for my mac on which localhost is running (I have checked and double checked several times). I have no idea what the problem is because it worked perfectly fine before and I haven't changed anything that I believe would interfere with localhost access.
I don't have firewall or port blocking settings on my router either.
I have also tried on several different Android devices to eliminate it being a problem specific to one particular device.
Totally stumped. Any clues or hints on how to fix this would be much appreciated!
***** UPDATE *****
I tried using python -m SimpleHTTPServer 3000and it works. The site is accessible on my Android device. So I am pretty sure it is not a network issue per se.
The site is essentially a Node app which I built using the angular-quickstart template found here. It launches lite-server when npm start is run. Hope that gives some further insight into what the problem might be.
If you open up a terminal on your mac and then run the command ifconfig it will tell you what ip address all your interfaces have. It is probably your en0 interface. That ip address should be used in your browser on your Android device.
You will have to make user that you server (web) is binding to the correct ip address as well. You could be binding to all ip addresses if possible.
I tried to install a hardware I've installed in my previous computer under Windows 7, basically an external network card with antenna, but when I try to use it, after installed it I get this bluescreen error:
BUGCODE_NDIS_DRIVER
I don't know if it's possible to fix it, any useful information?
PS: If this isn't the best Stack forum, please guide me to the right one.
There is some technical information on Windows Dev Center - Hardware on this bugcheck. Driver developers can find the cause from the bugcheck code and parameters.
I can duplicate the BUGCODE_NDIS_DRIVER blue screen on my Windows 8.1 developer box fairly easily by opening two different VPN tunnels. Luckily, I don't need both running at the same time, so my solution is "don't do that".
For example, I open SonicWALL Global VPN Client to connect to one network. Then, I open the Cisco VPN client to connect to another. The crash happens almost immediately.
If you have two active network card, deactivate one, that is all.
I am stucked within a weired problem. I have two little programs (written in C, using Win API), the one sends a multicast package, the other one receives it. Well, I tried it between two notebooks, the one running win7, the other win8, and it works as expected while running a P2P connection between them (=without switch, just the patch cable plugged into both hosts).
But when I try to connect a switch between both hosts it does not work. I also tested a hub, but that dows not work either. I tested it over wifi, but it still does not work.
The Multicast Packet works just over P2P. And THAT seems to be weired.
Firewall is off, also any other security software. Ping works in any configuration as expected.
Any tip would be highly appreciated :-)
Dirk
I've found the problem for myself - the notebook I tried to send the packets has virtualbox installed. After Disabling the virtualbox service the connection worked successfully. I still don't know exactly the reason, but this workaround helped for me.
I connected two laptops using a cross-over cable. My IP Address is 192.168.1.1 and the other IP Address is 192.168.1.16. We both are able to ping each other and the reply is perfect. There is no loss of packets.
The problem is I shared a file and the other system is not able to open my IP Address using the run command. Even I am not able to open my Shared folder by giving in the run (\\192.168.1.1). A dialogue box with the message \\192.168.1.1, The Network Path was not found opens each time we try this.
But I am able to open his shared folder by giving in run command (\\192.168.1.16). I closed all the firewall services in my system. But still my system is not able to respond. Also we are not able to use remote desktop connection.
Can anyone please help me in solving this?
Additional Details: I use Windows XP and the other machine uses Windows 7. We both are in the same work group.
Here are some steps to solve your problem:
Did you set the static IP by yourself or that come automatically?
If yes then please go and set the IP manually
Then share the file and put the permission of that file to Maximum (If you believe your partner)
Then power down the firewall or antivirus for some moments (say 10 minutes)
Now try to connect using the \192.xxx.xxx.xxx method using the Run window
If the 5th step is not working, then try disabling and reenabling the LAN card, then try the 5th step again.
Hope that solved your problem.
Remote Desktop needs to be explicitly enabled. Right click on "My computer", go to properties and look at the remote settings tab.
I advice you to use Radio Access Point to connect both windows 7 and windowsXP. I think this is best choice of troubleshoting jaringan. why?
Because I already do anything to connect both Operating System but can't solve that problem.