|
| WSUS 3.0 installation problems... |
 |
Wed, 5 Mar 2008 05:39:00 -0800 |
Main WSUS server has been upgraded to WSUS 3.0 and it runs Windows Server
2003 SP2.
I decided to upgrade my remote office servers, which will be getting their
updates from my main WSUS server.
I attempted to upgrade two servers and the installation went fine except for
the last part...the wizard fails to run. I try to open the console and I get
this message: Cannot connet to <server-name>. The server may be using
another
port or different Secure Sockets Layer setting.
At first, I was letting WSUS use default port 80 configuration, but later on
I tried using 8530 port and this still gives me the same problem.
All my servers are fully patched, and running .NET 2.0 SP1.
I saw several posts about this message, on a different forum, but I could
not find a proper solution for my case.
|
| Post Reply
|
| RE: WSUS 3.0 installation problems... |
 |
Sun, 30 Mar 2008 20:46:00 -070 |
Have you tried upgrading to WSUS 3.0 SP1 on both machines? I did and it
solved quite a few problems.
It may have something to do with a firewall or port 80.
Cheers,
Lara
"Edward" wrote:
> Main WSUS server has been upgraded to WSUS 3.0 and it runs Windows Server
> 2003 SP2.
>
> I decided to upgrade my remote office servers, which will be getting their
> updates from my main WSUS server.
>
> I attempted to upgrade two servers and the installation went fine except
for
> the last part...the wizard fails to run. I try to open the console and I
get
> this message: Cannot connet to <server-name>. The server may be using
another
> port or different Secure Sockets Layer setting.
>
> At first, I was letting WSUS use default port 80 configuration, but later
on
> I tried using 8530 port and this still gives me the same problem.
>
> All my servers are fully patched, and running .NET 2.0 SP1.
>
> I saw several posts about this message, on a different forum, but I could
> not find a proper solution for my case.
>
|
| Post Reply
|
| RE: WSUS 3.0 installation problems... |
 |
Tue, 1 Apr 2008 05:46:06 -0700 |
I am having the same issue.
I am running Server 2003 SP2 w/ WSUS 3.0 sp1 and I can run it fine through a
RD Connection but not on my box with the SUSsp1 admin installed, but when I
try to connect (port 80-default and has never changed) I get the "Cannot
connect to 'SERVERNAME'. The server may be using another port or different
Secure Sockets Layer setting." Everything was working fine last week.
Dave
"Edward" wrote:
> Main WSUS server has been upgraded to WSUS 3.0 and it runs Windows Server
> 2003 SP2.
>
> I decided to upgrade my remote office servers, which will be getting their
> updates from my main WSUS server.
>
> I attempted to upgrade two servers and the installation went fine except
for
> the last part...the wizard fails to run. I try to open the console and I
get
> this message: Cannot connet to <server-name>. The server may be using
another
> port or different Secure Sockets Layer setting.
>
> At first, I was letting WSUS use default port 80 configuration, but later
on
> I tried using 8530 port and this still gives me the same problem.
>
> All my servers are fully patched, and running .NET 2.0 SP1.
>
> I saw several posts about this message, on a different forum, but I could
> not find a proper solution for my case.
>
|
| Post Reply
|
|
|
|
|
|
|
|
|
|