Help - Edimax Router Set Up or General Problem?

[#1]

not at all, its a DNS resolvement issue, the starting MS on the tracert/pings are ok yes, but when it hits the hunderds this is not, i work as an IT analyst its deffo a networking issue somewhere down the line, I'm currently and on a default profile because my IP profile hasnt been supplied yet by BT so im hoping once this is sortted the issue will resolve, only time will tell. The reason i know its somewhere on the network is speedtest.net used to work and just stopped, yet nothing changed my end.  
If you look at the MS on them closely and check what hop its on, generally takes effect when it leaves PN and joins any other. Which again leaves me to believe its not my end. Although i see there was traffic shaping/managment issues previously which maybe is effecting it ?

[#2]

How can it be a DNS issue when an IP address has been returned? I agree with fourfourdevon I can visit all the sites but can't ping or do a trace

[#3]

Quote from: Nemesis

not at all, its a DNS resolvement issue, the starting MS on the tracert/pings are ok yes, but when it hits the hunderds this is not, i work as an IT analyst its deffo a networking issue somewhere down the line

And I'm a network engineer, and it most positively, definitely is not a DNS issue, by the time you you start to see the trace route happening you have already resolved the DNS names, if you were having a DNS issue for those sites the trace route wouldn't even start.
Apart from reporting that you can't access the sites properly, everything, that's EVERYTHING else you've posted is EXACTLY the way it is designed to work.
What you say about "MS" and leaving PN's network doesn't make sense to me, but lets deconstruct one of your trace routes.
2 ms     1 ms     1 ms  192.168.2.1 - This is your router, physically on your network, and thus the replies from it are received within 1 to 2 ms, no name is given because you don't have DNS on your network giving out rDNS names for local addresses
44 ms    46 ms    44 ms  lo0-central2.pcl-ag04.plus.net [195.166.128.242] - This is your first sight of Plusnet's network, 44ms to 46ms is all very normal, a name is given because PN do have rDNS names setup
43 ms    44 ms    42 ms  gi1-12-421.pcl-gw01.plus.net [84.92.6.232] - More Plusnet, see above
43 ms    43 ms    42 ms  po4.pcl-gw02.plus.net [212.159.1.129] - More Plusnet, see above
77 ms    45 ms    43 ms  195.50.122.129 - Your traffic leaves Plusnets network and joins the Level 3 network, level 3 are a major wholesale transit provider, but for some reason this IP doesn't have a rDNS name, and looking at the times of the reply I think is perhaps in the same building as the Plusnet network, the spurious spike of 77 ms sometimes happens and can be ignored.
43 ms    43 ms    43 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97] - your traffic has now hit Level 3's core UK network in London and is about to be sent to
112 ms   111 ms   112 ms  ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74] - New York, this is cleary quite a fast route as its only adding ~70ms to latency, when last time I did a check of this, transatlantic traffic normally received a ~80ms addition to the latency
113 ms   112 ms   112 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18] - More New York Level 3
112 ms   117 ms   113 ms  ae-1-51.edge2.NewYork2.Level3.net [4.69.138.195] - More New York Level 3
110 ms   112 ms   111 ms  MICROSOFT-C.edge2.NewYork2.Level3.net [4.71.190.2] - Still New York Level 3, but we've hit an edge device dedicated to Microsoft transit
11   112 ms   112 ms   112 ms  209.240.199.194 - OK, so now we hit Microsofts network, against still in New York, and probably in the same building as the level 3 stuff
12   181 ms   180 ms   182 ms  ge-7-0-0-0.co1-64c-1b.ntwk.msn.net [207.46.40.90] - Still M$ network, but weve lept up ~60ms, so weve probably transited from the US east coast (new york) to the US west coast (seattle)
13   199 ms   197 ms   198 ms  ge-0-1-0-0.wst-64cb-1b.ntwk.msn.net [207.46.43.185] - OK, we bounce around M$ network
14   187 ms   187 ms   197 ms  ge-4-3-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.46.162] - again
15   185 ms   185 ms   187 ms  ten1-1.tuk-76c-1b.ntwk.msn.net [207.46.46.21] - again
16   186 ms   184 ms   185 ms  po15.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.35.138] - again
And then no more, after that M$ are no longer interested in letting you see their network, in all probability the machine that refuses to reply is the one you want as most network engineers wont turn off basic tools like trace route and ping as it would make their life very difficult, however some server administrators do turn them off as they believe it lessons the load on the server.
So basically, Plusnet did its job, Level 3 did it's job, and M$ did most of its job, and what you are seeing is NORMAL, TO BE EXPECTED and NOTHING TO BE EXCITED ABOUT.

[#4]

http://community.plus.net/forum/?topic=86544.msg729540
I can't claim any credit for this, but problem sorted and I'm a happy bunny.