Problem Activating/Connecting via Port 443

I upgraded 2 servers from Windows Server 2000 to Windows Server 2003. While
I can activate 1 just fine, the other will not activate.

I debugged the problem and found that this server cannot connect to
microsoft.com on port 443. HOWEVER, it can connect to a host of other SSL
sites on port 443. Even Telnet to www.microsoft.com on port 443 does not
work.

Both machines are identical in their network configurations (with the
exception of the static IP). Each has 1 NIC with the same DNS, WINS, and
default gateway. There is a firewall, but it doesn't block 443 (BUT, I even
swapped their IPs to give the "broken" machine the other "working" machine's
IP, brought down the "working" machine, and it still failed).

It's funny that the only site affected is microsoft.com. I've checked the
Internet Connection settings, and there doesn't appear to be anything fishy.
I cleared the SSL State cache, all temporary objects, but still no luck.

Any ideas on how I can get this connectivity back?

--
Doug Thews
Director, Customer Solutions
D&D Consulting Services
----------------
Visit my Tech Blog at:
http://www.ddconsult.com/blogs/illuminati/

microsoft.com is not listening on the SSL port.
www.microsoft.com IS listening on the SSL Port...

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-(E-Mail Removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Tue, 6 Jul 2004 10:34:49 -0500, "Doug Thews"
<(E-Mail Removed)> wrote:

>I upgraded 2 servers from Windows Server 2000 to Windows Server 2003. While
>I can activate 1 just fine, the other will not activate.
>
>I debugged the problem and found that this server cannot connect to
>microsoft.com on port 443. HOWEVER, it can connect to a host of other SSL
>sites on port 443. Even Telnet to www.microsoft.com on port 443 does not
>work.
>
>Both machines are identical in their network configurations (with the
>exception of the static IP). Each has 1 NIC with the same DNS, WINS, and
>default gateway. There is a firewall, but it doesn't block 443 (BUT, I even
>swapped their IPs to give the "broken" machine the other "working" machine's
>IP, brought down the "working" machine, and it still failed).
>
>It's funny that the only site affected is microsoft.com. I've checked the
>Internet Connection settings, and there doesn't appear to be anything fishy.
>I cleared the SSL State cache, all temporary objects, but still no luck.
>
>Any ideas on how I can get this connectivity back?

http://www.microsoft.com:443 doesn't work either. This is the reason why
this machine won't activate. The other machine gets to this URL just fine.

Any suggestions?

------
Doug Thews
D&D Consulting Services

http://www.ddconsult.com/blogs/illuminati/
"Jeffrey Randow (MVP)" <jeffreyr-(E-Mail Removed)> wrote
in message news:(E-Mail Removed)...
> microsoft.com is not listening on the SSL port.
> www.microsoft.com IS listening on the SSL Port...
>
> Jeffrey Randow (Windows Networking & Smart Display MVP)
> jeffreyr-(E-Mail Removed)
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
> http://www.remotenetworktechnology.com
> Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
>
> On Tue, 6 Jul 2004 10:34:49 -0500, "Doug Thews"
> <(E-Mail Removed)> wrote:
>
> >I upgraded 2 servers from Windows Server 2000 to Windows Server 2003.
While
> >I can activate 1 just fine, the other will not activate.
> >
> >I debugged the problem and found that this server cannot connect to
> >microsoft.com on port 443. HOWEVER, it can connect to a host of other
SSL
> >sites on port 443. Even Telnet to www.microsoft.com on port 443 does not
> >work.
> >
> >Both machines are identical in their network configurations (with the
> >exception of the static IP). Each has 1 NIC with the same DNS, WINS, and
> >default gateway. There is a firewall, but it doesn't block 443 (BUT, I
even
> >swapped their IPs to give the "broken" machine the other "working"
machine's
> >IP, brought down the "working" machine, and it still failed).
> >
> >It's funny that the only site affected is microsoft.com. I've checked
the
> >Internet Connection settings, and there doesn't appear to be anything
fishy.
> >I cleared the SSL State cache, all temporary objects, but still no luck.
> >
> >Any ideas on how I can get this connectivity back?
>

Hey guys, I'm really stuck here and time is running down for activation.
Can anyone help me with getting connectivity going under port 443 on this
one server (the other upgraded one works fine). And it's only against the
MS site. SSL/port 443 works fine for any other site I can think of.

Any help would be appreciated.

--
Doug Thews
D&D Consulting Services
http://www.ddconsult.com/blogs/illuminati/


"Doug Thews" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> http://www.microsoft.com:443 doesn't work either. This is the reason why
> this machine won't activate. The other machine gets to this URL just
fine.
>
> Any suggestions?
>
> ------
> Doug Thews
> D&D Consulting Services
>
> http://www.ddconsult.com/blogs/illuminati/
> "Jeffrey Randow (MVP)" <jeffreyr-(E-Mail Removed)>
wrote
> in message news:(E-Mail Removed)...
> > microsoft.com is not listening on the SSL port.
> > www.microsoft.com IS listening on the SSL Port...
> >
> > Jeffrey Randow (Windows Networking & Smart Display MVP)
> > jeffreyr-(E-Mail Removed)
> >
> > Please post all responses to the newsgroups for the benefit
> > of all USENET users. Messages sent via email may or may not
> > be answered depending on time availability....
> >
> > Remote Networking Technology Support Site -
> > http://www.remotenetworktechnology.com
> > Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> >
> > On Tue, 6 Jul 2004 10:34:49 -0500, "Doug Thews"
> > <(E-Mail Removed)> wrote:
> >
> > >I upgraded 2 servers from Windows Server 2000 to Windows Server 2003.
> While
> > >I can activate 1 just fine, the other will not activate.
> > >
> > >I debugged the problem and found that this server cannot connect to
> > >microsoft.com on port 443. HOWEVER, it can connect to a host of other
> SSL
> > >sites on port 443. Even Telnet to www.microsoft.com on port 443 does
not
> > >work.
> > >
> > >Both machines are identical in their network configurations (with the
> > >exception of the static IP). Each has 1 NIC with the same DNS, WINS,
and
> > >default gateway. There is a firewall, but it doesn't block 443 (BUT, I
> even
> > >swapped their IPs to give the "broken" machine the other "working"
> machine's
> > >IP, brought down the "working" machine, and it still failed).
> > >
> > >It's funny that the only site affected is microsoft.com. I've checked
> the
> > >Internet Connection settings, and there doesn't appear to be anything
> fishy.
> > >I cleared the SSL State cache, all temporary objects, but still no
luck.
> > >
> > >Any ideas on how I can get this connectivity back?
> >
>
>