Anyone having trouble connecting to MSN?

For the past few days I've found that MSN messenger fails to connect on both my desktop and laptop. In the process of elimination I connected to a nearby open wifi point and was able to connect to MSN no problem. I've tried rebooting my router but still can't connect through my own connection.

Anyone else having problems or got any ideas?

Not having any problems.

Try changing your DNS servers and see if the issue goes away.

Do you have any port forwarding or QoS rules on your router that may be causing this?

No QoS on my router. Nothing has been changed lately. Something that makes it even stranger is that it only seems to affect the official MS app. If i use IM+ on my iPad it connects without problem.

in MSN Go into tools > options > connection - and see what comes up?
Then go > Advanced > and run the tests.

Edited by Pipexer (Sat 17-Dec-11 23:13:45)

Seems like it's contradicting itself

http://imageshack.us/photo/my-images/862/24711558.jpg/

followed by

http://imageshack.us/photo/my-images/543/66284012.jpg/

Weird!

I'd try temporarily changing your preferred DNS server on the network adapters settings in Windows to google DNS (8.8.8.8), reboot the computer, and try again. I'd have thought if fault lies anywhere with Zen it would be with their DNS.

Is your system clock correct?

Is your network location "Home"?

Is Windows Live Messenger allowed in Windows Firewall? It's poss when you connected to public wifi you selected public network location which may have had correct config, but your local wireless may be "home", and settings in there may be goofed, for example.

Any proxy servers configured in internet options?

Edited by Pipexer (Sat 17-Dec-11 23:45:26)

All those settings are fine. Just installed Pidgin which also connects fine. It's something limited to the MS client only used in conjunction with my Zen connection

When you went into Connection did you get something like this?

http://i39.tinypic.com/nbd8ok.png

Strange, I mean one hand it "rules out" zen due to it working with other clients, then on the other it "rules out" the clients due to it occuring to two of them. Router is looking like a culprit.

Yeah except it said I wasn't connected to the messenger service (obviously)

I think you should change the DNS server temporarlily and see if the issue still persists. I notice you are putting that off (Any specific reason?)

Assuming you have double checked windows firewall settings and other neccessary things, and tried a final full reboot of router and PC, in your position, what I'd now be doing is putting my router back to factory defaults in case port forwarding has upset it.

Can you post the output of an IPconfig /all onto here?

I don't think this is a Zen problem because more people would be on here complaining about it, but I could, of course, be wrong, which would make everything above (bar first step potentially) redundant.

Edited by Pipexer (Sun 18-Dec-11 01:00:29)

Do you mean change the DNS settings on my pc or in the router setup? Also I don't have any port forwarding configured. Will post the ipconfig results when I'm back on the pc later today

I'd do it locally on your PC - that way it's only a few mouse clicks to change and revert.

Didn't have any effect

Here's the ipconfig info

Windows IP Configuration

Host Name . . . . . . . . . . . . : Paul-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Edimax 802.11n PCI Card
Physical Address. . . . . . . . . : 00-1F-1F-59-21-4E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d0dd:ec88:ca0f:3d17%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 18 December 2011 15:12:11
Lease Expires . . . . . . . . . . : 19 December 2011 15:16:08
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 184557343
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-F7-1B-C2-00-1F-1F-59-21-4E

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2cfd:788:2664:3cf7(Preferred)
Link-local IPv6 Address . . . . . : fe80::2cfd:788:2664:3cf7%15(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{3F5C43F0-FE7D-4E43-BCB9-0AD88D6272CB}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

In reply to a post by No_One:

DNS Servers . . . . . . . . . . . : 192.168.0.1

That means DNS settings not in PC but in router!

Did you restart the PC inbetween changing the DNS server? Or at the very very least ipconfig /flushdns

Otherwise stale information will be cached

Huh?

Pipexer recommended you change your DNS in the PC. That "DNS Servers . . . . . . . . . . . : 192.168.0.1" indicates the PC is using the DNS in the router. Which one did you change?

It wasn't just you. I had exactly the same problem; worked fine on another connection but not with Zen, yet unofficial clients (Pidgin) worked fine.

Edited by deleted (Mon 19-Dec-11 16:37:15)

Ahh. I Win7 I went into the connection settings, TCP/IP v4 DNS settings etc

http://img855.imageshack.us/img855/6495/dnsh.jpg

Didn't have any issues at the times mentioned.

It gets even stranger. I found this thread...

http://windowslivehelp.com/thread.aspx?threadid=daaa...

I have a Netgear DG834 like many of the people reporting similar problems in that thread. I changed the MTU like they suggested but it didn't work. When I changed it back to default it seemed to take ages to obtain an IP but when it did I was able to connect to MSN again. So far it's been working perfectly for several hours.

I have a DG834GT with MTU = 1492 and I have no trouble logging into Windows Live Messenger, which, I presume, is what you mean by MSN.

Yeah. On mine (v2) the defrault it 1458. It was sat to that when I was having problems, changed it to no effect, changed it back and now all is well.