WSUS 3.0 Admin Console Can No Longer Connect

The WSUS 3.0 admin console will not connect. When I select Connect to
Server from the context menu from the Update Services Tree, I get the
Connect to Server dialog into which I enter the server name and port
(8530). I then get an error dialog saying I "do not have permissions
necessary to access the WSUS server. To connect to the server you must
be a member of the WSUS Administrators or WSUS Reporters security
groups."

I added the administrator account I logged on with WSUS Administrators
group but the problem remained.

I uninstalled and reinstalled WSUS 3.0 and was able to connect again
with the admin console, but my clients were not. (In another post
(http://groups.google.com/group/
microsoft.public.windows.server.update_services/browse_thread/thread/
16f987dd28005e15/4a98d25538ba4694#4a98d25538ba4694) I had described
the problems I had trying to get clients to checkin.)

So I took the steps I had taken before to get the clients to connect
(I had also previously has to manually install the updated AU client
for the client PCs, but obviously did not repeat that): reset the
password for the IUSR_LEORA user used for anonymous access and making
sure the integrated windows authentication box had a check in it for
the directories comprising the WSUS Administration website in IIS.

Now the clients were connecting (as I was seeing from the still
running WSUS 3.0 admin console), so I closed the admin console and
tried opening it again. The problem described in the initial paragraph
is now back.

I'm hopeful that given the small number of steps I took between the
console working and the console failing to work, someone can help me
troubleshoot this problem.

I presume this a security issue, but do not know enough about how the
console operates to know how to troubleshoot it. I hope that soemone
who knows more about this can help out.

Thanks.

On May 23, 11:33 am, DWAnderson <gdwander...@gmail.com> wrote:
> The WSUS 3.0 admin console will not connect. When I select Connect to
> Server from the context menu from the Update Services Tree, I get the
> Connect to Server dialog into which I enter the server name and port
> (8530). I then get an error dialog saying I "do not have permissions
> necessary to access the WSUS server. To connect to the server you must
> be a member of the WSUS Administrators or WSUS Reporters security
> groups."
>
> I added the administrator account I logged on with WSUS Administrators
> group but the problem remained.
>
> I uninstalled and reinstalled WSUS 3.0 and was able to connect again
> with the admin console, but my clients were not. (In another post
> (http://groups.google.com/group/
> microsoft.public.windows.server.update_services/browse_thread/thread/
> 16f987dd28005e15/4a98d25538ba4694#4a98d25538ba4694) I had described
> the problems I had trying to get clients to checkin.)
>
> So I took the steps I had taken before to get the clients to connect
> (I had also previously has to manually install the updated AU client
> for the client PCs, but obviously did not repeat that): reset the
> password for the IUSR_LEORA user used for anonymous access and making
> sure the integrated windows authentication box had a check in it for
> the directories comprising the WSUS Administration website in IIS.
>
> Now the clients were connecting (as I was seeing from the still
> running WSUS 3.0 admin console), so I closed the admin console and
> tried opening it again. The problem described in the initial paragraph
> is now back.
>
> I'm hopeful that given the small number of steps I took between the
> console working and the console failing to work, someone can help me
> troubleshoot this problem.
>
> I presume this a security issue, but do not know enough about how the
> console operates to know how to troubleshoot it. I hope that soemone
> who knows more about this can help out.
>
> Thanks.

Anyone?

On May 24, 8:55 am, DWAnderson <gdwander...@gmail.com> wrote:
> On May 23, 11:33 am, DWAnderson <gdwander...@gmail.com> wrote:
>
>
>
>
>
> > The WSUS 3.0 admin console will not connect. When I select Connect to
> > Server from the context menu from the Update Services Tree, I get the
> > Connect to Server dialog into which I enter the server name and port
> > (8530). I then get an error dialog saying I "do not have permissions
> > necessary to access the WSUS server. To connect to the server you must
> > be a member of the WSUS Administrators or WSUS Reporters security
> > groups."
>
> > I added the administrator account I logged on with WSUS Administrators
> > group but the problem remained.
>
> > I uninstalled and reinstalled WSUS 3.0 and was able to connect again
> > with the admin console, but my clients were not. (In another post
> > (http://groups.google.com/group/
> > microsoft.public.windows.server.update_services/browse_thread/thread/
> > 16f987dd28005e15/4a98d25538ba4694#4a98d25538ba4694) I had described
> > the problems I had trying to get clients to checkin.)
>
> > So I took the steps I had taken before to get the clients to connect
> > (I had also previously has to manually install the updated AU client
> > for the client PCs, but obviously did not repeat that): reset the
> > password for the IUSR_LEORA user used for anonymous access and making
> > sure the integrated windows authentication box had a check in it for
> > the directories comprising the WSUS Administration website in IIS.
>
> > Now the clients were connecting (as I was seeing from the still
> > running WSUS 3.0 admin console), so I closed the admin console and
> > tried opening it again. The problem described in the initial paragraph
> > is now back.
>
> > I'm hopeful that given the small number of steps I took between the
> > console working and the console failing to work, someone can help me
> > troubleshoot this problem.
>
> > I presume this a security issue, but do not know enough about how the
> > console operates to know how to troubleshoot it. I hope that soemone
> > who knows more about this can help out.
>
> > Thanks.
>
> Anyone?- Hide quoted text -
>
> - Show quoted text -

FYI, I solved the problem by unchecking "allow anonymous access" in
the directory security of the APIRemoting30 subdirectory of the WSUS
Administration website in IIS.