Skip to main content

misc: netstumbler in vista...

in truth, it doesn't work. apparently there isn't a version of netstumbler that works yet with vista. the reason i was looking was because i was having some problems with connectivity or something.  i thought i'd switch the channel that my ap was using to something that wasn't being used in my immediate area.  i couldn't get any information out of the wireless networks gui (or at least i have no idea how).  ah well. 

netstumbler wasn't showing any active access points. :/ ... but speaking of stumbling... i did stumble across this gem on windowsconnected.com. in short, you can get information on wireless networks using netsh!  here's the command:

 

netsh wlan show networks mode=bssid 

Comments

  1. Great, information!!!!!!!!

    ReplyDelete
  2. I don't know why I never thought of that... but damn, that's almost more useful than netstumbler anyway!

    ReplyDelete
  3. Sweet! Just what I was looking for as an alternative to Netstumbler in Vista!

    ReplyDelete
  4. Hi...
    I downloaded netstumbler(the latest version) and installed it on an Hp laptop running Vista and having an intel pro wireless a/b/g card. At first I found out that it was not working (netstumbler was appearing the follow message "access denied"). After hours of trying to make it work I made it... The only thing it needed was to open netstumbler as admin (right click on netstumbler--->enter as admin) and it finally worked...I hope it will help you---sorry if it is hard for you to understand what i have written but....Greece--

    ReplyDelete
  5. I got Netstumbler to RUN in Vista, but I get the dreaded "Access Denied" message after that. uuuggghhh...

    ReplyDelete
  6. I've developed sort of a netstumbler clone for vista, you can download it here: http://wifistudio.100webspace.net/

    ReplyDelete
  7. Check this out:

    http://www.codeproject.com/gadgets/WifiScanner.asp

    A nice GUI that works with Vista and the netsh command.

    ReplyDelete
  8. Works fine just run it as administrator.

    ReplyDelete
  9. Checkout Inssider from MetaGeek:
    http://www.metageek.net/products/inssider

    ReplyDelete
  10. Netstumbler wont work with my onboard Intel wirless. That command worked great. But the real gem is the program link for Inssider. It picked up all the wireless in my hood, including the MAC applenet blasting on channel 11 friggin up my wireless.

    ReplyDelete
  11. yer great information... the only program that seems to have any home is the one that is called "gem" and you need to register to get it..
    i just registered and am still waiting for an e-mail..

    if ur gona help do it properly and list the name of the program at least instead of sending people around in a circle

    running net stumbler as administrator does f'all.

    try it do it then post

    ReplyDelete
  12. still waiting for an email ?!?!?


    What a goofball.

    ReplyDelete
  13. thanks !!!!

    ReplyDelete
  14. You can get netstumbler to work in vista, First you need to install an XP driver for your wireless card, i go to hp to get the driver. then you run the program as admin, Wallah! it works ;) gl with it though

    any questions send me an email

    00taggerung@sbcglobal.net (not my usual email might take a little while for me to respond)

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m