As I am definately on-line and I downloaded the Messenger for Mac
software correctly i can't understand why it won't let me sign in.
1. Make sure you entered your password correctly. Passwords are case
sensitive
2. Go to the Sign-in dialog and uncheck ³Save Password², click OK. Then quit
and relaunch Messenger. When you try to sign-in manually enter your
password, but do not save.
3. Try to sign-in again to see if it might be server related. Server issues
may take a few hours to resolve. If you always take two tries after
launching the application to sign-in, please delete your preferences and
setup Messenger again. Information about deleting your preferences can be
found below.
4. Check to see if you have the OS Firewall enabled. If so, make sure you
have an exception for the listing ³MSN Messenger². If not, you will need to
create a New exception. The OS firewall settings are set in System
Preferences | Sharing | Firewall tab.
5. If you have a firewall on your router, please make sure to add Messenger
as an expection or open the ports for chatting. Port 1863 over TCP.
6. If you are behind proxies, please make sure they are setup correctly in
the System Preferences | Network. If that doesn¹t help, please set them up
manually in Messenger | Preferences | Accounts. Make sure you have the
correct ³Type² chosen.
7. Are you running any network traffic utilities, such as Little Snitch,
NetBarrier, etc. If so, please make sure you are running the latest version.
You will need to make sure you have allowed Messenger as an exception in any
utility that blocks network traffic, or you will be unable to sign-in.
8. Launch the Keychain Access application, located in your Utilities folder.
Look on the left pane for the x509 anchors. Do any certificates show for the
x509 anchors? If so, do you have the ³Secure Server Certification Authority²
certificate? If not, you will need to copy this certificate from another
Macintosh into the x509 anchors in your keychain, or reinstall the OS. The
certificate allows for a more secure login.
9. Delete your preferences, then try to setup Messenger and sign-in again
> * All preferences are located in your ~/Library/Preferences/Microsoft folder
> * com.microsoft.Messenger.plist
> * com.microsoft.MessengerDaemon.plist
> * Microsoft Messenger User Cache
> * Microsoft Messenger User Cache.plist
If none of the above works for you, please send a TCPDump (instructions
below) to your support representative. Please make sure no other network
applications are running at the time, outside of Messenger. Thanks.
Getting a TCPDump log:
1) Open System Preferences and choose the Network item. In the Show
selector choose Network Status; you should see a list of network interfaces
- the current network adapter in use will have a green dot to the left of
its name. If you see more than one adapter with a green dot then you will
have to figure out which one is the adapter connected to the internet. The
description text for the network adapter should show its IP address (looks
something like 182.168.0.14) - jot this IP address down as you will need it
later. If the description text does not contain the IP address then you
should double click on the network interface to open it up. Once you are
examining this network interface choose the TCP/IP tab and jot down the IP
address.
2) Using the Network Utility (found at /Applications/Utilities/Network
Utility.app) select the Info tab and cycle through the Network Interfaces
selector looking for one whose IP address matches the IP address that you
found in step 1. When you have found the matching network adaptor you will
need to note the Unix network interface name shown in the selector;
typically something like fw0, en0 or en1.
IMPORTANT NOTE: Before proceeding any further make sure to close down any
applications that access the network. These include Web browsers, Email
programs, Chat programs, etc. This will help keep your private data private
as well as reduce the amount of noise (or non-applicable data) in the
network capture.
3) Open the terminal application found at
/Applications/Utilities/Terminal.app
4) Type the following line into the Terminal application making sure to
substitute the XXX with your active network adapter's name (found in step
2). Once the proper network name is substituted for the XXX placeholder hit
the enter/return key to start the network capture. This will start the
network capture and dump the output to a file named NetworkCapture.txt on
your desktop.
sudo tcpdump i XXX s 10000 U -w ~/Desktop/networkcapt.txt ip proto
TCP
IMPORTANT NOTE: Once you have entered the above line and hit enter you will
be asked for your password; your Mac OS X login password is required to run
the tcpdump tool (via the sudo command). Your account must also be able to
administer the computer in order for the sudo command to work for you.
5) Attempt to login with Messenger
6) Click on the Terminal window to activate it. Press and hold the control
key and press the c key - this will stop the network capture. You should
see a file named networkcapt.txt on your desktop; you should send this file
to your support representative (harriss...@hotmail.com).
----------------
On 8/1/07 3:54 PM, in article
1186001696.7...@q75g2000hsh.googlegroups.com,
"calebcu...@hotmail.com" <calebcu...@hotmail.com> wrote:
--
Mickey Stevens (Microsoft MVP for Office:mac)
Office & Mac Resources: <http://home.earthlink.net/~mickey.stevens/>
a. Web Messenger
b. Third-parties software Adium
is a problem at MSN client only...
no la.. get same problem at MSN window. with exception code
81000378... xyz
try web messenger... or third-parties software (eg adium) should work
On 26/02/08 15:33, in article ee7e3...@webcrossing.caR9absDaxw, "Me" <Me>
wrote:
--
Michel Bintener
Microsoft MVP
Office:mac (Entourage & Word)
*** Please always reply to the newsgroup. ***
I can log in on any of my pc's but it appears that messenger will only work on a mac if the weather is not too rainy or depending on what you had for breakfast that morning. In my case, it appears that the weather has been stormy for 6 months or so.
I know that it is a problem with mac messenger. It has nothing to do with my mac, osx, isp, router, firewall, etc.
Microsoft - PLEASE FIX THIS ISSUE
when i click on the "sign in" link the email and password window comes up fine, but when i click "ok" i get another window saying :-
"A newer version of MSN Messenger for macs is available. you must download the newer version in order to continue".
So i hit the download button. 30secs of loading later i get a bloody MSN Messenger document called "messenger.bin". so i click on that... but THEN another sodding window opens telling me...
"you must be signed in before you can import a contact list"
so i went back to the sign in window and clicked on the sign in link... which told me the same @£$@ing thing as last time (a newer version blah blah, must download blah blah, in order to continue, blah)!!!!!
this is a irritating and vicious cycle that is baffling me PLEEEEASE HELP ME FIGURE THIS OUT!!!
thanks andy
I have tried both aMSN & Adium & they aren't connecting. I've tried changing my password & that hasn't worked.
If my friends weren't windows MSN users I wouldn't bother with this rubbish.
:angry:
Weirdly enough, my co-worker sees me as "signed in" but "away" yet when he send me a message, it never gets to me, and my Messenger 7 app shows me as not signed in.
Are you using the Office Communications Server 2007 or LCS 2005?
Messenger 7 supports OCS 2007. If your company is using LCS 2005, you'll
need to use Messenger 6.0.3.
Thanks,
Rebecca
Rebecca Harriss
rhar...@online.microsoft.com (remove online for any direct replies)
Microsoft Corporation
Macintosh Business Unit, SDET
This posting is provided ³AS IS² with no warranties, and confers no rights.
Cheers.
Please see below.
Here is some standard troubleshooting to try if you are unable to sign-in.
1. Make sure you entered your password correctly. Passwords are case
sensitive
2. Go to the Sign-in dialog and uncheck ģSave Passwordē, click OK. Then quit
and relaunch Messenger. When you try to sign-in manually enter your
password, but do not save.
3. Try to sign-in again to see if it might be server related. Server issues
may take a few hours to resolve. If you always take two tries after
launching the application to sign-in, please delete your preferences and
setup Messenger again. Information about deleting your preferences can be
found below.
4. Check to see if you have the OS Firewall enabled. 10.4.x If so, make sure
you have an exception for the listing ģMSN Messengerē. If not, you will need
to create a New exception. The OS firewall settings are set in System
Preferences | Sharing | Firewall tab. 10.5.x instructions: System
Preferences | Security | Firewall and either enable ģAll incoming
connectionsē (allows everything), ģAllow only essential servicesē, or
choose ģSet Access for specific services . . .ē. The first option allows
everything. The second & third options are potential culprits. If you have
either of the latter 2 options, you need to make an exception for Messenger
by clicking the + button and adding the application to the list of
exceptions.
5. If you have a firewall on your router, please make sure to add Messenger
as an expection or open the ports for chatting. Port 1863 over TCP.
6. If you are behind proxies, please make sure they are setup correctly in
the System Preferences | Network. If that doesnđt help, please set them up
manually in Messenger | Preferences | Accounts. Make sure you have the
correct ģTypeē chosen.
7. Are you running any network traffic utilities, such as Little Snitch,
NetBarrier, etc. If so, please make sure you are running the latest version.
You will need to make sure you have allowed Messenger as an exception in any
utility that blocks network traffic, or you will be unable to sign-in.
8. OS X 10.4.x and later: Launch the Keychain Access application, located in
your Utilities folder. Look on the left pane for the x509 anchors. Do any
certificates show for the x509 anchors? If so, do you have the ģSecure
Server Certification Authorityē certificate? If not, you will need to copy
this certificate from another Macintosh into the x509 anchors in your
keychain, or reinstall the OS. The certificate allows for a more secure
login. OS X 10.5.x: Launch Keychain Access located in your Utilities
folder. Choose File -> Add to Keychain, then select
/System/Library/Keychains/X509Certificates.obsoleted. You should now be able
to view the x509 anchors. Do any certificates show for the x509 anchors? If
so, do you have the ģSecure Server Certification Authorityē certificate? If
not, you will need to copy this certificate from another Macintosh into the
x509 anchors in your keychain, or reinstall the OS. The certificate allows
for a more secure login.
9. Delete your preferences, then try to setup Messenger and sign-in again
> * All preferences are located in your ~/Library/Preferences/Microsoft folder
> for Messenger 6.0.3 and in ~/Library/Preferences for Messenger 7.0
> * com.microsoft.Messenger.plist
> * com.microsoft.MessengerDaemon.plist
> * com.microsoft.Messenger.rtc.plist
> * Microsoft Messenger User Cache
> * Microsoft Messenger User Cache.plist (Located in the
> ~/Library/Preferences/Microsoft folder for both Messenger 6.0.3 & Messenger
> 7.0)
If none of the above works for you, please send an Apple System Profile
Report and a Messenger Log. (instructions below). A TCPDump (instructions
below) may also be requested at a later time. Please make sure no other
network applications are running at the time, outside of Messenger when
gathering a TCPDump. Thanks.
Getting an Apple System Profile Report:
1. Go under the blue apple menu and choose About This Mac
2. Click the ģMore Info . . .ē button
3. Choose Save and select a name for the file
Enabling Messenger Logs for Messenger 6.0.3:
Quit Messenger
Go to /Applications/Utilities and launch the Terminal application
Type the following on one line exactly as you see below:
defaults write ~/Library/Preferences/Microsoft/com.microsoft.Messenger
EnableConnectionLogging -bool true
Disabling Messenger Logs for Messenger 6.0.3: Quit Messenger
Go to /Applications/Utilities and launch the Terminal application
Type the following on one line exactly as you see below:
defaults write ~/Library/Preferences/Microsoft/com.microsoft.Messenger
EnableConnectionLogging -bool false
Enabling/Disabling Messenger Logs for Messenger 7:
Launch Messenger
Messenger | Preferences | General tab
Under the Logging section check the checkbox ģSave a log . . .ē to enable
logging
Under the Logging section uncheck the checkbox ģSave a log . . .ē to disable
logging
Locating Messenger Logs: Messenger logs are located in your ~/Documents
folder and the file name is Microsoft Messenger.log
Deleting Messenger Logs: Quit Messenger
Move the log named Microsoft Messenger.log to the trash and empty it
Notes about Messenger Logs: Enabling logs saves a file containing personal
information to ~/Documents. Anyone with access to this directory can open
this file.
They are not automatically deleted
They will continue to grow in size if you don't delete them from time to
time or disable logging
Deleting your log without disabling logging will create a new log on launch
of Messenger
Deleting your com.microsoft.messenger.plist file (preference file) will
clear out any settings for logging. You will have to re-enable the logging
again if you want to get a Messenger log file
Getting a TCPDump log:
1) Open System Preferences and choose the Network item. In the Show
selector choose Network Status; you should see a list of network interfaces
- the current network adapter in use will have a green dot to the left of
its name. If you see more than one adapter with a green dot then you will
have to figure out which one is the adapter connected to the internet. The
description text for the network adapter should show its IP address (looks
something like 182.168.0.14) - jot this IP address down as you will need it
later. If the description text does not contain the IP address then you
should double click on the network interface to open it up. Once you are
examining this network interface choose the TCP/IP tab and jot down the IP
address.
2) Using the Network Utility (found at /Applications/Utilities/Network
Utility.app) select the Info tab and cycle through the Network Interfaces
selector looking for one whose IP address matches the IP address that you
found in step 1. When you have found the matching network adaptor you will
need to note the Unix network interface name shown in the selector;
typically something like fw0, en0 or en1.
IMPORTANT NOTE: Before proceeding any further make sure to close down any
applications that access the network. These include Web browsers, Email
programs, Chat programs, etc. This will help keep your private data private
as well as reduce the amount of noise (or non-applicable data) in the
network capture.
3) Open the terminal application found at
/Applications/Utilities/Terminal.app
4) Type the following line into the Terminal application making sure to
substitute the XXX with your active network adapter's name (found in step
2). Once the proper network name is substituted for the XXX placeholder hit
the enter/return key to start the network capture. This will start the
network capture and dump the output to a file named NetworkCapture.txt on
your desktop.
sudo tcpdump i XXX s 10000 U -w ~/Desktop/networkcapt.txt ip proto
TCP
IMPORTANT NOTE: Once you have entered the above line and hit enter you will
be asked for your password; your Mac OS X login password is required to run
the tcpdump tool (via the sudo command). Your account must also be able to
administer the computer in order for the sudo command to work for you.
5) Attempt to login with Messenger
6) Click on the Terminal window to activate it. Press and hold the control
key and press the c key - this will stop the network capture. You should
see a file named networkcapt.txt on your desktop; you should send this file
to rhar...@online.microsoft.com (removing the ģonlineē before sending).
Thanks,
Rebecca
Rebecca Harriss
rhar...@online.microsoft.com (remove online for any direct replies)
Microsoft Corporation
Macintosh Business Unit, SDET
This posting is provided ģAS ISē with no warranties, and confers no rights.
Thanks for your advice.
I went through the troubleshooting steps as best I could and have found the x509 anchors to be missing. Reinstalling the OS seems incredibly disproportionate to getting Messenger working, besides my Mac is only a month old! Have you any other suggestions please?
Thanks again.
Hi, please install the x509 anchors. If you are on Leopard (10.5.x) the
instructions are below. The x509 anchors are there by default on 10.4.x
OS X 10.5.x: Launch Keychain Access located in your Utilities
folder. Choose File -> Add to Keychain, then select
/System/Library/Keychains/X509Certificates.obsoleted. You should now be able
to view the x509 anchors. Do any certificates show for the x509 anchors? If
so, do you have the ³Secure Server Certification Authority² certificate? If
not, you will need to copy this certificate from another Macintosh into the
x509 anchors in your keychain, or reinstall the OS. The certificate allows
for a more secure login.
Thanks,
Rebecca
Rebecca Harriss
rhar...@online.microsoft.com (remove online for any direct replies)
Microsoft Corporation
Macintosh Business Unit, SDET
This posting is provided ³AS IS² with no warranties, and confers no rights.
Tomislav - mail: igu...@gmail.com
Just an FYI for anyone using TLS in Mac Messanger and OSX Leopard
(10.5).
The instructions in the Mac Messenger Deployment Guide for adding an
X509 Certificate to the OSX Keychain do not work on Leopard. In
previous OSX versions the "X509 Anchors" keychain is added to your
keychain by default and is an option when you double click a
certificate for import. With Leopard however you must manually open
your "Applications/Utilities/Keychain Accces", go to "File" then "Add
Keychain". Then navigate to /System/Library/Keychains where you should see the file "X509Anchors", add this keychain. This keychain is the keychain that must contain the correct certificate your corporation
uses for TLS transport. If your corp happens to use a standard public
certificate of course you will never have to worry about this, but if
it is an non-included certificate you must import to to that keychain.
So if one's corporate folks are locked into LCS 2005, the Mac users at such a company are stuck with Messenger 6.0.3?! And in order to use the new video capabilities of Messenger 7 the Mac users will have to convince the IT folks to upgrade to OCS 2007, even though there's no real benefit to do that?
ARGH, this is a major disappointment!!!
That is correct, Messenger 7 requires the OCS 2007 server.
Thanks,
Rebecca
Rebecca Harriss
rhar...@online.microsoft.com (remove online for any direct replies)
Microsoft Corporation
Macintosh Business Unit, SDET
This posting is provided ³AS IS² with no warranties, and confers no rights.
My mac OS X, 10.4.11... please help I really need have msn... before I was use it on my HP laptop but at the moment I'm not able to use it... also, I spent so much money on my macbook... I think I have the right to make it work ...
Help!!! Please!!
Dan
Do you have any extended characters in your password? If so, can you change
to an all lowercase alphabet based password and see if that works?
Another user also pointed out issues with a particular version of the
firmware on Netgear routers causing problems in a post on 5/27 that may be
of interest if you are running a Netgear router.
Also, please see the post on 5/19 and 5/23 where I suggest specific
troubleshooting regarding signing into the personal service.
If you are unable to sign-in, after trying the various things, I need to get
logs in order to help troubleshoot the problem.
Hi Dan,
Do you have any extended characters in your password? If so, can you change
to an all lowercase alphabet based password and see if that works?
Another user also pointed out issues with a particular version of the
firmware on Netgear routers causing problems in a post on 5/27 that may be
of interest if you are running a Netgear router.
Also, please see the post on 5/19 and 5/23 where I suggest specific
troubleshooting regarding signing into the personal service.
If you are unable to sign-in, after trying the various things, I need to get
logs in order to help troubleshoot the problem as described in the posts
above.
Do you have any extended characters in your password? If so, can you change
to an all lowercase alphabet based password and see if that works?
Another user also pointed out issues with a particular version of the
firmware on Netgear routers causing problems in a post on 5/27 that may be
of interest if you are running a Netgear router.
Also, please see the post on 5/19 and 5/23 where I suggest specific
troubleshooting regarding signing into the personal service.
If you are unable to sign-in, after trying the various things, I need to get
logs in order to help troubleshoot the problem.
A problem has appeared in Microsoft Messenger and the progamma must be closed. Our excuses for the inconvenience.
You were busy with treating something. These data have possibly lost gone.
Tell Microsoft about this problem.
With Microsoft Messenger an error report has been made that you can send, so that we can improve Microsoft Messenger. This report are treated confidentially and anonymously.
(sorry for the bad grammar, i'm from the Netherlands)
Can somebody help me? It happens all the time..
Hi,
Another user also pointed out issues with a particular version of the
firmware on Netgear routers causing problems in a post on 5/27 that may be
of interest if you are running a Netgear router.
Please let us know if reverting the firmware version resolved your sign-in
issue.
> > On 5/12/08 1:28 PM, in article ee7e3...@webcrossing.caR9absDaxw,
> > "subaq...@officeformac.com" wrote: > > > > > Hi Rebecca, > > > >
> > Thanks for your advice. > > > > > > I went through the troubleshooting
steps as best I could and have found the > > > x509 anchors to be missing.
Reinstalling the OS seems incredibly > > > disproportionate to getting
Messenger working, besides my Mac is only a month > > > old! Have you
any other suggestions please? > > > > > > Thanks again. > > > > Hi, please
install the x509 anchors. If you are on Leopard (10.5.x) the > > instructions
are below. The x509 anchors are there by default on 10.4.x > > > > OS
X 10.5.x: Launch Keychain Access located in your Utilities > > folder.
Choose File -> Add to Keychain, then select > > /System/Library/Keychains/X509Certificates.obsoleted.
You should now be able > > to view the x509 anchors. Do any certificates
show for the x509 anchors? If > > so, do you have the �Secure Server
Certification Authority� certificate? If > > not, you will need
to copy this certificate from another Macintosh into the > > x509 anchors
in your keychain, or reinstall the OS. The certificate allows > > for
a more secure login. > > > > Thanks, > > Rebecca > > > > Rebecca Harriss
> > rhar...@online.microsoft.com (remove online for any direct replies)
> > Microsoft Corporation > > Macintosh Business Unit, SDET > > > > This
posting is provided �AS IS� with no warranties, and confers
no rights. > > > > > > > > > > > Hi, > I copy this answer from - <http://groups.google.com/group/microsoft.public.mac.messenger/browse_thread/thread/d82459f5ecb3813c>
> And that solution worked fine for me. > > Tomislav - mail: igu...@gmail.com
> > Just an FYI for anyone using TLS in Mac Messanger and OSX Leopard
> (10.5). > > The instructions in the Mac Messenger Deployment Guide for
adding an > X509 Certificate to the OSX Keychain do not work on Leopard.
In > previous OSX versions the "X509 Anchors" keychain is added to your
> keychain by default and is an option when you double click a > certificate
for import. With Leopard however you must manually open > your "Applications/Utilities/Keychain
Accces", go to "File" then "Add > Keychain". Then navigate to /System/Library/Keychains
where you should see the file "X509Anchors", add this keychain. This keychain
is the keychain that must contain the correct certificate your corporation
> uses for TLS transport. If your corp happens to use a standard public
> certificate of course you will never have to worry about this, but if
> it is an non-included certificate you must import to to that keychain.
did this work for anyone? it surely didn't work for me as i don't have
X509Anchors in the System/Library/Keychains folder, and have no idea where
to download it from... so... still stuck with "not able to connect to
the server...
Received same "unable to connect" message about 20 minutes ago, but I’m back in service. Try this fix: Log out, close all files and applications and shut off your computer. Unplug modem for about 30 seconds. Plug modem back in and re-start.
Good luck!
Hope this helps other people.
Take care.
same hereeee!!!! i can't log on to my messenger as well!
On 7/16/08 10:36 AM, in article ee7e3...@webcrossing.caR9absDaxw, "MONICA
It used to work fine.. I have been using VMware Fusion and Windows MSN Messenger or web messenger instead, which both sign in no problems.
Can anyone advise why suddenly MSN Messenger for MAC would stop working on both machines? When started, after clicking 'sign in', within an extremely short time less than a second, msn gives the standard failed to connect error.
The netgear router has not changed, the mac's have not changed other than any standard OSX updates. MSN MAC used to work fine!
Any help would be greatly appreciated...
Messenger will not let me access my hotmail inbox in Safari. I have to login through Firefox. What is going on?
I can't access msn via any IM application be it messenger for Mac or otherwise. I can't change my password because i can't login via any browser because the server stops responding. I have accessed messenger from both messenger for mac and third party apps on my dads macbook on the same network as my laptop, and from the latest messenger for windows on my uni network. So i know it has something to do with my computer personally.
I have deleted all the preferences, I haven't tried the TCPDump but i don't think its a simple messenger problem.
I can get onto www.live.com but as soon as i click login it times out. Is there anyone else who has this problem....
Canon
Yep, same problem here too. Messenger Mac not been working for a few days
now. I have not changed anything in the settings since then - what's wrong???
Luckily for me, this was easily resolved by changing my password to one that only consisted of alphabetic characters. However, this had made my password much less secure, which I am not happy about!
Thank you to Microsoft for reminding me once again why I chose a Mac. I can't stand putting up with sub-standard software and inadequate support to solve problems, such as the examples above. If you bothered to test your software properly, situations like this might be avoided.
I hope that the problem will be properly addressed, such that users can use more secure passwords and more serious problems are resolved so that Mac users don't have to resort to fiddling around with keychains and re-installing OS, which really isn't acceptable.
MY ADVICE TO YOU ALL IS TO PUT YOURSELVES OUT YOUR MISERY AND USE SKYPE INSTEAD!!! ;-)
On 5/11/08 9:23 AM, in article ee7e3...@webcrossing.caR9absDaxw, "subaq...@officeformac.com"
wrote:
> I'm having a similar problem. I had no issues with version 6 but upgraded
to 7 > the other day. I can still connect at home but I can't connect
in college - it > says I don't seem to be connected to the internet. I've
tried manually > activating the proxy settings instead of through OS X
with no luck. Any ideas? > > Cheers. > >> I have upgraded to Messenger
7 from version 6. Version 6 worked fine for my >> corporate network. The
upgrade properly transferred to settings over. >> However, now when I
try and sign in I get a message that the service is not >> available or
I may not be connected to the internet. >> >> Weirdly enough, my co-worker
sees me as "signed in" but "away" yet when he >> send me a message, it
never gets to me, and my Messenger 7 app shows me as >> not signed in.
Please see below.
Here is some standard troubleshooting to try if you are unable to sign-in.
1. Make sure you entered your password correctly. Passwords are case sensitive
2. Go to the Sign-in dialog and uncheck �Save Password�,
click OK. Then quit and relaunch Messenger. When you try to sign-in manually
enter your password, but do not save. 3. Try to sign-in again to see if
it might be server related. Server issues may take a few hours to resolve.
If you always take two tries after launching the application to sign-in,
please delete your preferences and setup Messenger again. Information
about deleting your preferences can be found below. 4. Check to see if
you have the OS Firewall enabled. 10.4.x If so, make sure you have an
exception for the listing �MSN Messenger�. If not, you will
need to create a New exception. The OS firewall settings are set in System
Preferences | Sharing | Firewall tab. 10.5.x instructions: System Preferences
| Security | Firewall and either enable �All incoming connections�
(allows everything), �Allow only essential services�, or
choose �Set Access for specific services . . .�. The first
option allows everything. The second & third options are potential culprits.
If you have either of the latter 2 options, you need to make an exception
for Messenger by clicking the + button and adding the application to the
list of exceptions. 5. If you have a firewall on your router, please make
sure to add Messenger as an expection or open the ports for chatting.
Port 1863 over TCP. 6. If you are behind proxies, please make sure they
are setup correctly in the System Preferences | Network. If that doesn�t
help, please set them up manually in Messenger | Preferences | Accounts.
Make sure you have the correct �Type� chosen. 7. Are you
running any network traffic utilities, such as Little Snitch, NetBarrier,
etc. If so, please make sure you are running the latest version. You will
need to make sure you have allowed Messenger as an exception in any utility
that blocks network traffic, or you will be unable to sign-in. 8. OS X
10.4.x and later: Launch the Keychain Access application, located in your
Utilities folder. Look on the left pane for the x509 anchors. Do any certificates
show for the x509 anchors? If so, do you have the �Secure Server
Certification Authority� certificate? If not, you will need to
copy this certificate from another Macintosh into the x509 anchors in
your keychain, or reinstall the OS. The certificate allows for a more
secure login. OS X 10.5.x: Launch Keychain Access located in your Utilities
folder. Choose File -> Add to Keychain, then select /System/Library/Keychains/X509Certificates.obsoleted.
You should now be able to view the x509 anchors. Do any certificates show
for the x509 anchors? If so, do you have the �Secure Server Certification
Authority� certificate? If not, you will need to copy this certificate
from another Macintosh into the x509 anchors in your keychain, or reinstall
the OS. The certificate allows for a more secure login. 9. Delete your
preferences, then try to setup Messenger and sign-in again > * All preferences
are located in your ~/Library/Preferences/Microsoft folder > for Messenger
6.0.3 and in ~/Library/Preferences for Messenger 7.0 > * com.microsoft.Messenger.plist
> * com.microsoft.MessengerDaemon.plist > * com.microsoft.Messenger.rtc.plist
> * Microsoft Messenger User Cache > * Microsoft Messenger User Cache.plist
(Located in the > ~/Library/Preferences/Microsoft folder for both Messenger
6.0.3 & Messenger > 7.0)
If none of the above works for you, please send an Apple System Profile
Report and a Messenger Log. (instructions below). A TCPDump (instructions
below) may also be requested at a later time. Please make sure no other
network applications are running at the time, outside of Messenger when
gathering a TCPDump. Thanks.
Getting an Apple System Profile Report: 1. Go under the blue apple menu
and choose About This Mac 2. Click the �More Info . . .�
button 3. Choose Save and select a name for the file
Enabling Messenger Logs for Messenger 6.0.3: Quit Messenger Go to /Applications/Utilities
and launch the Terminal application Type the following on one line exactly
as you see below: defaults write ~/Library/Preferences/Microsoft/com.microsoft.Messenger
EnableConnectionLogging -bool true
Disabling Messenger Logs for Messenger 6.0.3: Quit Messenger Go to /Applications/Utilities
and launch the Terminal application Type the following on one line exactly
as you see below: defaults write ~/Library/Preferences/Microsoft/com.microsoft.Messenger
EnableConnectionLogging -bool false
Enabling/Disabling Messenger Logs for Messenger 7: Launch Messenger Messenger
| Preferences | General tab Under the Logging section check the checkbox
�Save a log . . .� to enable logging Under the Logging section
uncheck the checkbox �Save a log . . .� to disable logging
Locating Messenger Logs: Messenger logs are located in your ~/Documents
folder and the file name is Microsoft Messenger.log
Deleting Messenger Logs: Quit Messenger Move the log named Microsoft Messenger.log
to the trash and empty it
Notes about Messenger Logs: Enabling logs saves a file containing personal
information to ~/Documents. Anyone with access to this directory can open
this file. They are not automatically deleted They will continue to grow
in size if you don't delete them from time to time or disable logging
Deleting your log without disabling logging will create a new log on launch
of Messenger Deleting your com.microsoft.messenger.plist file (preference
file) will clear out any settings for logging. You will have to re-enable
the logging again if you want to get a Messenger log file
Getting a TCPDump log:
1) Open System Preferences and choose the Network item. In the Show selector
choose Network Status; you should see a list of network interfaces - the
current network adapter in use will have a green dot to the left of its
name. If you see more than one adapter with a green dot then you will
have to figure out which one is the adapter connected to the internet.
The description text for the network adapter should show its IP address
(looks something like 182.168.0.14) - jot this IP address down as you
will need it later. If the description text does not contain the IP address
then you should double click on the network interface to open it up. Once
you are examining this network interface choose the TCP/IP tab and jot
down the IP address.
2) Using the Network Utility (found at /Applications/Utilities/Network
Utility.app) select the Info tab and cycle through the Network Interfaces
selector looking for one whose IP address matches the IP address that
you found in step 1. When you have found the matching network adaptor
you will need to note the Unix network interface name shown in the selector;
typically something like fw0, en0 or en1.
IMPORTANT NOTE: Before proceeding any further make sure to close down
any applications that access the network. These include Web browsers,
Email programs, Chat programs, etc. This will help keep your private data
private as well as reduce the amount of noise (or non-applicable data)
in the network capture.
3) Open the terminal application found at /Applications/Utilities/Terminal.app
4) Type the following line into the Terminal application making sure to
substitute the XXX with your active network adapter's name (found in step
2). Once the proper network name is substituted for the XXX placeholder
hit the enter/return key to start the network capture. This will start
the network capture and dump the output to a file named NetworkCapture.txt
on your desktop.
sudo tcpdump �i XXX �s 10000 �U -w ~/Desktop/networkcapt.txt
ip proto TCP
IMPORTANT NOTE: Once you have entered the above line and hit enter you
will be asked for your password; your Mac OS X login password is required
to run the tcpdump tool (via the sudo command). Your account must also
be able to administer the computer in order for the sudo command to work
for you.
5) Attempt to login with Messenger
6) Click on the Terminal window to activate it. Press and hold the control
key and press the c key - this will stop the network capture. You should
see a file named networkcapt.txt on your desktop; you should send this
file to rhar...@online.microsoft.com (removing the �online�
before sending).
In the /System/Library/Keychain folder I only have a 'login.keychain' file and a 'Microsoft_Intermediate_Certificates' file. Any ideas where I can find the x509 certificates?
Cheers and thanks.
sorry but I'm not going through all of that when it was working this morning
and every day before that and I haven't changed any settings on my mac
or on the router or other computers on the network!
Since installing Office 2008 along Office 2004 , i ve been unable to enter my messenger account. I tried Adium and it get stuck at 75% authenticating and then times out repeats and repeats. MSN Messenger (ver 6 & 7 ) cant find find me at all says" sig in in failed because the password is incorrect or the sign-in names does not exist. etc.. Tried the X509 anchors suggestion with keychain no go . Nowt worked. Tried copying from my partners mac and that buggered up my keychain and passwords.
Seems many of us are having to reinstall everything again only to encounter this hurdle again. Can anyone tell us what is really happening.
Is there a new version planned for any time soon? This is very annoying. i even tried contacting microsoft about this issue and they did not reply to my email. Please help me!
I can log in to Messenger with all of my accounts and friends accounts except one that I had been using just fine up until yesterday. No changes in the machine or router or proxies, etc...
Like I said Messenger logs other accounts in just fine, it's a problem with the one account.
The particular account seems to be hanging after it gets all of my contacts (according to the log file).
After that, it just hangs there until it times out.
Here's a cut & paste of the very bottom of the log file:
<c n="madelynbymabe" l="4" t="1" /><c n="saundrapozany" l="4" t="1" /><c n="ykpeate" l="4" t="1" /></d></ml>
2009/02/26 19:09:26.456 <<--< 508 5 50
<ml><d n="yahoo.com"><c n="jedymastyr" /></d></ml>
2009/02/26 19:09:26.456 <<--< 508 5 51
<ml><d n="yahoo.com"><c n="vittoriaspa" /></d></ml>
2009/02/26 19:09:26.456 <<--< 508 5 47
<ml><d n="yahoo.com"><c n="smeglor" /></d></ml>
2009/02/26 19:12:19.144 Login (0) failed with error: (0.0)
Any ideas?
The only problem I'm having is using Microsoft Messenger Mac and only signing in to this one account.
"2009/02/27 12:42:33.204 >-->> ADL 12 70
<ml><d n="yahoo.com"><c n="spider_pierce2004" l="1" t="32" /></d></ml>
2009/02/27 12:42:33.339 <<--< ADL 11 OK
2009/02/27 12:42:33.350 <<--< ADL 12 OK
2009/02/27 12:44:14.393 Login (0) failed with error: (1.0)"
I noticed something in that log, the signing process get stuck when is processing the the "contact Block List".. the last Live ids are from my block list... and I found that there is no way to remove those contacts forever from the blacklist. <http://www.vistax64.com/live-messenger/129565-how-fully-delete-contacts-msn-live-messenger.html>
Also, between the day this was working for me, and the next day when it all of a sudden wasn't, I didn't make any change to my contacts, so I'm not sure what happened.
Think we could get a response from someone at MS on this?
thanks
the funny thing is, i can't log into the same email account on adium, amsn, ebuddy, msn2go, or even the older 6.0 version of mac messenger. but another email works fine. i just don't know wtz wrong and it's soooo frustrating.
it's been a couple days now...please help!!!!(should i post my log as well?)
Come on MS! Fix it!
I remove everything that was related to the Messenger and then I re-installed and when it asked me for email and password during the installation, I did not choose "remember me" and worked.
I had it already uninstalled, so I downloaded the newest version. I tried signing in and it didn't work. Then in MSN's Preferences I went to "account" and under network settings I checked off "automatic" since it was on manual and it worked.
The next problem now I have is after awhile, I get signed off (and I mean a WHILE I could be on for more than an hour) and I get an error sending it crashed. When I open it back up, it resets anything I changed ( Display pic, display name etc etc). So...it's kinda fixed? lol.
Maybe that'll help some of you. I hope/wish for MSN to just FIX IT!!! grrrr.