I have this one issue, which I'm hopeful you guys will help me out with...
I use a plugin we have created for IE... It detects devices over the network... Devices are the ones that we ourselves have created... Now this plugin works fine and detects devices when it is wired with the Ethernet on our Subnet in XP as well as Windows 7... It detects devices when it is connected Wirelessly over our Subnet in Windows XP... But when I connect it with my Wireless subnet over Windows 7 it stops discovering the devices... The moment I enable my LAN it again detects the devices... It's behaves very stange on this part and I can't be sure that Windows 7 is responsible for this but it had to be considered... There seems like a wireless security affecting it but there is no such proof as off now...
I'm not fully aware of the plugin code but it uses mDNSresponder service over the network...
I use Windows 7 64-bit OS and Internet Explorer 9... The tests have been made over Windows 7 32-bit and IE version 8 and 9, to give the same outcome... Windows firewall has been turned on/off as well...
I'm sorry if I've posted over a wrong thread, please forgive me for any inconsistencies... Any help is appreciated... Thanks...
EDIT-1: The plugin has been built with C++ and I could give you the code for it as well but the point is that it does not get involved here... It seems like an issue over Wireless in Windows 7... I used Wireshark to sniff the packets over the network and found out that there while running in a wired network I can see requests and responses over the MDNS protocol... But when I switch to Wireless network there is no request or response over MDNS and hence there is no query sent only over the network... Seems like when I connect with the Wireless network, something blocks the plugin from querying the network... Help me out with this if possible... Thanks so much...
Ok the issue is solved... The problem was that my program was not being able to find the IEEE 802.11 wireless network interface... Since the dawn of Vista, Windows has changed some it its architecture and my program was made years before that...
Before Vista, the network adapter type value for Ethernet and IEEE wireless was same i.e 6 and is known as MIB_IF_TYPE_ETHERNET... But now they both have been differentiated and IEEE wireless adapter gets a new value 71 named IF_TYPE_IEEE80211... In our code we had a validation to reject network adapters other than MIB_IF_TYPE_ETHERNET and so it used to work with XP, but Windows 7 had other plans... Adding another validation for IF_TYPE_IEEE80211 solved the problem.
You can check out the below link to get more clarity over this and let me know if you've any queries...
http://msdn.microsoft.com/en-us/library/windows/desktop/aa366062%28v=vs.85%29.aspx
Cheers...
Related
my PC does not frequently detect my WIFI network on the WIFI list, although it is detectable on my phone. So still suffer from this problem which does not allow me to connect to my PC.
Description of my windows version
Description of my network card
First of all, i should try to use Solve problems tool on windows. Sometimes solves problems.
If this doesnt work, check your drivers and if none of this options work, i would to replce your network card.
I am developing on an ARM Mbed board which connects to my Windows laptop over USB. I've just moved to a new Dell laptop running Win 10 [from a Dell laptop running Win 7] and I find that the laptop resets my development board every 15 minutes.
There are two things that will cause the ARM Mbed board to reset:
powering down/up the USB connection
sending "break" via the USB serial driver.
When the reset occurs there is nothing of note in the Windows event logs. I have all of the "allow Windows to power me down" boxes unticked on the USB hubs in System devices and in the Control Panel power management options.
Does anyone have any suggestions on how I (a) debug what's going on or (b) fix/workaround the problem? I've not yet tried connecting via a powered USB hub, will do that next...
I had the same issue using a FRDM-K64F running mBed and communicating over a USB COM port to a Windows 7 Dell machine. The communication would sometimes drop out. As #Rob suggested, uninstalling the Dell Support Assist Agent completely fixed the issue.
Just adding this answer as it was very difficult to find any information using google.
Another note in support of this solution for google...
I have a Dell 5480 running Windows 10, and started using from ST Nucleo boards on it. I've used the exact same boards at work, with no problems. Every 15minutes or so the board was reset.
I tried disabling the Dell Support Assist services but this did not seem to fix the problem.
Removing the programs did make the Nucleo work.
I'm manufacturing a device that connects to my computer using Bluetooth and then a desktop Java app uses the Bluetooth connection to send serial data to the device which is then displayed.
When I try to connect my device to windows 7 it successfully finds and pairs with it creating a Bluetooth link on a COM port. This link can then be used by a serial prompt (used for testing) or my Java application. It works initially however soon after windows drops the connection and the only way to reconnect is to delete the device within devices and printers and then reconnect.
This seems to be a known problem with windows bluetooth so I decieded to use a third party Bluetooth application. I downloaded and tried Toshiba's Bluetooth Stack and it was able to add a Bluetooth device and keep a stable connection which works great however this only works for Toshiba computers without getting a cracked version.
This device is commercial and can't be sold with cracked versions of software. Has anybody experienced the same problems or not in other operating systems and has any solutions of advice as that would be a tremendous help.
This is not a good idea/method to use the COM ports generated by Windows, it's not working fine and not reliable in any scenario ; you should use Bluetooth Sockets instead.
Using Toshiba or Widcomm or BleuSoleil won't help: under Win7, all dongles are now trying to use the Microsoft Stack, not their own implementation.
A few useful pieces of information: I'm running Windows 8 Professional on a custom-built rig, and I am using a 'WiFi dongle' to connect my computer to the local router. I am using a home network, not a public/work/school network.
I installed the Windows Phone SDK. Piece of strawberry cheesecake so far. Coded my first simple browser app (as detailed on the Windows Phone Dev site) and hit the Run button, expecting my app to come to life and breathe in links and breathe out websites!
But instead, I got this:
Something happened while creating a switch:
Xde couldn't find an IPv4 address for the host machine.
In this case, the emulator wouldn't run at all. And so, I did my research and found out that the solution was this:
Remove all the switches from Hyper-V Manager's "Virtual Switch Manager", and make a new Internal one called Windows Phone Emulator Internal Switch.
I did, and the error did NOT show up again but it did screw up my WiFi and Bluetooth adapters (which I had to do a system restore to solve) and now both WiFi and Bluetooth peripherals are working again.
However, I got this error instead when running the emulator again:
The Windows Phone Emulator wasn't able to connect to the Windows
Phone operating system:
The emulator couldn't determine the host IP address, which is used to
communicate with the guest virtual machine.
Some functionality may be disabled.
In this case, the emulator did run, but I couldn't find my app anywhere. I did some research again and found that the solution to this was:
Delete the Windows Phone Emulator Internal Switch from Hyper-V Manager's Virtual Switch Manager.
Now, I created the switch to solve the problem in the first place. But I did delete it, for the heck of trying everything out. And no surprise there but, it went back to the first error.
I am now stuck in this paradox and have no idea how to escape it.
Thank you in advance!
follow the following steps to solve this problem
1.go to network and sharing center
2.go to change adapter setting
3.go to v Ethernet (internal Ethernet port windows phone emulator internal switch)
4.right click it and enable it(if already enabled then disable and enable it again).
Remove any Cisco VPN's or similar connections. I have found this VPN client works as a replacement to Cisco https://www.shrew.net/
For me shrew soft version 2.1.7 was the only version that worked.
I am trying to write an application for myself to learn things and to use in my own office. What I am trying to write is:
I have two nics. First one is connected to internet and the other one is connected to network
I have enabled ICS (Internet Connection Sharing) in my own PC
Other computers (Laptops, iPads etc.) are connecting to internet using my PC
So my c works like a hotspot
I am trying to see where they are connecting to and log their IP and MAC address. If I can do this, I will also add sign-in function at future.
Actually, my LSP supports TCP, UDP and RAW protocols. It works both on x86 and x64 Windows OS (Tested on Windows 7). However, when I connect to internet through this PC using my iPad, it doesn't seem working. WSPStartup never called.
If you have any idea, I will be more than happy.
Bests,
You need to use NDIS, a library like WinPCAP would do the work.