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

Microsoft Windows Network Unknown Workgroup

There is a new workgroup inside my Microsoft Windows Network that I cannot access. I do not know who created it.  When I try to open it I get this message: "NODENAME. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions".
How can I find out what machines belong to it?
How can I find out who created it?
It is not part of the domain.
We already joined the workgroup with a pc and we could only see our machine.

1 Solution
Some 3rd party devices like routers etc that support uPnP show up as a separate workgroup. Have you checked your routers etc?
When you bring a new computer onto the domain many times it is in a "Workgroup" workgroup  by default and windows will pick this up an cache the fact that this workgroup existed and then leave an empty workgroup when that computer is added to the domain.  I'm not sure that the timeout is, but I BELIEVE that the domain controllers cache that workgroups existence until reboot.  (May be a specific time frame, but I'm not aware of it.)
iidseAuthor Commented:
We used the command nbtstat
That gave us the name of a printer and a mac address.  But when I log into the printer I cannot find the workgroup setup anywhere.
That name is listed in the domain controller WINS.

1.It is probably a workstation that has been in this workgroup once. It then creates it in the networkfolder.
I dont know how many workstations you got. Probably one is giving the problem. If you solve that, that folder should go away after a few hours (browserservice will delete it)

2.Domains and workgroups list are provided by the Master Browser of your network.

You can find the Master Browser with the tool Browstat : http://www.howtonetworking.com/Windows/computerbrowser.htm

Normally, the cache on the Master Browser should be up to date, but it doesn't seem to be your case.  So you try to clear the cache with these commands:
nbtstat -R and nbtstat -RR

Ref this EE post for same issue...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now