sky192
@shawcable.net
| reply to LLigetfa
Re: [Help Me] MSNMessenger/MSMGS - Firewall Rules duplicated
all i know is my di-624 is junk, it cant handle p2p networks even if the port are forward, it disconnects sometimes when both pc are surfing the net, disconnects sometims while playing cs. and each version of frimware has its own problem.
next time i buy a router it wont be a d-link and i'm gonna spend abit more cash in hopes of a better quality router. |
|
LLigetfa
join:2006-05-15
Fort Frances, ON
| reply to alanbr
Well, I never advocated disabling UPnP and if you read the DLink FAQ, the key bit is "as well as your computers". If you only disable it on the router, it almost surely will destabilize it.
I too use UPnP for Messengerand was bit by the issue in this topic. My router was doing OK on 2.71 for a long time and only started to act up after I moved it. Since it was already in the toilet, I thought I'd give 2.76 a try. I have since back-rev'd it to 2.71, enlarged the vent holes and used long screws to stand it away from the wall for better airflow and it has stayed up for weeks. |
|
alanbr
join:2007-01-02
canada
2 edits | reply to LLigetfa
Hi LLigetfa
I need uPNP to run properly for my Messengers to work, so I cannot run with it turned off. Considering the router is sold by D-Link as uPNP compatible, I find it bizarre that I found this FAQ on the D-Link Canada site: »support.dlink.ca/supportfaq/Disp···Id=33721
As a consequence, I turned uPNP off to simply use it as a diagnostic method to see if the problem went away when uPNP was disabled : it didn't! It was never my intention to leave it turned off because as indicated above, I use it all the time.
Prior to the 2.76/2.75 experiences, I was running 2.71 Beta (like you are) and getting intermittent failures (...granted not as frequently as with 2.75/6).
So, I am going to try running on 2.59 for a while and see how it goes. As the router has been up now for two days, I am convinced that the problem is the router firmware, which means D-Link's Product Support (quick)"fix" of replacing the router hardware is a cop out to "resolve" problems without proper analysis and diagnosis (which I thought was the primary function of Tier 3 level support). While replacing the router may be effective from a cost perspective for D-Link, it does not bode well for long term customer loyalty or D-Link product satisfaction metrics. |
|
LLigetfa
join:2006-05-15
Fort Frances, ON
| reply to alanbr
said by alanbr  :I tried all of the following with firmware 2.75 version (as suggested by D-Link kb), none of which worked: -Disabling uPNP ... It is often reported that disabling UPnP destabilizes the router and as such it should be enabled, not disabled.
My router is stable on 2.71b10. ISTR that 2.5x lacked WPA2 support but it was along time ago. |
|
alanbr
join:2007-01-02
canada
3 edits | reply to sky192
The only P2P apps I run are MSN and Yahoo Messengers.
I have been trying to solve this problem of router rebooting over the last week. I have tried just about all I can find on the D-Link KB and I have talked to D-Link support staff, multiple times. Finally, I got past 1st level support, to "senior team support" (2nd level?), and after 3 more calls, I was finally referred to "Product Support" - the ultimate in D-Link support! This was basically limited to an immediate offer to replace my router. Only when I pressed him for a solution, did he suggest going back to firmware rev. 2.59 or 2.53, both of which he said were the most stable. I have installed 2.59  , and the router seems stable.
For the record, I tried all of the following with firmware 2.75 version (as suggested by D-Link kb), none of which worked:
-Disabling uPNP
-Disabling logging
-Enabling WAN-side ping
-Using static IPs for LAN-side PCs
-Setting the ethernet card to 10mbps (instead of auto-negotiate)
-Using the documented router crash recovery procedure
And lastly, I tried running with both my MSN and Yahoo Messengers unloaded, and with Wireless capability disabled. Nothing solved the router rebooting problem with the 2.75 release. |
|
sky192
@on.ca
| reply to alanbr
dont know if this helps but this is a site i use to configue the ports. also i dont know much about this stuff, just know abit since seems like theirs always a new problem coming up with my dlink router.
»www.portforward.com/english/rout···ndex.htm |
|
sky192
@on.ca
| reply to Talon88
are you using any programs that use p2p networks or multiple connections since i know when i used the older version, i had problems with it disconnecting every 20 mins. even after opening up the right ports.
check the log and note whats running when it crashes might help to find a solution.
so far mines working good but i haven't really put it to the test. |
|
Talon88
The One
join:2003-08-13
Toronto
 ·Bell Sympatico
| reply to alanbr
:::
Do you use "Talon Crash Recovery" to flash?
Do you "Reset to Factory Default" after Flash?
Do you Manually input all the setting after Flash?
Try....!! May help....!
:::
said by alanbr :Thanks Sky (and Talon).
--
[=Talon88=] @ Bell DSL 5M (Rogers HiSpeed So Slow, Cut. Don't Use Rogers Internet!)
»D-Link FW update "Talon88 Crash Recovery" Step by
--
»[Info] Some Clue about DI-624 Reboot
--
»DI-624 Firmware update w/ Crash Recovery Step by S (Old) |
|
alanbr
join:2007-01-02
canada
2 edits | reply to sky192
Thanks Sky (and Talon). I downloaded the 2.75 production release from the D-Link website and installed it last night. As you say, the repeated MSN Messenger firewall rules problem vanished and is not in that release. However, after running it for a little over a day now, I have found that with the 2.75 release that the router keeps dropping the ADSL link anywhere between every 5 minutes and up to 45 minutes  . This is really frustrating because I regularly use MSN Messenger for voice and webcamming to family in Europe. Needless to say, it falling over in a heap every few minutes like this does not work well for interactive communications! I do not believe it is my ADSL service because the router ADSL link light does not go out when the connection to the Internet is dropped (as indicated by the router reconnecting and my Messenger connections lost).
I will persevere for another day or so with 2.75... and if things don't get better, I guess it is back to the land of 2.71. Thanks everyone for all you help and suggestions - any other ideas most welcome.
p.s. I "file compared" D-Link's website's 2.75 production release with 2.75B2 on Lizzi's site and they are the same version (I couldn't find a way to decode the file headers of each so used FC...) |
|
sky192
@shawcable.net
| reply to Talon88
i installed v2.75B02, as talon recommeded so far it works. ty talon.
i downloaded it from,
»ftp://lizzi555.dyndns.org/Download/WLA···/Rev_C_H |
|
sky192
@shawcable.net
| reply to alanbr
i have the same problem, i talked to dlink and all the guy would do is ask me to check to see if i had the wan port in right and the wires connected. i told him the internet was fine then he asks me to go to 3 websites..... i kept telling him what the problem is!!!! but he avoided it and told me to call back later.
its something to do with the dlink firewall but right now i have it unhooked. and msn works fine with out the router in line.
but i wouldn't go back a firmware since then your gonna have to deal with more problems... |
|
alanbr
join:2007-01-02
canada | reply to alanbr
... I am really trying to avoid having to go backwards to 2.75 unless I have to. I will try that next, but I fear it will be the same problem and that I will end up being pushed back to 2.71. |
|
alanbr
join:2007-01-02
canada | reply to The Flash
Indeed, it is a upnp problem because my Yahoo messenger works fine - no firewall rules are created for its use. |
|
Talon88
The One
join:2003-08-13
Toronto
1 edit | reply to alanbr
:::
I just downgrade back to v2.75B02
for these few reasons......!
Firewall Rules duplicated Fixed.
::: |
|
Scree
In the pipe 5 by 5
join:2001-04-24
Mount Laurel, NJ
 ·Comcast
| reply to alanbr
MSN Messenger/Windows Live Messenger is typically great with UPnP, compared to other apps that just don't use the API right. So if Messenger is having an issue with the router, it must be due to a bug in the firmware update, unfortunately. May want to confirm this by putting on the previous firmware again. |
|
The Flash
You don't win friends with salad
Premium
join:2002-10-17
Toronto, ON | reply to alanbr
Looks like it's created by uPNP. |
|
alanbr
join:2007-01-02
canada
1 edit | I have just loaded FW rel. 2.76 into my DI-624C. Every time I start my PC, new firewall rules are established for (auto-started) MSN Messenger and its companion MSMSGS. Between them, approximately 6-7 firewall rules are created each time I start my PC boot, so after 5 boots I have around 30+ firewall rules automatically being created for the same two programs. Eventually, two problems occur: 1)MSN Messenger won't start and just sits there waiting for a port - this is no doubt because there are no more options for alternative ports and associated firewall rules; 2) firewall rules get duplicated, and duplicates (only) appear to get deleted/disabled/invalidated. I'm not concerned about problem 2 because this is just a side effect of problem 1.
I have been using MSN Messenger with the router for years - problem seemed to surface with FW 2.76 upgrade: I previously had 2.71 beta loaded. I do have uPNP turned on on the router (and enabled in my Win Home XP). Also running NIS 2006, with MSN Messenger/MSMSGS both permitted Internet access. XP firewall is off.
I have talked to D-Link technical support to no avail. They told me to talk to MSN... Attached is a partial screenshot of the Firewall page rules. Any help/ideas would be appreciated. Thanks. |
|
