System.Network.Wireless Not Working

It seems like System.Network.Wireless doesn't work...

I have tried a few Windows Vista Sidebar gadets that use it and non of them work.

I have also tried creating my own gadet and it doesn't work either.

Has the object refrence been update but not the documentation

Has anyone else seen this issue Or am I just doing something wrong

I tried the following to have it printed out on the gadget and also saved in the Event Log and both places show that nothing is outputted. (and before it is asked, yes I do have wireless that is what I am using to write this and dont even have a hard connection)

var IPAddress = System.Network.Wireless.address;

gadgetContent.innerText = IPAddress;

System.Diagnostics.EventLog.writeEntry("IP Address: " + IPAddress, "Application");



Answer this question

System.Network.Wireless Not Working

  • Xefan

    Has anyone else seen this issue
  • Helen999888

    Do you have a physical LAN card installed If it's the 1st NIC, you'll probably get blank results.

    I believe it only returns results if the NIC is going though the Wireless API - and it has to be the primary NIC.

  • Vamsee Krishna

    I have the final release (aka RTM) of Windows Vista Ultimate from MSDN.

    I am using a laptop, which has a standard wired 10/100 built-in LAN, and a 802.11 b/g built-on WiFi.

    I am not ever seeing values reported.


  • TallMike

    I am still needing some help with this, if anyone can help out.
  • heavenlycharmus

    I think "ipconfig /all" lists them in order - but don't count me on it.

    How System.Network.Wireless works, I don't know as the documentation isn't clear. Does it only deal with the primary Wireless NIC, or primary NIC Who knows, but I'd guess it's refering to Wireless NIC's only.

    The fact you're getting null results implies it's dealing with the primary NIC - which may or may not be wireless. Through the testing I've done, this certainly seems to be true, so the name "System.Network.Wireless" is somewhat misleading.

  • Semola

    Hello,

    let me tell you that I've found a solution for this problem.

    There's a hotfix available from Microsoft to solve several problems in context of wireless networks. In my case, it resolved also the issue with the wireless network gadgets.

    The hotfix changes the behavior of interfaces: although having the same configuration as in my first post, my system shows only 1 interface now, which is indeed correct. So the wireless gadgets work again.

    For further informations, please read the following Knowledge-Base article:

    http://support.microsoft.com/kb/932063

    Best regards,

    Andreas Guther



  • trezeguet

    Hello,

    let me tell you that I contacted Oliver Scheer (Developer Evangelist @ Microsoft) and he told me that the Sidebar Development Team is aware of this problem and tries to resolve it.

    Best regards,
    Andreas G.


  • jca_john

    I have a similar situation. The only difference, however, is that I also include the SSID in my code for display, and that works just fine. Other than the SSID, no other information will display. System.Network.Wireless simply refuses to report anything other than the name of the router I'm connected to.
  • Larkin Y

    Hi,

    I had the same problem. When starting the gadget, I received the right values once and when I tried to update the values, I got an error, so nothing was outputted.

    What version of Vista do you have (Beta2, RC1, RC2, RTM, english, german, francais, ...) At first I had the Ultimate RC2, where it wasn't working at first, now I have the Business Edition and no more problems, also when there is an additional LAN-connecton. It works with the buildin card on my laptop and with the WLan-USB-device on my PC.

    The object references hasn't been updated, the documentation is up to date!


  • Emadkb

    It must be returning the results for the LAN card, it certainly did when I tested it. Not sure if that's a bug or not, MS need to confirm how it should behave when you have LAN and WLAN NIC's on the same machine.

    As "ipconfig /all" didn't tell you much, look at the result from "route print". The interface list at the top should be in order. You can confirm that by checking the 1st NIC is also the interface with the lowest Metric in the IPv4 route table.

  • jmom

    I do have a physical LAN card. It's on a laptop so there is a built in standard LAN and a built in wireless lan card installed. I dont know which one is the primary... How do you tell You said it needs to go through the Wireless API... I dont understand that... how can you tell a card to use the wireless API Isn't it that you would have to call the card through the wireless API If that is the case then I am since I am calling System.Network.Wireless. It seems strange that the API would not allow you to specify the card to use, and only use the "primary".
  • System.Network.Wireless Not Working