First a bit of history. For 2 or 3 months, experiencing slow, 'sticking' pageloads in all browsers. Unable to connect to remote webserver via FTP reliably despite changing computers, FTP client software. FTP port mode just about worked, Passive mode would not even connect most of the time. I was experiencing these problems for ages using a belkin router, and blamed that - so I bought the router listed above. No improvement.
Eventually noted that the router's WAN diagnostics interface was showing 'FAIL' for 'ping primary DNS server'. Tried to manually ping both the primary and secondary DNS servers via XP cmd interface, both failed - no reply.
Decided to untick the WAN configuration checkbox in the router for 'automatically assigned DNS servers', and replaced the DNS server addresses supplied by BT with addresses supplied by the 'OpenDNS' public DNS service.
Great improvement - FTP now working smoothly on both passive and port mode. Webpages loading much faster and no 'stalls'.
However, still sticks occasionally.
Looking in the TP-Link router's diagnostics interface, I see the two following failures:
If I run the diagnostics without specifying 'OAM F4', both of those tests appear to pass.
What gives? Do I have a fault somewhere that I can complain about and get fixed? Do I possibly have a setting wrong in my WAN connection details? I use the following connection details:
PPPoA VPI/VCI 0/38 UBR without PCR MTU 1492 IGMP enabled QoS disabled Encapsulation VC/MUX PPP user: [email protected] PPP password: BT (as per everyone else)
Are you using the router through a BT line? if you are BT will be able to sort this problem for you by sending the router an update that it sounds like it needs
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Sounds like you need to change the TP link router for a wireless Access Point or a range extender.
Who knows what goofing around BT does with their equipment.
I'm an electrical and electronic engineer (Iranian and Persian native
speaker) that had the same problem,exactly my modem went to death (just
power LED is ON) after upgrading from version 3 to 6 and I have
precisely similar TP-LINK TD-8901G ADSL2+ router but I found a great
"step by step" tutorial in a Russian website(in their forum) which
contributed me significantly; I hope it might help you too. [email protected] +989358817467 http://www.lan23.ru/forum/showthread.php?t=6859&page=1
The best way to resolve this one is to upgrade the firmware of your router, firmware is the software inside your router so better check the manufacturer's site for the latest firmware for it...
yeah i had that problem 2 days ago go to 192.168.254.254 and type in your user name and password click save settings and if you see the connect button press connect and if that doesn't work try getting a ball point pen and press down on the reset button for 5 seconds and it will have a flashing light on the last thing and that means it's powering up try it again until 3 solid lights come on and the last thing is flashing
this the web site download the user manual from this site what ur configuration go thought it i think you get it and maybe the problem in the pppoa line its working or not just check it
please call dlink tech support at 877-453-5465. just an advise on how to handle the call when you reach dlink tech support (agent); do not agree to call back after you troubleshoot with them (they'll be giving you a case id reference# and be advising you to check your pc or call "who" and call them back to continue the troubleshooting). insist to the agent that he need to resolve the problem asap (by the way, agents are not allowed to drop the call or they'll be dead-history!). and if the agent still insisted you to call back, ask for a "senior level technician" to finish the job (escalate the problem). fyi: dlink tech support handling time to resolve a call is 15 to 18 minutes only. if you reach that 15-18 minutes (max) time the agent will think of a way for you to call back (advising you to check with your pc manufacturer, check with your ISP, call microsoft to update your software, etc... non-sense!) they need to do this in order to reach their handling time (agents need to reach 21 to 25 billable calls, and billable calls are "solution provided", "resolved", and "dropped call"). ---- believe me, i was one of them and repented.
Go to the "Security" option and click to "Incoming" rules. By default, all WAN traffic blocked, but you can create "ALL" rules, just left the source and destination ip address and port blank. This means ALL ports and ip like the firewall off.
×