1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Workgroup or Domain?

Discussion in 'Networking (Hardware & Software)' started by bravo66, 2004/12/10.

Thread Status:
Not open for further replies.
  1. 2004/12/10
    bravo66

    bravo66 Inactive Thread Starter

    Joined:
    2004/12/10
    Messages:
    1
    Likes Received:
    0
    I manage a network of about 300 servers & 6000 workstations. I have a single NT 4.0 domain structure, and about a dozen workgroups that I can not bring into my domain for one reason or another. I have a lot of vendors doing work here and we can not monitor each vendor every second they are here. So, like any good network admin, I assume everyone is out to ruin my network, and I worry about a vendor creating a new NT domain without my knowledge. I wish to have a way to know when a new domain is created on my network.
    My question is this. When I view my network thru "My Network Places ", windows uses the same icon to represent both domains and workgroups and the icon properties tells you nothing about if the item is a domain or workgroup. Does anyone know of a method or tool that will allow me to look at these names and determin if it is a domain or a workgroup?

    Thanks for any help....
     
  2. 2004/12/10
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    http://www.exporterpro.com/hyena/ has a 30 day free trial and is a tool I've used for years. I consider it my one essential for general network admin and it will certainly do what you want.

    Network Neighborhood is a major horror story for a network the size of yours.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2004/12/13
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    That looks like a nice utility Newt is pointing you to.

    However, if you don't go that way you could use the nltest command to check the workgroup/domain. If you use the /dsgetdc:<domainName> switch, it will tell you if the domain exists and also some information to help you track it down.

    For example if you have a workgroup called henry:

    nltest /dsgetdc:henry

    will result in "DsGetDcName failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN "

    The output you get if henry is a domain depends on the domain (for example, the output from an NT4 DC is different to that from a 2003 AD server), but includes the domain controllers name and possibly its IP address. Try it on your own domain first to see how that shows up.
     
  5. 2004/12/13
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    ReggieB - if I had to choose between giving up Hyena or factory sliced bread, I'd be eating my bread in chunks. Hyena vs. red meat and I'd have to think a while but I suspect I'd eat more pork and fish.

    The longer I use it, the better I like it. If a co-worker asks if Hyena will do ..... (anything we never tried to use it for before) I say yes and haven't been wrong in a long while.

    We have 42 DCs and 42 GC servers located in a bunch of states and a few foreign countries that I can get to via the local GC server by just pointing the LDAP entry at it. Working with any of the local resource domains (NT4 still) or workgroups is even easier.
     
    Newt,
    #4
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.