No console access through MMC, but can connect to server via IE OK

WSUS v3 SP2

Running on LAN
No SSL (yet)

Using port 8530 I can connect and download a test file OK:
http://myserver.domain.com:8530/iuident.cab

myserver.domain.com is a split DNS so internally it's resolved to the same
IP as the internal server name 'WSUS_1'

When using the mmc console to connect it's fine when using the server name
(WSUS_1), but if I use 'myserver.domain.com' it fails to connect with: "The
server may be using another port or different Secure Sockets Layer setting."

I've tried adding all sorts to the local host file to see if it's a host
name to IP mapping issue - no change

What am I missing here?

BTW- the reason I want to access via calling myserver.domain.com is that I
can't produce ac ert through the IIS6 wizard with SANs and so calling WSUS_2
in the console will fail with cert warning unless it's added as a SAN.

If I could generate a cert with SANs from IIS6 everything would
work...anyone know of a cert wizard?

Any help much appreciated.
Lea

"LeaUK" <> wrote in message
news:71FA1E95-A32A-4A0C-BE95-...

> When using the mmc console to connect it's fine when using the server name
> (WSUS_1), but if I use 'myserver.domain.com' it fails to connect with:
> "The
> server may be using another port or different Secure Sockets Layer
> setting."

Two possibilties..

1. DNS is not properly resolving 'myserver.domain.com' to the internal IP
Address.

2. IIS is not properly configured to respond to requests addressed to
'myserver.domain.com'.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" wrote:

> "LeaUK" <> wrote in message
> news:71FA1E95-A32A-4A0C-BE95-...
>
> > When using the mmc console to connect it's fine when using the server name
> > (WSUS_1), but if I use 'myserver.domain.com' it fails to connect with:
> > "The
> > server may be using another port or different Secure Sockets Layer
> > setting."
>
> Two possibilties..
>
> 1. DNS is not properly resolving 'myserver.domain.com' to the internal IP
> Address.

DNS is fine
>
> 2. IIS is not properly configured to respond to requests addressed to
> 'myserver.domain.com'.
>

IE connects fine, it's a weird one but it's specific to the WSUS console..

Solved by eventually working out how to add SANs to the certificate. Placed
the internal name of the WSUS_server in teh SAN and voila...


>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2010)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

Lea