PDA

View Full Version : (+22 rep) MSN Problem



You
01-10-2008, 07:47 PM
Hey,

My mate is having a problem on MSN, when he signs in, goes to options > connections, he has the yellow warning triangle with a black exclamation mark inside it inside a red circle...

Does anyone know how to fix it?

http://i36.tinypic.com/a2uc1.png

+ rep to solutions!!

5,5
01-10-2008, 08:33 PM
Delete cookies

Flisker
01-10-2008, 08:45 PM
restart his router etc

You
01-10-2008, 08:55 PM
Restarted router, looked at settings, changed firewall settings and still nothing.

e5
01-10-2008, 08:56 PM
Use ebuddy.com instead. It's a good alternative to msn

You could try reinstalling msn, restarting the rooter or restarting the computer.

Blue
01-10-2008, 09:04 PM
Is it actually stopping anything from happening?

Just make sure the ports listed here (http://support.microsoft.com/kb/927847) are open

You
01-10-2008, 09:15 PM
PC has been restarted and router, reinstalled MSN about 3 times lol.

Blue, sometimes it'll show him as offline and sometimes messages will not be sent to him.

Blue
01-10-2008, 09:16 PM
Router make?

And does it have UPnP enabled?

Cells
01-10-2008, 09:18 PM
Trouble Shoot.

Its Deafault Gateway, Right Click and Repair it.

OR Run troubleshoot on msn, and repair.

You
01-10-2008, 09:19 PM
As far as i know it's a belkin.
Yeah, UPnP is enabled. MSN on other computers are fine at his but it's just the laptop he is on that shows a problem :S

Cells
01-10-2008, 09:20 PM
I also use Belking, Is this on Vista?

You
01-10-2008, 09:39 PM
Nope, it's on XP.

Samishlol
01-10-2008, 09:41 PM
Maybe the msn server cannot connect to your internet

Cells
01-10-2008, 09:44 PM
Ok, Try to sign in and and wait for the Troubleshoot dialogue.

Let it run and check whats the error, then at the end press repair.

If still all fails, Unplug the wireless dongle, and replace it back in the laptop, then reload msn :)

You
01-10-2008, 09:50 PM
He can sign in fine - It's just sometimes it'll show him as offline and messages don't always get through to him.

I'll tell him about the last bit though.

Samishlol
01-10-2008, 09:51 PM
Because maybe he doesn't have the same verison as you?

You
01-10-2008, 09:54 PM
It is the same version

Slowpoke
01-10-2008, 09:54 PM
It's definately something to do with his internet connection and not MSN. It's hard to diagnose though since we don't have any facts about his computer, internet, connection etc. It really could be anything.

You
01-10-2008, 09:56 PM
We don't think it is his internet connection more along the lines of his PC. He can sign on to his sisters laptop and it'll be fine... He only gets the image (from the first post) when he is on his laptop

Samishlol
01-10-2008, 09:57 PM
I reckon its a signal problem.. is the internet wireless?

You
01-10-2008, 09:59 PM
Yes it is, he is directly above his router and his internet browsing hasn't been affected.

Slowpoke
01-10-2008, 10:01 PM
Yes it is, he is directly above his router and his internet browsing hasn't been affected.

No, it's nothing to do with that, I can't explain it! :(

Cells
01-10-2008, 10:01 PM
Non-UPnP NAT Devices
Windows Messenger peers, separated by a NAT device that cannot be detected, should be able to use IM and Presence information. This is true whether the network service being used is .NET Messenger, Exchange IM, or a SIP solution. Clients using SIP servers also work because logic has been added to the client to ensure communication when the server is opened.

Issues arise, as described earlier in this article, with the other features of Windows Messenger. The following points relate to those issues:

IM and Presence information are implemented through a mediating server with a direct TCP connection initiated by the client when using .NET Messenger or Exchange IM. This should not present any NAT or firewall issues. Sessions or connections initiated by clients external to the NAT device do not succeed because the internal client cannot provide the NAT-translated address to the peer. In the case of AV, this applies to calls made by the internal client to the external client because the external client is the one initiating the SIP session. If the external client calls the internal client, the failure occurs later in the process. The internal client can send the SIP invite to the external client, but the address passed in this invite is incorrect.
Calls made between peers on the same side of the NAT device should work.
An application layer gateway (ALG) for SIP may alleviate some of these problems. ALGs can be used as an application level filter for specific applications and protocols.

Edit: Its dodgier on Msn 7.5 and 8,

It works fine on MSN 7

Want to hide these adverts? Register an account for free!