Error Code: 80072ee2

I've been getting this error message for quite some time now when i try to
login at my workplace?

When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
gateway is offline. (which it isn't)

Any ideas as to what protocol/port needs to be enabled? It works fine at
home with my cable connection and soho router.

Greetings,

Messenger just pings the gateway. If it's unpingable (which is acceptable and still be
working), it will show up as one of the possible issues in the troubleshooter.

When Messenger fails on its own port, it goes back to HTTP mode. As such, if your web access
is working then so should Messenger. Is it possible that your workplace has blocked it from
functioning?

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2006 Jonathan Kay.
You *must* contact me for redistribution rights.
--

"SeanDatRRC" <> wrote in message
news:87F19447-AEA0-46CF-8412-...
> I've been getting this error message for quite some time now when i try to
> login at my workplace?
>
> When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
> gateway is offline. (which it isn't)
>
> Any ideas as to what protocol/port needs to be enabled? It works fine at
> home with my cable connection and soho router.
>

I don't think they are blocking it intentionally. I just called our resident
network analyst and he's getting calls from a lot of other employees and he
told me he's done a capture seeing a lot of requests on port 1863...kicks
out back to port 80 and nothing. This whole thing he figures started when
Microsoft released a security patch through Windows Update for MSN back
during the summer sometime.


"Jonathan Kay [MVP]" wrote:

> Greetings,
>
> Messenger just pings the gateway. If it's unpingable (which is acceptable and still be
> working), it will show up as one of the possible issues in the troubleshooter.
>
> When Messenger fails on its own port, it goes back to HTTP mode. As such, if your web access
> is working then so should Messenger. Is it possible that your workplace has blocked it from
> functioning?
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
> You *must* contact me for redistribution rights.
> --
>
> "SeanDatRRC" <> wrote in message
> news:87F19447-AEA0-46CF-8412-...
> > I've been getting this error message for quite some time now when i try to
> > login at my workplace?
> >
> > When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
> > gateway is offline. (which it isn't)
> >
> > Any ideas as to what protocol/port needs to be enabled? It works fine at
> > home with my cable connection and soho router.
> >
>
>
>

Hi,

That is exactly what Messenger tries. Regardless, there is no widespread outage on the
Messenger side to what you are describing so I'm sure they'll be able to sort it out on your
end.

He should however, be seeing (attempts to?) connections to port 443 (HTTPS) for Passport
authentication and will fail without it. You may want to pass that along for their info.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2006 Jonathan Kay.
You *must* contact me for redistribution rights.
--

"SeanDatRRC" <> wrote in message
news:62654DF8-2EC7-43F4-A334-...
>I don't think they are blocking it intentionally. I just called our resident
> network analyst and he's getting calls from a lot of other employees and he
> told me he's done a capture seeing a lot of requests on port 1863...kicks
> out back to port 80 and nothing. This whole thing he figures started when
> Microsoft released a security patch through Windows Update for MSN back
> during the summer sometime.
>
>
> "Jonathan Kay [MVP]" wrote:
>
>> Greetings,
>>
>> Messenger just pings the gateway. If it's unpingable (which is acceptable and still be
>> working), it will show up as one of the possible issues in the troubleshooter.
>>
>> When Messenger fails on its own port, it goes back to HTTP mode. As such, if your web
>> access
>> is working then so should Messenger. Is it possible that your workplace has blocked it
>> from
>> functioning?
>>
>> --
>> Jonathan Kay
>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
>> Associate Expert
>> http://www.microsoft.com/windowsxp/expertzone/
>> Messenger Resources - http://messenger.jonathankay.com
>> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>> --
>>
>> "SeanDatRRC" <> wrote in message
>> news:87F19447-AEA0-46CF-8412-...
>> > I've been getting this error message for quite some time now when i try to
>> > login at my workplace?
>> >
>> > When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
>> > gateway is offline. (which it isn't)
>> >
>> > Any ideas as to what protocol/port needs to be enabled? It works fine at
>> > home with my cable connection and soho router.
>> >
>>
>>
>>

We've figured it out. Port 1863 was blocked. SSL authentication worked on
port 443, but when Messenger tried to establish a link on 1863, it failed.
Opening the firewall on 1863 fixed the problem here.
Is this a new port as compared to previous versions of messenger?

"Jonathan Kay [MVP]" wrote:

> Hi,
>
> That is exactly what Messenger tries. Regardless, there is no widespread outage on the
> Messenger side to what you are describing so I'm sure they'll be able to sort it out on your
> end.
>
> He should however, be seeing (attempts to?) connections to port 443 (HTTPS) for Passport
> authentication and will fail without it. You may want to pass that along for their info.
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
> You *must* contact me for redistribution rights.
> --
>
> "SeanDatRRC" <> wrote in message
> news:62654DF8-2EC7-43F4-A334-...
> >I don't think they are blocking it intentionally. I just called our resident
> > network analyst and he's getting calls from a lot of other employees and he
> > told me he's done a capture seeing a lot of requests on port 1863...kicks
> > out back to port 80 and nothing. This whole thing he figures started when
> > Microsoft released a security patch through Windows Update for MSN back
> > during the summer sometime.
> >
> >
> > "Jonathan Kay [MVP]" wrote:
> >
> >> Greetings,
> >>
> >> Messenger just pings the gateway. If it's unpingable (which is acceptable and still be
> >> working), it will show up as one of the possible issues in the troubleshooter.
> >>
> >> When Messenger fails on its own port, it goes back to HTTP mode. As such, if your web
> >> access
> >> is working then so should Messenger. Is it possible that your workplace has blocked it
> >> from
> >> functioning?
> >>
> >> --
> >> Jonathan Kay
> >> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> >> Associate Expert
> >> http://www.microsoft.com/windowsxp/expertzone/
> >> Messenger Resources - http://messenger.jonathankay.com
> >> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
> >> You *must* contact me for redistribution rights.
> >> --
> >>
> >> "SeanDatRRC" <> wrote in message
> >> news:87F19447-AEA0-46CF-8412-...
> >> > I've been getting this error message for quite some time now when i try to
> >> > login at my workplace?
> >> >
> >> > When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
> >> > gateway is offline. (which it isn't)
> >> >
> >> > Any ideas as to what protocol/port needs to be enabled? It works fine at
> >> > home with my cable connection and soho router.
> >> >
> >>
> >>
> >>
>
>
>

Hi,

Nope, Messenger has used this port since day one.

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2006 Jonathan Kay.
You *must* contact me for redistribution rights.
--

"SeanDatRRC" <> wrote in message
news:25A239FC-E70A-4BF9-99C7-...
> We've figured it out. Port 1863 was blocked. SSL authentication worked on
> port 443, but when Messenger tried to establish a link on 1863, it failed.
> Opening the firewall on 1863 fixed the problem here.
> Is this a new port as compared to previous versions of messenger?
>
> "Jonathan Kay [MVP]" wrote:
>
>> Hi,
>>
>> That is exactly what Messenger tries. Regardless, there is no widespread outage on the
>> Messenger side to what you are describing so I'm sure they'll be able to sort it out on
>> your
>> end.
>>
>> He should however, be seeing (attempts to?) connections to port 443 (HTTPS) for Passport
>> authentication and will fail without it. You may want to pass that along for their info.
>>
>> --
>> Jonathan Kay
>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
>> Associate Expert
>> http://www.microsoft.com/windowsxp/expertzone/
>> Messenger Resources - http://messenger.jonathankay.com
>> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>> --
>>
>> "SeanDatRRC" <> wrote in message
>> news:62654DF8-2EC7-43F4-A334-...
>> >I don't think they are blocking it intentionally. I just called our resident
>> > network analyst and he's getting calls from a lot of other employees and he
>> > told me he's done a capture seeing a lot of requests on port 1863...kicks
>> > out back to port 80 and nothing. This whole thing he figures started when
>> > Microsoft released a security patch through Windows Update for MSN back
>> > during the summer sometime.
>> >
>> >
>> > "Jonathan Kay [MVP]" wrote:
>> >
>> >> Greetings,
>> >>
>> >> Messenger just pings the gateway. If it's unpingable (which is acceptable and still be
>> >> working), it will show up as one of the possible issues in the troubleshooter.
>> >>
>> >> When Messenger fails on its own port, it goes back to HTTP mode. As such, if your web
>> >> access
>> >> is working then so should Messenger. Is it possible that your workplace has blocked it
>> >> from
>> >> functioning?
>> >>
>> >> --
>> >> Jonathan Kay
>> >> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
>> >> Associate Expert
>> >> http://www.microsoft.com/windowsxp/expertzone/
>> >> Messenger Resources - http://messenger.jonathankay.com
>> >> All posts unless otherwise specified are (c) 2006 Jonathan Kay.
>> >> You *must* contact me for redistribution rights.
>> >> --
>> >>
>> >> "SeanDatRRC" <> wrote in message
>> >> news:87F19447-AEA0-46CF-8412-...
>> >> > I've been getting this error message for quite some time now when i try to
>> >> > login at my workplace?
>> >> >
>> >> > When I click the 'Troubleshoot' button, it stops on the 2nd test saying my
>> >> > gateway is offline. (which it isn't)
>> >> >
>> >> > Any ideas as to what protocol/port needs to be enabled? It works fine at
>> >> > home with my cable connection and soho router.
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>