Solved: Cannot find the WINS Server - Access is denied

Create Account

Windows Server 2003

Questions

Followers

Top Experts

WayneKessler

Cannot find the WINS Server - Access is denied

Hi, folks.

I have a Windows Server 2003 set up as a WINS Server. It was an upgraded W2K Server.

The WINS service is running, and clients can connect. However, when I click on the WINS MMC Snap-In, the right pane displays the subject error and indicates in the body of the text that:

The error was: Access is denied.

I don't understand how this could be. There are no errors in the logs, and I am logged on as a Domain Admin.

Any ideas? We can't manage WINS if we can't get to the interface...

Thanks very much.

Wayne Kessler

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

rhandels🇳🇱

Are you using the WINS MMC on the server itself or from a remote machine. Also, try to go to run, choose mmc, on edit choose add/remove snap in and add the single WINS mmc. Then try to access it again, this might help..

WayneKessler

ASKER

I am trying to access the MMC on the server's console.

It does not work from the Manage Server console or from the WINS console that is added to Administrative Tools or from a new MMC.

I've tried them all.

rhandels🇳🇱

Hi,

If you restart the WINS service, does that give any relief??

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

WayneKessler

ASKER

No.

I have been troubleshooting this for weeks. Reboots do not work. The service starts/restarts just fine.

rhandels🇳🇱

Hi,

Looks like this is your problem.

http://support.microsoft.com/?kbid=287727

This issue occurs because the WINS manager is dependant on the Remote Registry Service. If this service is not running, the WINS component is not initialized. However, the WINS service starts and looks as if it is running, but the WINS snap-in generates the error described in the preceding section.

And the solution...

To resolve this issue, start the Computer Management console, click Services, and then set the Remote Registry Service to Automatic.

WayneKessler

ASKER

The Remote Registry service has been running since day one. It is running now, and startup shows set as Automatic.

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

rhandels🇳🇱

Damn, i did think this was the solution.... I'm out of ideas. This should be working....

ASKER CERTIFIED SOLUTION

rhandels🇳🇱

membership

Signing up is free and takes 30 seconds. No credit card required.

Create Account

WayneKessler

ASKER

Great! That did it.

This is what it said:

Go to the registry on the DC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

Add a permission for "Local Service" Full Control. This is a fix from Microsoft, however it has not been published yet.

For the sake of the thread here, our WINS server is not a DC. Here's what I did:

REGEDT32 to the spot mentioned. Permissions, added SERVICE (Full Control) after changing the location from the domain to the local computer.

Thanks very much!

rhandels🇳🇱

Hi,

Glad to be of help...

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

rolfecat

This worked perfectly. Thanks for the tip!!!

mbhumphries

Thanks. That fixed our issues also.

beargonefishing🇺🇸

That's what I needed. Thanks a bunch!

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

GTDean55

Worked for me too! THANKS!!

tcorley

Just a small note. Adding the LOCAL SERVICE to the registery entry solves the problem. I wasn't able to do this until I gave the DC the PDC role, and was able to add LOCAL SERVICE to the list. Took me a while to work this out, hope this saves someone time..

Windows Server 2003

Questions

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).