WSUS Support Forums: New WSUS install cannot connect to server - WSUS Support Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

New WSUS install cannot connect to server

#1 User is offline   tim5700 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 19-Oct-07

Posted 19 Oct 2007, 08:12

Hello,

I have a server that I am trying to run WSUS as a downstream server on. I cannot connect to the server using the management console. When accessing the console I get this error message:

"Cannot connect to 'computername'. The server may be using another port or different Secure Sockets Layer setting."

Here are the details on the server:
OS = Windows Server 2003 R2 x64
It is a DC
It runs Symantec Backup Exec, Symantec Corp AV client & VMWare server.

IIS runs the default website on port 80, VMWare Mgmt on & WSUS admin on port 8530. I have tried installed the WSUS page in IIS using both the default page and by using a custom page, the results are the same.

There is no firewall software running on the server. I can view the default page, when I access the WSUS page at port 8530 I get 403 forbidden error.

I have the following errors in the server's application log:

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The DSS Authentication Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12042
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The SimpleAuth Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The Client Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12032
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The Server Synchronization Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The API Remoting Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12002
Date: 10/19/2007
Time: 9:46:03 AM
User: N/A
Computer: COMPUTER
Description:
The Reporting Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.


Any help is appreciated.

This post has been edited by tim5700: 22 Oct 2007, 06:33

0

#2 User is offline   joseti 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 242
  • Joined: 11-Oct-07

Posted 19 Oct 2007, 09:04

Check permissions on the server. Start with the program files\update services directory and the %windir%\microsoft.net\framework directory and make sure network service has read permissions. Check other permissions according to this doc:
http://technet2.micr...fd338c1033.mspx

If it is still failing use process monitor to log events as you restart the Update services service and then search on "access denied".
http://www.microsoft...essMonitor.mspx
0

#3 User is offline   tim5700 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 19-Oct-07

Posted 19 Oct 2007, 10:06

View Postjoseti, on Sat 20th Oct 2007, 02:04 am, said:

Check permissions on the server. Start with the program files\update services directory and the %windir%\microsoft.net\framework directory and make sure network service has read permissions. Check other permissions according to this doc:
http://technet2.micr...fd338c1033.mspx

If it is still failing use process monitor to log events as you restart the Update services service and then search on "access denied".
http://www.microsoft...essMonitor.mspx


OK,

I ran cacls against the framework directory and confirmed the network service had read access. I checked the permissions listed on
http://technet2.micr...fd338c1033.mspx

Those permissions are correct.

I ran process monitor and restarted the update services service I received several 'access denied' entries for RegOpenKey for the service under /HKLM/Software/Microsoft/EnterpriseCertificates and SystemCertificates. I gave the network service first read, followed by full control rights with no luck.
0

#4 User is offline   joseti 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 242
  • Joined: 11-Oct-07

Posted 19 Oct 2007, 15:14

If you are using WSUS 3 there is no http\IE admin option. You have to access it through the admin console which is MMC based. Are you doing this locally on the WSUS server or remote. If local look in admin tools for the WSUS snap in, if remote you have to install the admin console from the setup exe. Check and see if you can access the console. If the errors are correct I doubt you will be able to but lets verify the errors are accurate.
0

#5 User is offline   tim5700 

  • Newbie
  • Pip
  • Group: Regular Members
  • Posts: 3
  • Joined: 19-Oct-07

Posted 22 Oct 2007, 06:24

View Postjoseti, on Sat 20th Oct 2007, 08:14 am, said:

If you are using WSUS 3 there is no http\IE admin option. You have to access it through the admin console which is MMC based. Are you doing this locally on the WSUS server or remote. If local look in admin tools for the WSUS snap in, if remote you have to install the admin console from the setup exe. Check and see if you can access the console. If the errors are correct I doubt you will be able to but lets verify the errors are accurate.


Right, I am trying to access the console locally. However, the reason I mention the http is because the admin console connects to the virtual directory in IIS.
0

#6 User is offline   joseti 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 242
  • Joined: 11-Oct-07

Posted 22 Oct 2007, 20:31

Ok, I understand. You are right, the WSUS snap-in/MMC connects to the WSUS server via the APIremoting30 virtual directory but does not use http.

Are you see any errors in the program files\update services\logfiles\softwaredistribution.log file?

How about the IIS log files? Any errors besides the 403?
0

#7 User is offline   Heinz 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 2
  • Joined: 24-Oct-07

Posted 24 Oct 2007, 23:49

I had the exact same "Services Not Working" issue - I had a look @ the WSUS3 Operations guide (Appendix C: IIS Settings for Web Services) and saw most of those services there listed with "Security: Anonymous Access Enabled" I found and changed "SelfUpdate" to allow Anonymous Access, rebooted & all those errors went away @ the same time "Updates Ready to be installed" balloons started to appear on most of my workstations.

However when I now try to go into the WSUS3 MMC I get "You don't have premissions required to access this WSUS server" I added myself to the local WSUS Administrator & Reporters security group - I even found a WSUS goup on the AD & added myslelf there - Still no luck!! same problem.

Any one have any suggestions?

thanks in advance

Heinz
0

#8 User is offline   joseti 

  • Advanced Member
  • PipPipPip
  • Group: Regular Members
  • Posts: 242
  • Joined: 11-Oct-07

Posted 25 Oct 2007, 13:56

have you logged off and then logged back on so your security token will get the new groups?
0

#9 User is offline   Heinz 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 2
  • Joined: 24-Oct-07

Posted 25 Oct 2007, 21:36

Yes, in fact I rebooted the server twice - no luck
0

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users