Coding Thread, Programmatically enable/disable a network interface? in Coding and Web Development; I am trying to write in a 'self fixer' to a program to fix an issue with wireless connectivity over ...
29th January 2010, 10:44 AM #1
Programmatically enable/disable a network interface?
I am trying to write in a 'self fixer' to a program to fix an issue with wireless connectivity over a long time.
Namely, it seems that over time, wireless connections always seem to drop. The fix always being disabling and re-enabling the connection. As I know what this fix is, how can I write it into the software to do it itself should it need to?
My idea was this:
Normal activity of the program fails for whatever reason. In the try/catch block, it would check to see if the device was active, if it wasn't, enable it, run a ping and based on the result of that, try again.
However, every reference to doing this I come across is like running into a big Microsoft shaped wall.
Does anybody have any ideas as to API calls within Windows XP which I can use to do a simple enable/disable of a named connection? It seems that you can do it in Vista, but the devices I'm working with are embedded systems and therefore, no Vista (not to mention they only have 256Mb RAM).
IDG Tech News
29th January 2010, 10:48 AM #2
Does disabling and re-enabling the device from the Device Manager do the same thing? If so, devcon could be the answer: Enable/disable a device from the command line - The solution
Thanks to webman from:
localzuk (29th January 2010)
29th January 2010, 10:48 AM #3
Thanks to SYNACK from:
localzuk (29th January 2010)
29th January 2010, 10:50 AM #4
It would be ideal, however, from Microsoft 'DevCon is not redistributable. It is provided for use as a debugging and development tool.'
Originally Posted by webman
Looks interesting. I'll take a peak.
Originally Posted by SYNACK
29th January 2010, 10:53 AM #5
Ah - curses!
If you can do an AutoIt script, there's some posts in the forum which might work:
Disable/Enable Local Area Connection - AutoIt Forums
29th January 2010, 10:54 AM #6
The Native WIFI API has led me to this Managed Wifi API
Which looks like it'll be perfect, should it work
29th January 2010, 04:54 PM #7
Just an update for anyone else who is interested.
I have now achieved my goal by doing the following:
1. The test method runs a ping
2. If the ping succeeds, then the connectivity returns as OK
3. If not, the software looks for a predefined wireless LAN, and joins it (this automatically drops any other wireless LAN's you may be joined to.
4. Waits a while (this is currently done via a crude thread.sleep() call but I will hopefully add a while loop with a WMI call to check it is connected.
5. Pings again.
6. If OK, continues running the program.
7. If fails, then it informs the user and exits.
This is done via the ManagedWifi API I mention in my earlier post, and the Ping method in c#
By ZeroHour in forum Windows Vista
Last Post: 7th February 2012, 07:46 PM
By the_mighty_boosh in forum Netware
Last Post: 28th January 2011, 10:34 AM
By Michael in forum Windows
Last Post: 2nd July 2008, 11:47 AM
By plexer in forum Wireless Networks
Last Post: 4th March 2008, 02:54 PM
By tarquel in forum Windows
Last Post: 7th February 2006, 02:51 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)