Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gdbr]

I'm not sure if it's related to my DIR-655 (A2 Rev. 1.31NA), it might be a Windows Live Messenger 2009 bug as well, but I didn't find useful information elsewhere, including at Microsoft sites. So, as there's someone else having webcam problems (although with iChat), I've decided to give this forum a try.

My LifeCam has stopped working with Windows Live Messenger 2009 on calls outside the lan. It works perfeclty inside the lan, when I'm setting it up or with Skype (inside or outside the lan), which makes me think about some issue between msn and UPnP. I've changed no configuration recently, UPnP is active on router, NAT endpoint filtering is the router default (UDP address restricted and TCP port and address restricted) msn is included in Vista Ultimate x64 firewall exceptions... what else?

As far as I can remember, nothing has changed, but I can't tell for sure if this problem started just after I've upgraded to 1.31NA (I don't think so) or later on (I'd bet on this one). I can tell for sure there's no problem with 1.22 and earlier. Never needed to use any manual port forwarding.

Looking at the log I found this when I start msn and skype:

[INFO]   Sun May 31 14:02:26 2009   UPnP added entry 255.255.255.255 <-> [MY IP HERE]:33683 <-> 192.168.0.100:33683 TCP timeout:0 'Skype TCP at 192.168.0.100:33683 (881)'
[INFO]   Sun May 31 14:02:25 2009   UPnP added entry 255.255.255.255 <-> [MY IP HERE]:33683 <-> 192.168.0.100:33683 UDP timeout:0 'Skype UDP at 192.168.0.100:33683 (881)'

(...)

[INFO]   Sun May 31 14:01:58 2009   UPnP deleted entry 255.255.255.255 <-> [MY IP HERE]:42193 TCP
[INFO]   Sun May 31 14:01:58 2009   UPnP renew entry 255.255.255.255 <-> [MY IP HERE]:42193 <-> 192.168.0.100:42193 TCP timeout:0 'MSNMSGR'
[INFO]   Sun May 31 14:01:58 2009   UPnP added entry 255.255.255.255 <-> [MY IP HERE]:42193 <-> 192.168.0.100:42193 TCP timeout:0 'MSNMSGR'

It puzzles me why UPnP entry for MSNMGR is deleted right after being added. I've never looked at it before, so I can't tell if this is the default behavior, but it isn't the same with skype.

Msn diagnostics says everything is fine, always — no, really? what a surprise!

I've tried turning SPI off, loosing NAT enpoint restrictions, even setting DMZ for my computer, all without any success.

Does anyone have a clue?


Thanks in advance,
Gui

[gdbr]

Not a word?
Am I the only winner of a exclusive bug? What a joy...

[EddieZ]

Doers your internet gateway modem have the ports opened up? This does not happen automatically....

[gdbr]

Doers your internet gateway modem have the ports opened up? This does not happen automatically....

It's a Motorola Surfboard 5121 cable modem. Unfortunately, it has nothing to be set up regarding TCP/IP ports, just signal and frequencies settings — I checked it long, long ago, before this problem showing up.

Besides, my ISP doesn't block any port. If they did, I bet I wouldn't get hundreds of blocked UDP and TCP packets and requests all the time at random, at a variety of ports, in the router log. Nor would be able to access my box from outside the lan (remote desktop, ftp, etc.). Anyway, UPnP works fine with everything (Skype, uTorrent, Teredo, eMule, etc.), except, appearently, msn. I don't understand why UPnP entries are beind created and deleted soon after, and that's the only reason I could imagine so far preventing my webcam from working JUST with msn calls — working with everything else — right out of the blue. It has always worked; then stopped.

That, or I have a weak imagination. I'm really puzzled.

[gdbr]

I've tried all I could, have loosen all the seetings, for nothing. So I did the ultimate test: took the router away and connected my computer directly to the modem. And got the same, no webcam working with MSN.

So I have to assume that it's not a router issue (not a exclusive one, at least). What still puzzles me is why UPnP entry is created for MSN, renewed and deleted, all in a row.

If anybody happens to get those logs too, please let me know.

Thanks!

[lizzi555]

Yes, this is quite normal with Skype and UPNP, here my log from this morning:

[INFO] Sun Jun 28 08:23:49 2009 UPnP added entry 255.255.255.255 <-> 77.21.xxx.xxx:17306 <-> 172.22.222.164:17306 TCP timeout:0 'Skype TCP at 172.22.222.164:17306 (909)'
[INFO] Sun Jun 28 08:23:47 2009 UPnP added entry 255.255.255.255 <-> 77.21.xxx.xxx:17306 <-> 172.22.222.164:17306 UDP timeout:0 'Skype UDP at 172.22.222.164:17306 (909)'
[INFO] Sun Jun 28 08:23:46 2009 UPnP deleted entry 255.255.255.255 <-> 77.21.xxx.xxx:17306 TCP
[INFO] Sun Jun 28 08:23:45 2009 UPnP deleted entry 255.255.255.255 <-> 77.21.xxx.xxx:17306 UDP
[WARN] Sun Jun 28 08:23:08 2009 A network computer (Lizzi2) was assigned the IP address of 172.22.222.164.

[gdbr]

Yes, this is quite normal with Skype and UPNP, here my log from this morning:

Hm... But it's not quite the same. It ends ADDING skype entries there (even if is starts deleting them), while it ends DELETING msn entries here. Anyway, skype is the one working great here (same there?).

[gdbr]

Ok, that's final: Microsoft has screwed it up! I've stripped out version 2009 and put 2008 back. Everything is working again (with the same weird UPnP add, renew and delete log entries — UPnP is a mistery to me).

Sorry for wasting everyone's time.