View Single Post
  #1 (permalink)  
Old July 15, 2009, 08:03 PM
geokilla's Avatar
geokilla geokilla is offline
Hall Of Fame
F@H
 
Join Date: Aug 2008
Location: Toronto
Posts: 3,635

My System Specs

Default BT Kills Windows Live Messenger

Every time I have BT running on my side computer, I get disconnected from Windows Live Messenger on my own computer. Also even if I don't have BT running, every once in a while I will randomly get kicked out of WLM or not be able to send and receive instant messages, even though my Internet would still be working perfectly fine.

I'm using the latest version of DD-WRT, build 12476M a WRT54GSv7. I have BT running on a side computer with its ports forwarded and UPnP enabled. I also have QoS enabled and have the BT's computer's priority set to bulk in QoS. My own computer has the QoS priority set to Express.

According to the UPNP page, I do not have any WLM ports forwarded. I do have some BT ports forwarded in the UPnP page, despite already having Port Forward setup.

I opened WLM as well and went to the connections tab on the left. It always gives me the following connection status:
Code:
You are directly connected to .NET Messenger service.

You are connected to the Internet through a wired network connection.

You are connected to the Internet through a UPnP port restricted NAT. (Administrator)
It doesn't matter which firmware I use or whether I'm downloading or not. WLM will always say that I have a UPnP port restricted NAT.

When I directly connect my computer to the modem, thus bypassing the router, my ports aren't blocked and everything's fine. WLM says:

Code:
You are directly connected to .NET Messenger service.

You are connected to the Internet through a wired network connection.

You are connected to the Internet using a direct connection. (Administrator)
__________________
Reply With Quote