Technical: Microsoft – Networking / Active Directory – Net Commands

Technical: Microsoft – Networking / Active Directory – Net Commands


One of the things I like about OS/X and Unix is that one gets in the habit of doing many things through the command line.

Whereas in Windows, one will use a GUI to get quick information.

But, truthfully Microsoft has many facilities for accomplishing things through the command line, or shall we say terminal mode, as well.


In the Valley, the saying goes “Got tired of patch Tuesday, and so went Goggling“.
But before you go, you can at least give Street Creds to Redmond, also.

List Active Directory User Profile


net user "<AD Account>"  /Domain 


net user "danieladeniji"  /Domain

Sample Output:


List Active Directory Domain groups that a user belongs to


net user "<AD Account>"  /Domain | find "Group"


net user "danieladeniji"  /Domain | find "Group"

Sample Output:

Local Group Memberships
Global Group memberships *Marketing *GAMERS


  • The user does not belong to any local group; which is not true, but since we are targeting via “/Domain” we will overlook for now
  • And, he belongs to a couple of Domain Groups (Marketing and Gamers)

List all Active Directory Domain groups


net group /Domain


net group  /Domain

List Members of Active Directory Domain group


net group "<AD Group Name>" /Domain


net group "Domain Admins"  /Domain


List Shared folders on a remote machine

The net view commands lists the shared resources on a remote machine.


net view \\<machine-name>


net view \\DWP


List Local Services

List Local Services.


net view


net view



References – Net Commands – NetUser

References – Net Commands – NetGroup

Atheros AR5006 EXS Wireless Network Adapter & MS Windows Vista ( trying to AT&T Universe supplied Wireless Access Point to get online) – Error “Unidentified Network”

A good friend texted me last week saying that upon the family upgrading to AT & T \ SBC U-verse one of their laptops is no longer able to connect to the Internet.  That is two of three computers are able to connect, but one last lone laptop is not.

He is a good friend and he is computer savvy.  And, I know he would not contact me unless he is tried and he really needs the help.

And, so he volunteered to bring the computer over, but I know it would not really help; as I needed to observe the interaction between his laptop and and the wireless access point.

But, first I had him connect the laptop to the Wireless Access Point via a Network Cable and that worked.

Drove over and spent the next 3 to 4 hours there tried everything.  But, nothing worked. Here are the things we tried:

  • Via Control Panel, Device Manager, removed the Wireless Adapter and had windows rediscovered it
  • Restarted Wireless Access Point
  • Unchecked IPV-6
  • Spent hours re-installing the TCP/IP Stack; since too many times when viruses take out the TCP/IP stack

The errors we were getting included:

  • Unidentified Network
  • On the “Network and Sharing” center, we were gaining connection to the WAP.  But, post WAP, no connection to the Internet
  • On the Status Window of the Wireless Card, we registered “Sent” traffic, but no “Received” traffic

Had a chance to think it over this last weekend and so was happy when he called that he will come by on Sunday evening.  Outside of watching “60 minutes” on CBS, my Sunday evenings are free.

Once he brought the computer by, I went to Control Panel \ Devices and checked the date-stamp on his Wireless Device Driver.

It was a bit dated:

Date: 11/20/2006

Googled for “Atheros AR5006 EXS Wireless AR 5006 EXS Wireless” Drivers and found a later one:

Date: 4/22/2009

So downloaded the new one:

Toshiba – Wireless Connection Portal

BTW, here is a link to a slightly newer version:

Atheros Wireless LAN Driver for Windows Vista (32bit/64bit)

Date: 6/30/2009

Had problems getting it to work until I extracted it.  Here is the folder hierarchy once extracted:

Atheros - Extracted Folder

There are two folders:

  • VistaDrv  –> Actual Device Driver
  • Vistautl –> Utility

Sojourn to the VistaDrv folder and run the setup.exe.

Once installed, revisit Control Panel\Device Manager and validate that your Atheros Wireless Driver is now or later.

There are so many renditions of this problem on the Net:

The most comprehensive that I found post fixing the problem and doing my write-up is Aseem Kishore’s entry:

One can quickly see that he has seen his share of desktop networking problems – “Little Game Recognizing Big Game”

Fix Unidentified Network and No Network Access in Windows 7

HP Pavilion — a847c Desktop – MS Windows – “Other Devices” “Ethernet Controller” –> Yellow Mark

HP Pavilion — a847c Desktop – MS Windows – “Other Devices” “Ethernet Controller” –> Yellow Mark

It all started one Saturday morning, actually this morning (Sat 2010-10-02) to be exact. A friend’s HP Pavilion hard-drive crashed and a new drive had been placed in for a couple of weeks now. But, only now completed MS Windows XP install. Only God knows how long it takes to apply all the security patches one has to download and apply these days.

Anyways, most everything was done. But, still there was a yellow exclamation mark that wouldn’t budge in the Control Panel \ Device Manager applet.

Visited HP’s Support site numerous times to see if I could find a matching driver, but no luck.

Reviewed, the Product Specifications – HP Pavilion a847c Desktop PC Product Specifications (, but very little detail regarding the Networking “elements”.

The specification per-functionary makes mention of “Network (LAN) – Integrated 10/100 Base-T Networking Interface”. And, that is it.

On HP’s Support \ Drivers web page , the closest we came to the drivers is:

HP Customer Care > HP Pavilion a847c Desktop PC > Microsoft Windows XP > Spring 2005 Original Network Adapter Driver Collection
but, even after downloading the driver, extracting the zip file, the extracted files lacked an install program (setup.exe) and the accompanying documentation yet failed to draw us any closer to knowing if we had the needed files.
So reached back and brought out an old trusted friend and companion (Halfdone Development – Unknown Devices
The “Unknown Devices” application immediately recognized the device as an “Atheros AR5212 Wireless”. So off I googled for that manufacturer and driver, but all
to dead ends. It appears that the driver is not publicly published, nor supported by the Vendor.
Googled some more and found a couple of Applications that would detect the “unknown devices” and match them with corresponding drivers.
Some of the Applications that were downloaded and tried are: DriverMedic and Unible – DriverScanner. But, as they were both commercial applications, could least afford them; at least on a broke Saturday morning ( on the 2nd day of October).
After much searching found the drivers on DriverGuide ( Yes, had to endure and click through about 15 advertisement pages, but as long as I hard searched it was worth it.
Once the compressed\zip file is downloaded please extract it and return to MS Device Manager where will be able to affix the newly downloaded drivers to the “Ethernet Controller”.
So that is the long story. A shorter story and possibly more official driver can be gleaned from this next paragraph.
Luvr, a techspot member, gave an espidodial journal, of a similar journey in “Getting Atheros AR5212 Wireless Cards to Work with Windows XP “. The URL
is He rightfully directed readers to download the drivers from AirLink’s web site @
MS write-up about “Unknown Devices”

How to troubleshoot unknown devices that are listed in Device Manager in Windows 2000


MS SQL Server – Installation – v2005

During a recent MS SQL Server Installation, actually a Service Group change, we ran into a problem:

The problem was logged in one of SQL Setup log files created under C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files.  The name of the file is

The error message is:

Transact package threw an exception.
        Error Code: 0x80070043 (67)
Windows Error Text: The network name cannot be found.

After a bit of thought, I decided to look a bit further into the network name I entered as an option in the setup command line:


The problem ended up being a wrong verbage for the network name: 
      It should have read Public Network rather than Public1

Yours may be different, depending on what is listed under Network, in the “Parameters” tab of your “IP Address” resource.

Note, that is available through the Cluster Administrator.