Welcome to WebmasterWorld Guest from 126.96.36.199 , register , free tools , login , search , subscribe , help , library , announcements , recent posts , open posts Pubcon Website
My Messages PNG blocked in firewall Frank_Rizzo msg:4281055 5:53 pm on Mar 13, 2011 (gmt 0) I installed a new router a few weeks ago. Since then I noticed that the My Messages Icon (yellow triangle, Exclamation mark) was not being shown. When I tried to view the source of the icon [ ...] webmasterworld.com I got the router blocked website page. It turns out that if I set the router to Close IM Ports then the router will block based on keyword mymsgs. Any URI which has mymsgs in it will be blocked. I don't know if others have this problem but it happens with this netgear router.
Frank_Rizzo msg:4286611 12:48 am on Mar 24, 2011 (gmt 0)
I can't believe I am the only one with this problem. It is impossible for me to read the 'my threads link'. Any chance the filename could be changed? m y m s g s.png is the problem. Even just posting that filename without the spaces black holes me.
Fotiman msg:4286648 1:57 am on Mar 24, 2011 (gmt 0)
Have you tried contacting Netgear? Sounds like their problem. engine msg:4286812 12:17 pm on Mar 24, 2011 (gmt 0)
Sorry to hear that. I'm not sure changing the filename would even solve that. Could it be ad blocking software and seeing it as some kind of ad? coopster msg:4287291 11:08 am on Mar 25, 2011 (gmt 0)
Does the router's firmware require an update? Frank_Rizzo msg:4287308 11:52 am on Mar 25, 2011 (gmt 0)
It's the way the router tries to prevent users getting around blocked IM ports. As a secondary blocking mechanism it looks for keywords. If it sees m y m s g s in the URI it totally blocks the page. Found a solution in another place, which suggests adding a rule to ALLOW the banned name. Haven't tried it yet but it's one for the record, i.e. some routers blocking keywords: could drive webmasters crazy if visitors say "can't access a page" Fotiman msg:4287362 1:22 pm on Mar 25, 2011 (gmt 0)
If it were me, I would report that as a bug to Netgear. It sounds like their "solution" is buggy.