Unfortunatly MSN has become critical for my work and i
reeeeeeeally need this problem solved..

Does anyone have suggestions to solve this?
I'm behind a firewall that i have no access to.. but i
know no configurations have been changed since the last
time i logged in to MSN..

Note: I did access my account at home before coming to
work.. but here (at work) i've been getting the same
error-code over and over again..

Note2: I can access my hotmail account through the
website here..

Is there something I can do to keep using messenger or is
this a microsoft-only answer ??

Thanks in advance..

Any suggestions 2 solve 0x81000306 ?? by Ryan

Ryan
Mon Jul 05 09:28:59 CDT 2004

Just to make sure you see the reply.... Try using Hopster
to by-pass your proxy. Worked for me. Just search google
for hopster. It's a free app.

good luck!

>-----Original Message-----
>Unfortunatly MSN has become critical for my work and i
>reeeeeeeally need this problem solved..
>
>Does anyone have suggestions to solve this?
>I'm behind a firewall that i have no access to.. but i
>know no configurations have been changed since the last
>time i logged in to MSN..
>
> Note: I did access my account at home before coming to
>work.. but here (at work) i've been getting the same
>error-code over and over again..
>
> Note2: I can access my hotmail account through the
>website here..
>
>Is there something I can do to keep using messenger or is
>this a microsoft-only answer ??
>
>Thanks in advance..
>.
>

Any suggestions 2 solve 0x81000306 ?? by anonymous

anonymous
Mon Jul 05 11:00:21 CDT 2004

I don't wanna risk using that kind of SW cause i work for
a big institutional company so.... just can't afford the
risk.. I guess there's no other way to go round this
problem while Micro$oft doesn't work it out.. is there?

..installing prior versions?
..changing my computer's network settings?

BTW: i'm pretty closed up to the outside cause every
communication has to go through the proxy.. but i know
nothing has changed (in the proxy config.) since the last
time i logged successefuly..

thanks

>-----Original Message-----
>Just to make sure you see the reply.... Try using
Hopster
>to by-pass your proxy. Worked for me. Just search google
>for hopster. It's a free app.
>
>good luck!
>
>>-----Original Message-----
>>Unfortunatly MSN has become critical for my work and i
>>reeeeeeeally need this problem solved..
>>
>>Does anyone have suggestions to solve this?
>>I'm behind a firewall that i have no access to.. but i
>>know no configurations have been changed since the last
>>time i logged in to MSN..
>>
>> Note: I did access my account at home before coming
to
>>work.. but here (at work) i've been getting the same
>>error-code over and over again..
>>
>> Note2: I can access my hotmail account through the
>>website here..
>>
>>Is there something I can do to keep using messenger or
is
>>this a microsoft-only answer ??
>>
>>Thanks in advance..
>>.
>>
>.
>

Any suggestions 2 solve 0x81000306 ?? by anonymous

anonymous
Mon Jul 05 11:49:28 CDT 2004

Well, as long as you don't abuse it (like by running
kazzaa etc...) I don't really see the problem, unless of
course your company "wants" to block access to MSN. The
only other thing I can suggest is to ask around the office
and see if other people are able to connect. If so, then
copy their settings.

Re: Any suggestions 2 solve 0x81000306 ?? by Corey

Corey
Mon Jul 05 12:05:15 CDT 2004

certain msns are down everywhere, the problem may be the with the service
itself, and not you...it's been down since friday night for me, and msn just
keeps telling me it'll be fixed eventually...


<anonymous@discussions.microsoft.com> wrote in message
news:261fa01c462b0$0951d2e0$a601280a@phx.gbl...
> Well, as long as you don't abuse it (like by running
> kazzaa etc...) I don't really see the problem, unless of
> course your company "wants" to block access to MSN. The
> only other thing I can suggest is to ask around the office
> and see if other people are able to connect. If so, then
> copy their settings.



Re: Any suggestions 2 solve 0x81000306 ?? by N

N
Mon Jul 05 13:51:25 CDT 2004

In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz says...

> Unfortunatly MSN has become critical for my work and i
> reeeeeeeally need this problem solved..

Have you requested the assistance of your employer's IT staff? If this is
critical to your job they should be able to get things running for you in
short order.

> Does anyone have suggestions to solve this?
> I'm behind a firewall that i have no access to.. but i
> know no configurations have been changed since the last
> time i logged in to MSN..

Any suggestions that I could offer require access to the firewall. Bug your
boss, bug the IT staff.

> Note: I did access my account at home before coming to
> work.. but here (at work) i've been getting the same
> error-code over and over again..

So, it works.

> Note2: I can access my hotmail account through the
> website here..

But Hotmail only works over port 80, MSN Messenger requires a bunch of
different ports, depending upon whether it is traversing a UPnP NAT, a
proxy, or whatever.

> Is there something I can do to keep using messenger or is
> this a microsoft-only answer ??

Without access to your system to see the symptoms, it can be difficult. I
ran into two separate firewall issues last night when I finally bit the
bullet and moved up to MSN Messenger 6.2 from 5.0.

I am using Kerio Personal Firewall, and these are the rules I have
configured for MSN Messenger 6.2:

___________________________________________________________

Descriptions: Messenger - UPnP Both

Protocol: UDP
Direction: Both directions

Local endpoint ============================================

Port type: Port/Range Application:
First port number: 1024 c:%path%msnmsger.exe
Last port number: 65535

Remote endpoint ===========================================

Address type: Network/Mask Port type: Single port

Network Address: 192.168.x.x Port number: 1900
Network Mask: 255.255.255.0

Rule valid ================================================

Always

Action ====================================================

(#) Permit [ ] Log when this rule matches
( ) Deny [ ] Disply alert box when this rule matches

___________________________________________________________

Descriptions: Messenger - Router HTTP

Protocol: TCP
Direction: Outgoing

Local endpoint ============================================

Port type: Port/Range Application:
First port number: 1024 c:%path%msnmsger.exe
Last port number: 65535

Remote endpoint ===========================================

Address type: Single address Port type: Single port

Host Address: 192.168.x.x Port number: 80

Rule valid ================================================

Always

Action ====================================================

(#) Permit [ ] Log when this rule matches
( ) Deny [ ] Disply alert box when this rule matches

___________________________________________________________

Descriptions: Messenger - Discard & Callback

Protocol: UDP
Direction: Both directions

Local endpoint ============================================

Port type: Port/Range Application:
First port number: 1024 c:%path%msnmsger.exe
Last port number: 5000

Remote endpoint ===========================================

Address type: Network/Range Port type: List of ports

First Address: 64.4.12.200 List of Ports: 9,7001
Last Address: 64.4.12.201

Rule valid ================================================

Always

Action ====================================================

(#) Permit [ ] Log when this rule matches
( ) Deny [ ] Disply alert box when this rule matches

___________________________________________________________

Descriptions: Messenger - TSL/SSL

Protocol: TCP
Direction: Outgoing

Local endpoint ============================================

Port type: Port/Range Application:
First port number: 1024 c:%path%msnmsger.exe
Last port number: 5000

Remote endpoint ===========================================

Address type: Network/Range Port type: Single port

First Address: 65.54.179.192 Port number: 443
Last Address: 65.54.231.248

Rule valid ================================================

Always

Action ====================================================

(#) Permit [ ] Log when this rule matches
( ) Deny [ ] Disply alert box when this rule matches

___________________________________________________________

Descriptions: Messenger - Auth & Msgs

Protocol: TCP
Direction: Outgoing

Local endpoint ============================================

Port type: Port/Range Application:
First port number: 1024 c:%path%msnmsger.exe
Last port number: 5000

Remote endpoint ===========================================

Address type: Network/Mask Port type: Single port

First Address: 207.46.0.0 Port number: 1863
Last Address: 255.255.0.0

Rule valid ================================================

Always

Action ====================================================

(#) Permit [ ] Log when this rule matches
( ) Deny [ ] Disply alert box when this rule matches

___________________________________________________________


--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

Re: Any suggestions 2 solve 0x81000306 ?? by Corey

Corey
Mon Jul 05 13:53:50 CDT 2004

it appears to be the same thing happening to me...if u click on the help box
when the error comes up, you will notice that msn is experiencing technical
difficulties that may prevent you from signing in...this could be your
problem, so instead of bugging your IT, maybe bugging msn would be a better
bet


"N. Miller" <duh@blackhole.aosake.net> wrote in message
news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz says...
>
> > Unfortunatly MSN has become critical for my work and i
> > reeeeeeeally need this problem solved..
>
> Have you requested the assistance of your employer's IT staff? If this is
> critical to your job they should be able to get things running for you in
> short order.
>
> > Does anyone have suggestions to solve this?
> > I'm behind a firewall that i have no access to.. but i
> > know no configurations have been changed since the last
> > time i logged in to MSN..
>
> Any suggestions that I could offer require access to the firewall. Bug
your
> boss, bug the IT staff.
>
> > Note: I did access my account at home before coming to
> > work.. but here (at work) i've been getting the same
> > error-code over and over again..
>
> So, it works.
>
> > Note2: I can access my hotmail account through the
> > website here..
>
> But Hotmail only works over port 80, MSN Messenger requires a bunch of
> different ports, depending upon whether it is traversing a UPnP NAT, a
> proxy, or whatever.
>
> > Is there something I can do to keep using messenger or is
> > this a microsoft-only answer ??
>
> Without access to your system to see the symptoms, it can be difficult. I
> ran into two separate firewall issues last night when I finally bit the
> bullet and moved up to MSN Messenger 6.2 from 5.0.
>
> I am using Kerio Personal Firewall, and these are the rules I have
> configured for MSN Messenger 6.2:
>
> ___________________________________________________________
>
> Descriptions: Messenger - UPnP Both
>
> Protocol: UDP
> Direction: Both directions
>
> Local endpoint ============================================
>
> Port type: Port/Range Application:
> First port number: 1024 c:%path%msnmsger.exe
> Last port number: 65535
>
> Remote endpoint ===========================================
>
> Address type: Network/Mask Port type: Single port
>
> Network Address: 192.168.x.x Port number: 1900
> Network Mask: 255.255.255.0
>
> Rule valid ================================================
>
> Always
>
> Action ====================================================
>
> (#) Permit [ ] Log when this rule matches
> ( ) Deny [ ] Disply alert box when this rule matches
>
> ___________________________________________________________
>
> Descriptions: Messenger - Router HTTP
>
> Protocol: TCP
> Direction: Outgoing
>
> Local endpoint ============================================
>
> Port type: Port/Range Application:
> First port number: 1024 c:%path%msnmsger.exe
> Last port number: 65535
>
> Remote endpoint ===========================================
>
> Address type: Single address Port type: Single port
>
> Host Address: 192.168.x.x Port number: 80
>
> Rule valid ================================================
>
> Always
>
> Action ====================================================
>
> (#) Permit [ ] Log when this rule matches
> ( ) Deny [ ] Disply alert box when this rule matches
>
> ___________________________________________________________
>
> Descriptions: Messenger - Discard & Callback
>
> Protocol: UDP
> Direction: Both directions
>
> Local endpoint ============================================
>
> Port type: Port/Range Application:
> First port number: 1024 c:%path%msnmsger.exe
> Last port number: 5000
>
> Remote endpoint ===========================================
>
> Address type: Network/Range Port type: List of ports
>
> First Address: 64.4.12.200 List of Ports: 9,7001
> Last Address: 64.4.12.201
>
> Rule valid ================================================
>
> Always
>
> Action ====================================================
>
> (#) Permit [ ] Log when this rule matches
> ( ) Deny [ ] Disply alert box when this rule matches
>
> ___________________________________________________________
>
> Descriptions: Messenger - TSL/SSL
>
> Protocol: TCP
> Direction: Outgoing
>
> Local endpoint ============================================
>
> Port type: Port/Range Application:
> First port number: 1024 c:%path%msnmsger.exe
> Last port number: 5000
>
> Remote endpoint ===========================================
>
> Address type: Network/Range Port type: Single port
>
> First Address: 65.54.179.192 Port number: 443
> Last Address: 65.54.231.248
>
> Rule valid ================================================
>
> Always
>
> Action ====================================================
>
> (#) Permit [ ] Log when this rule matches
> ( ) Deny [ ] Disply alert box when this rule matches
>
> ___________________________________________________________
>
> Descriptions: Messenger - Auth & Msgs
>
> Protocol: TCP
> Direction: Outgoing
>
> Local endpoint ============================================
>
> Port type: Port/Range Application:
> First port number: 1024 c:%path%msnmsger.exe
> Last port number: 5000
>
> Remote endpoint ===========================================
>
> Address type: Network/Mask Port type: Single port
>
> First Address: 207.46.0.0 Port number: 1863
> Last Address: 255.255.0.0
>
> Rule valid ================================================
>
> Always
>
> Action ====================================================
>
> (#) Permit [ ] Log when this rule matches
> ( ) Deny [ ] Disply alert box when this rule matches
>
> ___________________________________________________________
>
>
> --
> Norman
> ~Win dain a lotica, En vai tu ri, Si lo ta
> ~Fin dein a loluca, En dragu a sei lain
> ~Vi fa-ru les shutai am, En riga-lint



Re: Any suggestions 2 solve 0x81000306 ?? by Jonathan

Jonathan
Mon Jul 05 14:01:15 CDT 2004

Hi,

MSN is working on the problem affecting a minority of users, depending on how they connect --
"bugging MSN" isn't going to get it fixed sooner.
____________________________________________
Jonathan Kay
Microsoft MVP - 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) 2004 Jonathan Kay.
You *must* contact me for redistribution rights.

"Corey Johnson" <cjohnson202@hotmail.com> wrote in message
news:euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl...
> it appears to be the same thing happening to me...if u click on the help box
> when the error comes up, you will notice that msn is experiencing technical
> difficulties that may prevent you from signing in...this could be your
> problem, so instead of bugging your IT, maybe bugging msn would be a better
> bet
>
>
> "N. Miller" <duh@blackhole.aosake.net> wrote in message
> news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
>> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz says...
>>
>> > Unfortunatly MSN has become critical for my work and i
>> > reeeeeeeally need this problem solved..
>>
>> Have you requested the assistance of your employer's IT staff? If this is
>> critical to your job they should be able to get things running for you in
>> short order.
>>
>> > Does anyone have suggestions to solve this?
>> > I'm behind a firewall that i have no access to.. but i
>> > know no configurations have been changed since the last
>> > time i logged in to MSN..
>>
>> Any suggestions that I could offer require access to the firewall. Bug
> your
>> boss, bug the IT staff.
>>
>> > Note: I did access my account at home before coming to
>> > work.. but here (at work) i've been getting the same
>> > error-code over and over again..
>>
>> So, it works.
>>
>> > Note2: I can access my hotmail account through the
>> > website here..
>>
>> But Hotmail only works over port 80, MSN Messenger requires a bunch of
>> different ports, depending upon whether it is traversing a UPnP NAT, a
>> proxy, or whatever.
>>
>> > Is there something I can do to keep using messenger or is
>> > this a microsoft-only answer ??
>>
>> Without access to your system to see the symptoms, it can be difficult. I
>> ran into two separate firewall issues last night when I finally bit the
>> bullet and moved up to MSN Messenger 6.2 from 5.0.
>>
>> I am using Kerio Personal Firewall, and these are the rules I have
>> configured for MSN Messenger 6.2:
>>
>> ___________________________________________________________
>>
>> Descriptions: Messenger - UPnP Both
>>
>> Protocol: UDP
>> Direction: Both directions
>>
>> Local endpoint ============================================
>>
>> Port type: Port/Range Application:
>> First port number: 1024 c:%path%msnmsger.exe
>> Last port number: 65535
>>
>> Remote endpoint ===========================================
>>
>> Address type: Network/Mask Port type: Single port
>>
>> Network Address: 192.168.x.x Port number: 1900
>> Network Mask: 255.255.255.0
>>
>> Rule valid ================================================
>>
>> Always
>>
>> Action ====================================================
>>
>> (#) Permit [ ] Log when this rule matches
>> ( ) Deny [ ] Disply alert box when this rule matches
>>
>> ___________________________________________________________
>>
>> Descriptions: Messenger - Router HTTP
>>
>> Protocol: TCP
>> Direction: Outgoing
>>
>> Local endpoint ============================================
>>
>> Port type: Port/Range Application:
>> First port number: 1024 c:%path%msnmsger.exe
>> Last port number: 65535
>>
>> Remote endpoint ===========================================
>>
>> Address type: Single address Port type: Single port
>>
>> Host Address: 192.168.x.x Port number: 80
>>
>> Rule valid ================================================
>>
>> Always
>>
>> Action ====================================================
>>
>> (#) Permit [ ] Log when this rule matches
>> ( ) Deny [ ] Disply alert box when this rule matches
>>
>> ___________________________________________________________
>>
>> Descriptions: Messenger - Discard & Callback
>>
>> Protocol: UDP
>> Direction: Both directions
>>
>> Local endpoint ============================================
>>
>> Port type: Port/Range Application:
>> First port number: 1024 c:%path%msnmsger.exe
>> Last port number: 5000
>>
>> Remote endpoint ===========================================
>>
>> Address type: Network/Range Port type: List of ports
>>
>> First Address: 64.4.12.200 List of Ports: 9,7001
>> Last Address: 64.4.12.201
>>
>> Rule valid ================================================
>>
>> Always
>>
>> Action ====================================================
>>
>> (#) Permit [ ] Log when this rule matches
>> ( ) Deny [ ] Disply alert box when this rule matches
>>
>> ___________________________________________________________
>>
>> Descriptions: Messenger - TSL/SSL
>>
>> Protocol: TCP
>> Direction: Outgoing
>>
>> Local endpoint ============================================
>>
>> Port type: Port/Range Application:
>> First port number: 1024 c:%path%msnmsger.exe
>> Last port number: 5000
>>
>> Remote endpoint ===========================================
>>
>> Address type: Network/Range Port type: Single port
>>
>> First Address: 65.54.179.192 Port number: 443
>> Last Address: 65.54.231.248
>>
>> Rule valid ================================================
>>
>> Always
>>
>> Action ====================================================
>>
>> (#) Permit [ ] Log when this rule matches
>> ( ) Deny [ ] Disply alert box when this rule matches
>>
>> ___________________________________________________________
>>
>> Descriptions: Messenger - Auth & Msgs
>>
>> Protocol: TCP
>> Direction: Outgoing
>>
>> Local endpoint ============================================
>>
>> Port type: Port/Range Application:
>> First port number: 1024 c:%path%msnmsger.exe
>> Last port number: 5000
>>
>> Remote endpoint ===========================================
>>
>> Address type: Network/Mask Port type: Single port
>>
>> First Address: 207.46.0.0 Port number: 1863
>> Last Address: 255.255.0.0
>>
>> Rule valid ================================================
>>
>> Always
>>
>> Action ====================================================
>>
>> (#) Permit [ ] Log when this rule matches
>> ( ) Deny [ ] Disply alert box when this rule matches
>>
>> ___________________________________________________________
>>
>>
>> --
>> Norman
>> ~Win dain a lotica, En vai tu ri, Si lo ta
>> ~Fin dein a loluca, En dragu a sei lain
>> ~Vi fa-ru les shutai am, En riga-lint
>
>



Re: Any suggestions 2 solve 0x81000306 ?? by Jonathan

Jonathan
Mon Jul 05 14:02:31 CDT 2004

Greetings Nuno,

There are some minor difficulties with the Messenger service currently that will be
preventing a small minority of users from signing in.

If you are part of this minority, you may find it more handy to use a web-based Messenger
client for the time being:
http://www.wbmsn.net
http://www.e-messenger.net
http://www.msn2go.com
http://www.msn2web.com

Also, a number of software firewalls and proxies may be forcing you to connect using the
method that is currently not functioning. If this is the case, make sure that your software
firewall has given Messenger full access to the Internet connection and if you've forced
Messenger to use a proxy, try turning it off (this will only work of course, if you can
connect without a proxy). To turn off the proxy setting, open up the main Messenger window,
click the Tools menu, then Options, then Connection tab, uncheck "I use a proxy server" and
then click OK.
____________________________________________
Jonathan Kay
Microsoft MVP - 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) 2004 Jonathan Kay.
You *must* contact me for redistribution rights.


"Nuno Cruz" <anonymous@discussions.microsoft.com> wrote in message
news:270fb01c46282$cf5d3840$a301280a@phx.gbl...
> Unfortunatly MSN has become critical for my work and i
> reeeeeeeally need this problem solved..
>
> Does anyone have suggestions to solve this?
> I'm behind a firewall that i have no access to.. but i
> know no configurations have been changed since the last
> time i logged in to MSN..
>
> Note: I did access my account at home before coming to
> work.. but here (at work) i've been getting the same
> error-code over and over again..
>
> Note2: I can access my hotmail account through the
> website here..
>
> Is there something I can do to keep using messenger or is
> this a microsoft-only answer ??
>
> Thanks in advance..



Re: Any suggestions 2 solve 0x81000306 ?? by Corey

Corey
Mon Jul 05 14:06:31 CDT 2004

i know, I was just saying that the problem may not be with the IT department
at all


"Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
news:OWru0JsYEHA.3128@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> MSN is working on the problem affecting a minority of users, depending on
how they connect --
> "bugging MSN" isn't going to get it fixed sooner.
> ____________________________________________
> Jonathan Kay
> Microsoft MVP - 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) 2004 Jonathan Kay.
> You *must* contact me for redistribution rights.
>
> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
> news:euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl...
> > it appears to be the same thing happening to me...if u click on the help
box
> > when the error comes up, you will notice that msn is experiencing
technical
> > difficulties that may prevent you from signing in...this could be your
> > problem, so instead of bugging your IT, maybe bugging msn would be a
better
> > bet
> >
> >
> > "N. Miller" <duh@blackhole.aosake.net> wrote in message
> > news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
> >> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz says...
> >>
> >> > Unfortunatly MSN has become critical for my work and i
> >> > reeeeeeeally need this problem solved..
> >>
> >> Have you requested the assistance of your employer's IT staff? If this
is
> >> critical to your job they should be able to get things running for you
in
> >> short order.
> >>
> >> > Does anyone have suggestions to solve this?
> >> > I'm behind a firewall that i have no access to.. but i
> >> > know no configurations have been changed since the last
> >> > time i logged in to MSN..
> >>
> >> Any suggestions that I could offer require access to the firewall. Bug
> > your
> >> boss, bug the IT staff.
> >>
> >> > Note: I did access my account at home before coming to
> >> > work.. but here (at work) i've been getting the same
> >> > error-code over and over again..
> >>
> >> So, it works.
> >>
> >> > Note2: I can access my hotmail account through the
> >> > website here..
> >>
> >> But Hotmail only works over port 80, MSN Messenger requires a bunch of
> >> different ports, depending upon whether it is traversing a UPnP NAT, a
> >> proxy, or whatever.
> >>
> >> > Is there something I can do to keep using messenger or is
> >> > this a microsoft-only answer ??
> >>
> >> Without access to your system to see the symptoms, it can be difficult.
I
> >> ran into two separate firewall issues last night when I finally bit the
> >> bullet and moved up to MSN Messenger 6.2 from 5.0.
> >>
> >> I am using Kerio Personal Firewall, and these are the rules I have
> >> configured for MSN Messenger 6.2:
> >>
> >> ___________________________________________________________
> >>
> >> Descriptions: Messenger - UPnP Both
> >>
> >> Protocol: UDP
> >> Direction: Both directions
> >>
> >> Local endpoint ============================================
> >>
> >> Port type: Port/Range Application:
> >> First port number: 1024 c:%path%msnmsger.exe
> >> Last port number: 65535
> >>
> >> Remote endpoint ===========================================
> >>
> >> Address type: Network/Mask Port type: Single port
> >>
> >> Network Address: 192.168.x.x Port number: 1900
> >> Network Mask: 255.255.255.0
> >>
> >> Rule valid ================================================
> >>
> >> Always
> >>
> >> Action ====================================================
> >>
> >> (#) Permit [ ] Log when this rule matches
> >> ( ) Deny [ ] Disply alert box when this rule matches
> >>
> >> ___________________________________________________________
> >>
> >> Descriptions: Messenger - Router HTTP
> >>
> >> Protocol: TCP
> >> Direction: Outgoing
> >>
> >> Local endpoint ============================================
> >>
> >> Port type: Port/Range Application:
> >> First port number: 1024 c:%path%msnmsger.exe
> >> Last port number: 65535
> >>
> >> Remote endpoint ===========================================
> >>
> >> Address type: Single address Port type: Single port
> >>
> >> Host Address: 192.168.x.x Port number: 80
> >>
> >> Rule valid ================================================
> >>
> >> Always
> >>
> >> Action ====================================================
> >>
> >> (#) Permit [ ] Log when this rule matches
> >> ( ) Deny [ ] Disply alert box when this rule matches
> >>
> >> ___________________________________________________________
> >>
> >> Descriptions: Messenger - Discard & Callback
> >>
> >> Protocol: UDP
> >> Direction: Both directions
> >>
> >> Local endpoint ============================================
> >>
> >> Port type: Port/Range Application:
> >> First port number: 1024 c:%path%msnmsger.exe
> >> Last port number: 5000
> >>
> >> Remote endpoint ===========================================
> >>
> >> Address type: Network/Range Port type: List of ports
> >>
> >> First Address: 64.4.12.200 List of Ports: 9,7001
> >> Last Address: 64.4.12.201
> >>
> >> Rule valid ================================================
> >>
> >> Always
> >>
> >> Action ====================================================
> >>
> >> (#) Permit [ ] Log when this rule matches
> >> ( ) Deny [ ] Disply alert box when this rule matches
> >>
> >> ___________________________________________________________
> >>
> >> Descriptions: Messenger - TSL/SSL
> >>
> >> Protocol: TCP
> >> Direction: Outgoing
> >>
> >> Local endpoint ============================================
> >>
> >> Port type: Port/Range Application:
> >> First port number: 1024 c:%path%msnmsger.exe
> >> Last port number: 5000
> >>
> >> Remote endpoint ===========================================
> >>
> >> Address type: Network/Range Port type: Single port
> >>
> >> First Address: 65.54.179.192 Port number: 443
> >> Last Address: 65.54.231.248
> >>
> >> Rule valid ================================================
> >>
> >> Always
> >>
> >> Action ====================================================
> >>
> >> (#) Permit [ ] Log when this rule matches
> >> ( ) Deny [ ] Disply alert box when this rule matches
> >>
> >> ___________________________________________________________
> >>
> >> Descriptions: Messenger - Auth & Msgs
> >>
> >> Protocol: TCP
> >> Direction: Outgoing
> >>
> >> Local endpoint ============================================
> >>
> >> Port type: Port/Range Application:
> >> First port number: 1024 c:%path%msnmsger.exe
> >> Last port number: 5000
> >>
> >> Remote endpoint ===========================================
> >>
> >> Address type: Network/Mask Port type: Single port
> >>
> >> First Address: 207.46.0.0 Port number: 1863
> >> Last Address: 255.255.0.0
> >>
> >> Rule valid ================================================
> >>
> >> Always
> >>
> >> Action ====================================================
> >>
> >> (#) Permit [ ] Log when this rule matches
> >> ( ) Deny [ ] Disply alert box when this rule matches
> >>
> >> ___________________________________________________________
> >>
> >>
> >> --
> >> Norman
> >> ~Win dain a lotica, En vai tu ri, Si lo ta
> >> ~Fin dein a loluca, En dragu a sei lain
> >> ~Vi fa-ru les shutai am, En riga-lint
> >
> >
>
>



Re: Any suggestions 2 solve 0x81000306 ?? by Jonathan

Jonathan
Mon Jul 05 14:14:15 CDT 2004

Hi Corey,

Yeah I know; let's just say I woke up to a rather full inbox this morning =)
____________________________________________
Jonathan Kay
Microsoft MVP - 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) 2004 Jonathan Kay.
You *must* contact me for redistribution rights.

"Corey Johnson" <cjohnson202@hotmail.com> wrote in message
news:%23klGvMsYEHA.3664@TK2MSFTNGP12.phx.gbl...
>i know, I was just saying that the problem may not be with the IT department
> at all
>
>
> "Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
> news:OWru0JsYEHA.3128@TK2MSFTNGP09.phx.gbl...
>> Hi,
>>
>> MSN is working on the problem affecting a minority of users, depending on
> how they connect --
>> "bugging MSN" isn't going to get it fixed sooner.
>> ____________________________________________
>> Jonathan Kay
>> Microsoft MVP - 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) 2004 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>>
>> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
>> news:euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl...
>> > it appears to be the same thing happening to me...if u click on the help
> box
>> > when the error comes up, you will notice that msn is experiencing
> technical
>> > difficulties that may prevent you from signing in...this could be your
>> > problem, so instead of bugging your IT, maybe bugging msn would be a
> better
>> > bet
>> >
>> >
>> > "N. Miller" <duh@blackhole.aosake.net> wrote in message
>> > news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
>> >> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz says...
>> >>
>> >> > Unfortunatly MSN has become critical for my work and i
>> >> > reeeeeeeally need this problem solved..
>> >>
>> >> Have you requested the assistance of your employer's IT staff? If this
> is
>> >> critical to your job they should be able to get things running for you
> in
>> >> short order.
>> >>
>> >> > Does anyone have suggestions to solve this?
>> >> > I'm behind a firewall that i have no access to.. but i
>> >> > know no configurations have been changed since the last
>> >> > time i logged in to MSN..
>> >>
>> >> Any suggestions that I could offer require access to the firewall. Bug
>> > your
>> >> boss, bug the IT staff.
>> >>
>> >> > Note: I did access my account at home before coming to
>> >> > work.. but here (at work) i've been getting the same
>> >> > error-code over and over again..
>> >>
>> >> So, it works.
>> >>
>> >> > Note2: I can access my hotmail account through the
>> >> > website here..
>> >>
>> >> But Hotmail only works over port 80, MSN Messenger requires a bunch of
>> >> different ports, depending upon whether it is traversing a UPnP NAT, a
>> >> proxy, or whatever.
>> >>
>> >> > Is there something I can do to keep using messenger or is
>> >> > this a microsoft-only answer ??
>> >>
>> >> Without access to your system to see the symptoms, it can be difficult.
> I
>> >> ran into two separate firewall issues last night when I finally bit the
>> >> bullet and moved up to MSN Messenger 6.2 from 5.0.
>> >>
>> >> I am using Kerio Personal Firewall, and these are the rules I have
>> >> configured for MSN Messenger 6.2:
>> >>
>> >> ___________________________________________________________
>> >>
>> >> Descriptions: Messenger - UPnP Both
>> >>
>> >> Protocol: UDP
>> >> Direction: Both directions
>> >>
>> >> Local endpoint ============================================
>> >>
>> >> Port type: Port/Range Application:
>> >> First port number: 1024 c:%path%msnmsger.exe
>> >> Last port number: 65535
>> >>
>> >> Remote endpoint ===========================================
>> >>
>> >> Address type: Network/Mask Port type: Single port
>> >>
>> >> Network Address: 192.168.x.x Port number: 1900
>> >> Network Mask: 255.255.255.0
>> >>
>> >> Rule valid ================================================
>> >>
>> >> Always
>> >>
>> >> Action ====================================================
>> >>
>> >> (#) Permit [ ] Log when this rule matches
>> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >>
>> >> ___________________________________________________________
>> >>
>> >> Descriptions: Messenger - Router HTTP
>> >>
>> >> Protocol: TCP
>> >> Direction: Outgoing
>> >>
>> >> Local endpoint ============================================
>> >>
>> >> Port type: Port/Range Application:
>> >> First port number: 1024 c:%path%msnmsger.exe
>> >> Last port number: 65535
>> >>
>> >> Remote endpoint ===========================================
>> >>
>> >> Address type: Single address Port type: Single port
>> >>
>> >> Host Address: 192.168.x.x Port number: 80
>> >>
>> >> Rule valid ================================================
>> >>
>> >> Always
>> >>
>> >> Action ====================================================
>> >>
>> >> (#) Permit [ ] Log when this rule matches
>> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >>
>> >> ___________________________________________________________
>> >>
>> >> Descriptions: Messenger - Discard & Callback
>> >>
>> >> Protocol: UDP
>> >> Direction: Both directions
>> >>
>> >> Local endpoint ============================================
>> >>
>> >> Port type: Port/Range Application:
>> >> First port number: 1024 c:%path%msnmsger.exe
>> >> Last port number: 5000
>> >>
>> >> Remote endpoint ===========================================
>> >>
>> >> Address type: Network/Range Port type: List of ports
>> >>
>> >> First Address: 64.4.12.200 List of Ports: 9,7001
>> >> Last Address: 64.4.12.201
>> >>
>> >> Rule valid ================================================
>> >>
>> >> Always
>> >>
>> >> Action ====================================================
>> >>
>> >> (#) Permit [ ] Log when this rule matches
>> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >>
>> >> ___________________________________________________________
>> >>
>> >> Descriptions: Messenger - TSL/SSL
>> >>
>> >> Protocol: TCP
>> >> Direction: Outgoing
>> >>
>> >> Local endpoint ============================================
>> >>
>> >> Port type: Port/Range Application:
>> >> First port number: 1024 c:%path%msnmsger.exe
>> >> Last port number: 5000
>> >>
>> >> Remote endpoint ===========================================
>> >>
>> >> Address type: Network/Range Port type: Single port
>> >>
>> >> First Address: 65.54.179.192 Port number: 443
>> >> Last Address: 65.54.231.248
>> >>
>> >> Rule valid ================================================
>> >>
>> >> Always
>> >>
>> >> Action ====================================================
>> >>
>> >> (#) Permit [ ] Log when this rule matches
>> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >>
>> >> ___________________________________________________________
>> >>
>> >> Descriptions: Messenger - Auth & Msgs
>> >>
>> >> Protocol: TCP
>> >> Direction: Outgoing
>> >>
>> >> Local endpoint ============================================
>> >>
>> >> Port type: Port/Range Application:
>> >> First port number: 1024 c:%path%msnmsger.exe
>> >> Last port number: 5000
>> >>
>> >> Remote endpoint ===========================================
>> >>
>> >> Address type: Network/Mask Port type: Single port
>> >>
>> >> First Address: 207.46.0.0 Port number: 1863
>> >> Last Address: 255.255.0.0
>> >>
>> >> Rule valid ================================================
>> >>
>> >> Always
>> >>
>> >> Action ====================================================
>> >>
>> >> (#) Permit [ ] Log when this rule matches
>> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >>
>> >> ___________________________________________________________
>> >>
>> >>
>> >> --
>> >> Norman
>> >> ~Win dain a lotica, En vai tu ri, Si lo ta
>> >> ~Fin dein a loluca, En dragu a sei lain
>> >> ~Vi fa-ru les shutai am, En riga-lint
>> >
>> >
>>
>>
>
>



Re: Any suggestions 2 solve 0x81000306 ?? by Corey

Corey
Mon Jul 05 14:19:57 CDT 2004

i can imagine, meh, its summer, I guess a lot of people get cranky without
msn, it is kind of boring being home all day and nothing to do, especially
with the weather as crappy as it's been around here

"Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
news:OwYzFRsYEHA.2812@TK2MSFTNGP11.phx.gbl...
> Hi Corey,
>
> Yeah I know; let's just say I woke up to a rather full inbox this morning
=)
> ____________________________________________
> Jonathan Kay
> Microsoft MVP - 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) 2004 Jonathan Kay.
> You *must* contact me for redistribution rights.
>
> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
> news:%23klGvMsYEHA.3664@TK2MSFTNGP12.phx.gbl...
> >i know, I was just saying that the problem may not be with the IT
department
> > at all
> >
> >
> > "Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
> > news:OWru0JsYEHA.3128@TK2MSFTNGP09.phx.gbl...
> >> Hi,
> >>
> >> MSN is working on the problem affecting a minority of users, depending
on
> > how they connect --
> >> "bugging MSN" isn't going to get it fixed sooner.
> >> ____________________________________________
> >> Jonathan Kay
> >> Microsoft MVP - 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) 2004 Jonathan Kay.
> >> You *must* contact me for redistribution rights.
> >>
> >> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
> >> news:euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl...
> >> > it appears to be the same thing happening to me...if u click on the
help
> > box
> >> > when the error comes up, you will notice that msn is experiencing
> > technical
> >> > difficulties that may prevent you from signing in...this could be
your
> >> > problem, so instead of bugging your IT, maybe bugging msn would be a
> > better
> >> > bet
> >> >
> >> >
> >> > "N. Miller" <duh@blackhole.aosake.net> wrote in message
> >> > news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
> >> >> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz
says...
> >> >>
> >> >> > Unfortunatly MSN has become critical for my work and i
> >> >> > reeeeeeeally need this problem solved..
> >> >>
> >> >> Have you requested the assistance of your employer's IT staff? If
this
> > is
> >> >> critical to your job they should be able to get things running for
you
> > in
> >> >> short order.
> >> >>
> >> >> > Does anyone have suggestions to solve this?
> >> >> > I'm behind a firewall that i have no access to.. but i
> >> >> > know no configurations have been changed since the last
> >> >> > time i logged in to MSN..
> >> >>
> >> >> Any suggestions that I could offer require access to the firewall.
Bug
> >> > your
> >> >> boss, bug the IT staff.
> >> >>
> >> >> > Note: I did access my account at home before coming to
> >> >> > work.. but here (at work) i've been getting the same
> >> >> > error-code over and over again..
> >> >>
> >> >> So, it works.
> >> >>
> >> >> > Note2: I can access my hotmail account through the
> >> >> > website here..
> >> >>
> >> >> But Hotmail only works over port 80, MSN Messenger requires a bunch
of
> >> >> different ports, depending upon whether it is traversing a UPnP NAT,
a
> >> >> proxy, or whatever.
> >> >>
> >> >> > Is there something I can do to keep using messenger or is
> >> >> > this a microsoft-only answer ??
> >> >>
> >> >> Without access to your system to see the symptoms, it can be
difficult.
> > I
> >> >> ran into two separate firewall issues last night when I finally bit
the
> >> >> bullet and moved up to MSN Messenger 6.2 from 5.0.
> >> >>
> >> >> I am using Kerio Personal Firewall, and these are the rules I have
> >> >> configured for MSN Messenger 6.2:
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >> Descriptions: Messenger - UPnP Both
> >> >>
> >> >> Protocol: UDP
> >> >> Direction: Both directions
> >> >>
> >> >> Local endpoint ============================================
> >> >>
> >> >> Port type: Port/Range Application:
> >> >> First port number: 1024 c:%path%msnmsger.exe
> >> >> Last port number: 65535
> >> >>
> >> >> Remote endpoint ===========================================
> >> >>
> >> >> Address type: Network/Mask Port type: Single port
> >> >>
> >> >> Network Address: 192.168.x.x Port number: 1900
> >> >> Network Mask: 255.255.255.0
> >> >>
> >> >> Rule valid ================================================
> >> >>
> >> >> Always
> >> >>
> >> >> Action ====================================================
> >> >>
> >> >> (#) Permit [ ] Log when this rule matches
> >> >> ( ) Deny [ ] Disply alert box when this rule matches
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >> Descriptions: Messenger - Router HTTP
> >> >>
> >> >> Protocol: TCP
> >> >> Direction: Outgoing
> >> >>
> >> >> Local endpoint ============================================
> >> >>
> >> >> Port type: Port/Range Application:
> >> >> First port number: 1024 c:%path%msnmsger.exe
> >> >> Last port number: 65535
> >> >>
> >> >> Remote endpoint ===========================================
> >> >>
> >> >> Address type: Single address Port type: Single port
> >> >>
> >> >> Host Address: 192.168.x.x Port number: 80
> >> >>
> >> >> Rule valid ================================================
> >> >>
> >> >> Always
> >> >>
> >> >> Action ====================================================
> >> >>
> >> >> (#) Permit [ ] Log when this rule matches
> >> >> ( ) Deny [ ] Disply alert box when this rule matches
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >> Descriptions: Messenger - Discard & Callback
> >> >>
> >> >> Protocol: UDP
> >> >> Direction: Both directions
> >> >>
> >> >> Local endpoint ============================================
> >> >>
> >> >> Port type: Port/Range Application:
> >> >> First port number: 1024 c:%path%msnmsger.exe
> >> >> Last port number: 5000
> >> >>
> >> >> Remote endpoint ===========================================
> >> >>
> >> >> Address type: Network/Range Port type: List of ports
> >> >>
> >> >> First Address: 64.4.12.200 List of Ports: 9,7001
> >> >> Last Address: 64.4.12.201
> >> >>
> >> >> Rule valid ================================================
> >> >>
> >> >> Always
> >> >>
> >> >> Action ====================================================
> >> >>
> >> >> (#) Permit [ ] Log when this rule matches
> >> >> ( ) Deny [ ] Disply alert box when this rule matches
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >> Descriptions: Messenger - TSL/SSL
> >> >>
> >> >> Protocol: TCP
> >> >> Direction: Outgoing
> >> >>
> >> >> Local endpoint ============================================
> >> >>
> >> >> Port type: Port/Range Application:
> >> >> First port number: 1024 c:%path%msnmsger.exe
> >> >> Last port number: 5000
> >> >>
> >> >> Remote endpoint ===========================================
> >> >>
> >> >> Address type: Network/Range Port type: Single port
> >> >>
> >> >> First Address: 65.54.179.192 Port number: 443
> >> >> Last Address: 65.54.231.248
> >> >>
> >> >> Rule valid ================================================
> >> >>
> >> >> Always
> >> >>
> >> >> Action ====================================================
> >> >>
> >> >> (#) Permit [ ] Log when this rule matches
> >> >> ( ) Deny [ ] Disply alert box when this rule matches
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >> Descriptions: Messenger - Auth & Msgs
> >> >>
> >> >> Protocol: TCP
> >> >> Direction: Outgoing
> >> >>
> >> >> Local endpoint ============================================
> >> >>
> >> >> Port type: Port/Range Application:
> >> >> First port number: 1024 c:%path%msnmsger.exe
> >> >> Last port number: 5000
> >> >>
> >> >> Remote endpoint ===========================================
> >> >>
> >> >> Address type: Network/Mask Port type: Single port
> >> >>
> >> >> First Address: 207.46.0.0 Port number: 1863
> >> >> Last Address: 255.255.0.0
> >> >>
> >> >> Rule valid ================================================
> >> >>
> >> >> Always
> >> >>
> >> >> Action ====================================================
> >> >>
> >> >> (#) Permit [ ] Log when this rule matches
> >> >> ( ) Deny [ ] Disply alert box when this rule matches
> >> >>
> >> >> ___________________________________________________________
> >> >>
> >> >>
> >> >> --
> >> >> Norman
> >> >> ~Win dain a lotica, En vai tu ri, Si lo ta
> >> >> ~Fin dein a loluca, En dragu a sei lain
> >> >> ~Vi fa-ru les shutai am, En riga-lint
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Re: Any suggestions 2 solve 0x81000306 ?? by Jonathan

Jonathan
Mon Jul 05 14:48:26 CDT 2004

This is true, Saturday was nice however (assuming you aren't lying on your profile [17 year
old and married?], we're not that far away from each other).
____________________________________________
Jonathan Kay
Microsoft MVP - 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) 2004 Jonathan Kay.
You *must* contact me for redistribution rights.

"Corey Johnson" <cjohnson202@hotmail.com> wrote in message
news:O8XjPUsYEHA.3664@TK2MSFTNGP12.phx.gbl...
>i can imagine, meh, its summer, I guess a lot of people get cranky without
> msn, it is kind of boring being home all day and nothing to do, especially
> with the weather as crappy as it's been around here
>
> "Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
> news:OwYzFRsYEHA.2812@TK2MSFTNGP11.phx.gbl...
>> Hi Corey,
>>
>> Yeah I know; let's just say I woke up to a rather full inbox this morning
> =)
>> ____________________________________________
>> Jonathan Kay
>> Microsoft MVP - 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) 2004 Jonathan Kay.
>> You *must* contact me for redistribution rights.
>>
>> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
>> news:%23klGvMsYEHA.3664@TK2MSFTNGP12.phx.gbl...
>> >i know, I was just saying that the problem may not be with the IT
> department
>> > at all
>> >
>> >
>> > "Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
>> > news:OWru0JsYEHA.3128@TK2MSFTNGP09.phx.gbl...
>> >> Hi,
>> >>
>> >> MSN is working on the problem affecting a minority of users, depending
> on
>> > how they connect --
>> >> "bugging MSN" isn't going to get it fixed sooner.
>> >> ____________________________________________
>> >> Jonathan Kay
>> >> Microsoft MVP - 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) 2004 Jonathan Kay.
>> >> You *must* contact me for redistribution rights.
>> >>
>> >> "Corey Johnson" <cjohnson202@hotmail.com> wrote in message
>> >> news:euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl...
>> >> > it appears to be the same thing happening to me...if u click on the
> help
>> > box
>> >> > when the error comes up, you will notice that msn is experiencing
>> > technical
>> >> > difficulties that may prevent you from signing in...this could be
> your
>> >> > problem, so instead of bugging your IT, maybe bugging msn would be a
>> > better
>> >> > bet
>> >> >
>> >> >
>> >> > "N. Miller" <duh@blackhole.aosake.net> wrote in message
>> >> > news:MPG.1b53430ca9542feb98a132@msnews.microsoft.com...
>> >> >> In article <270fb01c46282$cf5d3840$a301280a@phx.gbl>, Nuno Cruz
> says...
>> >> >>
>> >> >> > Unfortunatly MSN has become critical for my work and i
>> >> >> > reeeeeeeally need this problem solved..
>> >> >>
>> >> >> Have you requested the assistance of your employer's IT staff? If
> this
>> > is
>> >> >> critical to your job they should be able to get things running for
> you
>> > in
>> >> >> short order.
>> >> >>
>> >> >> > Does anyone have suggestions to solve this?
>> >> >> > I'm behind a firewall that i have no access to.. but i
>> >> >> > know no configurations have been changed since the last
>> >> >> > time i logged in to MSN..
>> >> >>
>> >> >> Any suggestions that I could offer require access to the firewall.
> Bug
>> >> > your
>> >> >> boss, bug the IT staff.
>> >> >>
>> >> >> > Note: I did access my account at home before coming to
>> >> >> > work.. but here (at work) i've been getting the same
>> >> >> > error-code over and over again..
>> >> >>
>> >> >> So, it works.
>> >> >>
>> >> >> > Note2: I can access my hotmail account through the
>> >> >> > website here..
>> >> >>
>> >> >> But Hotmail only works over port 80, MSN Messenger requires a bunch
> of
>> >> >> different ports, depending upon whether it is traversing a UPnP NAT,
> a
>> >> >> proxy, or whatever.
>> >> >>
>> >> >> > Is there something I can do to keep using messenger or is
>> >> >> > this a microsoft-only answer ??
>> >> >>
>> >> >> Without access to your system to see the symptoms, it can be
> difficult.
>> > I
>> >> >> ran into two separate firewall issues last night when I finally bit
> the
>> >> >> bullet and moved up to MSN Messenger 6.2 from 5.0.
>> >> >>
>> >> >> I am using Kerio Personal Firewall, and these are the rules I have
>> >> >> configured for MSN Messenger 6.2:
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >> Descriptions: Messenger - UPnP Both
>> >> >>
>> >> >> Protocol: UDP
>> >> >> Direction: Both directions
>> >> >>
>> >> >> Local endpoint ============================================
>> >> >>
>> >> >> Port type: Port/Range Application:
>> >> >> First port number: 1024 c:%path%msnmsger.exe
>> >> >> Last port number: 65535
>> >> >>
>> >> >> Remote endpoint ===========================================
>> >> >>
>> >> >> Address type: Network/Mask Port type: Single port
>> >> >>
>> >> >> Network Address: 192.168.x.x Port number: 1900
>> >> >> Network Mask: 255.255.255.0
>> >> >>
>> >> >> Rule valid ================================================
>> >> >>
>> >> >> Always
>> >> >>
>> >> >> Action ====================================================
>> >> >>
>> >> >> (#) Permit [ ] Log when this rule matches
>> >> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >> Descriptions: Messenger - Router HTTP
>> >> >>
>> >> >> Protocol: TCP
>> >> >> Direction: Outgoing
>> >> >>
>> >> >> Local endpoint ============================================
>> >> >>
>> >> >> Port type: Port/Range Application:
>> >> >> First port number: 1024 c:%path%msnmsger.exe
>> >> >> Last port number: 65535
>> >> >>
>> >> >> Remote endpoint ===========================================
>> >> >>
>> >> >> Address type: Single address Port type: Single port
>> >> >>
>> >> >> Host Address: 192.168.x.x Port number: 80
>> >> >>
>> >> >> Rule valid ================================================
>> >> >>
>> >> >> Always
>> >> >>
>> >> >> Action ====================================================
>> >> >>
>> >> >> (#) Permit [ ] Log when this rule matches
>> >> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >> Descriptions: Messenger - Discard & Callback
>> >> >>
>> >> >> Protocol: UDP
>> >> >> Direction: Both directions
>> >> >>
>> >> >> Local endpoint ============================================
>> >> >>
>> >> >> Port type: Port/Range Application:
>> >> >> First port number: 1024 c:%path%msnmsger.exe
>> >> >> Last port number: 5000
>> >> >>
>> >> >> Remote endpoint ===========================================
>> >> >>
>> >> >> Address type: Network/Range Port type: List of ports
>> >> >>
>> >> >> First Address: 64.4.12.200 List of Ports: 9,7001
>> >> >> Last Address: 64.4.12.201
>> >> >>
>> >> >> Rule valid ================================================
>> >> >>
>> >> >> Always
>> >> >>
>> >> >> Action ====================================================
>> >> >>
>> >> >> (#) Permit [ ] Log when this rule matches
>> >> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >> Descriptions: Messenger - TSL/SSL
>> >> >>
>> >> >> Protocol: TCP
>> >> >> Direction: Outgoing
>> >> >>
>> >> >> Local endpoint ============================================
>> >> >>
>> >> >> Port type: Port/Range Application:
>> >> >> First port number: 1024 c:%path%msnmsger.exe
>> >> >> Last port number: 5000
>> >> >>
>> >> >> Remote endpoint ===========================================
>> >> >>
>> >> >> Address type: Network/Range Port type: Single port
>> >> >>
>> >> >> First Address: 65.54.179.192 Port number: 443
>> >> >> Last Address: 65.54.231.248
>> >> >>
>> >> >> Rule valid ================================================
>> >> >>
>> >> >> Always
>> >> >>
>> >> >> Action ====================================================
>> >> >>
>> >> >> (#) Permit [ ] Log when this rule matches
>> >> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >> Descriptions: Messenger - Auth & Msgs
>> >> >>
>> >> >> Protocol: TCP
>> >> >> Direction: Outgoing
>> >> >>
>> >> >> Local endpoint ============================================
>> >> >>
>> >> >> Port type: Port/Range Application:
>> >> >> First port number: 1024 c:%path%msnmsger.exe
>> >> >> Last port number: 5000
>> >> >>
>> >> >> Remote endpoint ===========================================
>> >> >>
>> >> >> Address type: Network/Mask Port type: Single port
>> >> >>
>> >> >> First Address: 207.46.0.0 Port number: 1863
>> >> >> Last Address: 255.255.0.0
>> >> >>
>> >> >> Rule valid ================================================
>> >> >>
>> >> >> Always
>> >> >>
>> >> >> Action ====================================================
>> >> >>
>> >> >> (#) Permit [ ] Log when this rule matches
>> >> >> ( ) Deny [ ] Disply alert box when this rule matches
>> >> >>
>> >> >> ___________________________________________________________
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Norman
>> >> >> ~Win dain a lotica, En vai tu ri, Si lo ta
>> >> >> ~Fin dein a loluca, En dragu a sei lain
>> >> >> ~Vi fa-ru les shutai am, En riga-lint
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>



Re: Any suggestions 2 solve 0x81000306 ?? by N

N
Mon Jul 05 18:18:04 CDT 2004

In article <euuYpFsYEHA.3420@TK2MSFTNGP12.phx.gbl>, Corey Johnson says...

> it appears to be the same thing happening to me...if u click on the help box
> when the error comes up, you will notice that msn is experiencing technical
> difficulties that may prevent you from signing in...this could be your
> problem, so instead of bugging your IT, maybe bugging msn would be a better
> bet

Eh. The only connection error I got was due to using a bad password. Other
than that, I was seeing a "non-UPnP restricted NAT." connections status,
until I scoped out the firewall conditions, and fixed those.

OP opined that maybe work was restricting him; if so, work needs to fix the
problem. The difficulty of troubleshooting remotely is trying to sort out
which end of a connection is at fault.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, E