WSUS 3.0 server connection error

Hello,

I am running SBS 2003 R2 and am having trouble getting WSUS 3.0 SP1 going on the machine. I have installed both the server and the console on the same box but when I try to connect to the wsus server from the MMC console I get the following error message:

Cannot connect to MYSERVER the server maybe using another port or different SSL setting.

I have tried to connect on all ports (80,8530,8531,443) but with the same error message. Netstat confirms that the computer is listening on 8530

This above problem  may tie in with another error message I get when I try to reinstall WSUS and start over. At the very final stages of the WSUS installation I get the following message:

An error occurred when communicating with the server and this wizard must be closed. You may restart WSUS server configuration wizard from the options page in the WSUS console.

My SBS2003 install is running the default settings so nothing special in that department. I have not made any changes to SSL or the IIS manager. One notable exception would be that there is a sharepoint server website in the IIS manager but Im pretty sure that Ive uninstalled the program. During installation I am told that the default port would be: http://MYSERVER:8530 because I already have a service using port 80. All other settings during installation are standard.

Can anyone help?
eddix99Asked:
Who is Participating?
 
ChiefITConnect With a Mentor Commented:
These two SBS machines are both running defaults.


Umm, I don't know if anyone told you this, but SBS machines have to be the FSMO role holder. Having two of them on the same domain will not work.
0
 
ChiefITCommented:
Did you set up the GPO, that points your clients to the server using port 8530?

0
 
eddix99Author Commented:
I haven't got to that stage yet. Both the server wsus component and the client wsus component are on the same SBS box. The problem is these two talking to each other on the same machine. Am I doing something wrong?

Ed
0
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.

 
ChiefITCommented:
That GPO defines the path. Though, these items are on the same box, they need that DNS path to communicate. I know, it is odd.
0
 
eddix99Author Commented:
I have been setting up some GPOs and have applied them to the domain and I'm pretty sure that I'm doing it right but i'm still having problems connecting to the server.

Yesterday I installed WSUS on another SBS machine just fine. I got the setup wizard to load but I havent yet set up the clients.  On the problem machine I cant even get the setup wizard to show.
These two SBS machines are both running defaults.

Not sure what to do?
0
 
eddix99Author Commented:
These machines are not on the same domain. I manage two separate domains, each with their own clients and member servers.

0
 
Olaf De CeusterConnect With a Mentor Commented:
Please reinstall R2 components on your SBS. Test WSUS2 first, than upgrade to WSUS 3.0 SP1.
http://www.petri.co.il/install_wsus_3_on_sbs_2003.htm
Olaf
0
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.

All Courses

From novice to tech pro — start learning today.