• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 575
  • Last Modified:

"Discovering" a workgroup name in WXP Pro

Is there a way to discover what the workgroup name is that systems are working under?  I guess I'm looking for if the name is broadcast on a workgroup.  Or, do you *have* to know the name before joining a workgroup?

Thanks!
0
CraigSNYC
Asked:
CraigSNYC
  • 6
  • 4
  • 3
5 Solutions
 
Rob WilliamsCommented:
Should be able to see the workgroup name if you now the IP of one computer that is the member of the workgroup, by running:
nbtstat  -a  <ip address>   such as nbtstat  -a  192.168.123.123
In the returned list, you should see a line:
WorkgroupName   <1E> GROUP

If you don't know the IP of any computers, assuming you are on the same LAN, via DHCP, or some other method, you can scan for IP addresses using a little tool such as TCP Net View:
http://www3.ns.sympatico.ca/malagash/Downloads/TCPNetView/TCPNV.EXE
0
 
Rob WilliamsCommented:
or....
You could use a scanning utility like LANSpy which will return IP's, NetBIOS names, and other information. Included in the NetBIOS names list is the workgroup or domain name.
http://lantricks.com/lanspy/
0
 
Fatal_ExceptionCommented:
Might try this utility, which was brought to my attention in the MVP forums  (free to use):

The Dude network monitor is a new application by MikroTik which can dramatically improve the way you manage your network enviroment. It will automatically scan all devices within specified subnets, draw and layout a map of your networks, monitor services of your devices and alert you in case some service has problems.

http://www.mikrotik.com/thedude.php

By the way, Workgroups don't really mean much in the way of Networking computers...  Their only use is to 'organize' your network..  you don't really 'join' workgroups like you would join a Domain..  For instance, I have some clients that don't want the expense and overhead of running Domains.  I can name every computer in the organization a different Workgroup, but I can access any computer in the Network...  Just so you know and understand..

FE
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
CraigSNYCAuthor Commented:
Hey, FE thanks for the clarification on Workgroups.  Can you explain a bit more about that, or where I can read a bit more about how Workgroups actually function?

Thanks!  

Craig
0
 
Fatal_ExceptionCommented:
Chicagotech has a lot a good information on general networking:

http://tinyurl.com/rmzlt

Windows Networking Myths:

http://www.bcmaven.com/myths.htm

Myth:  All of the computers on a network must use the same workgroup name.

Fact: Windows networking supports multiple workgroups.  Computers in any workgroup can access computers in any other workgroup.  Workgroups have no role in network access, and they don't provide any type of security.
Explanation: It's a little easier to access computers in the same workgroup than in other workgroups.  In Windows 95 and 98, computers in the same workgroup appear immediately when you open Network Neighborhood, and you need to click Entire Network to access other workgroups.



0
 
Fatal_ExceptionCommented:
You would think with everything that has been written about Windows Networking, the subject of Workgroups would be more fully explained, but I find no good references to this...  Basically, Workgroups just make organizing computers in a Wins or Netbios environment easier to find..  I do have a pretty good article on Netbios, posted on my Help Pages of my site, which is much more important in understanding Windows Networking than Workgoups.  Feel free to visit and read at your leisure:

http://65.24.134.81/KipSolutions/NetBios/netbios.htm

(www.doverproductions.com)

FE
0
 
CraigSNYCAuthor Commented:
FE,

I read the NetBios article on  your site. (great info!!) Just so that I completely understand: Without NetBios enabled, systems would not be able to communicate within a Workgroup?  

Thanks so much for your time!

Craig
0
 
Fatal_ExceptionCommented:
:)  Not necessarily.  Network Neighborhood or My Network Places populates using Netbios.  In today's environment (2K and XP) we use Netbios over TCP (NBT) to populate these.

If you disable it, then you can always get to a network share (or PC) using the Run Line:  \\ipaddress (or computername)
Workgroups do not come into play then...  :)

FE
0
 
CraigSNYCAuthor Commented:
FE,

Before I close out the question I was wondering if you had any other useful network tools you wanted to share.  I've checked out all the ones you've listed already and they're all great and will be helpful in future trouble shooting.

Craig
0
 
Rob WilliamsCommented:
Another I like for collecting network information, and is free is: http://www.lookatlan.com/
0
 
Rob WilliamsCommented:
Thanks CraigSNYC,
--Rob
0
 
Fatal_ExceptionCommented:
Yes, thanks, and best of luck!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 6
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now