I'm using XP Pro.
Again, if the problem was local to my machine it almost certainly wouldn't have worked at home. Also, tracert's to other sites complete successfully. BUT...interesting development when I was checking the tracert - the first hop on any tracert always times out. After the first it works fine (example below to good old bbc.co.uk). Tried half a dozen different traces and all the sam - 1st fails but afterwards works normally. I'm sure this is highly significnt but I have nfi what it means lol
------------------TRACERT---------------------
C:\Documents and Settings\George>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.228.154]
over a maximum of 30 hops:
1 * * * Request timed out.
2 215 ms 151 ms 149 ms gb-bir-c-r2-ge60.inet.ntl.com [80.1.208.194]
3 159 ms 149 ms 160 ms gb-lth-c-r1-pos150.inet.ntl.com [80.1.209.109]
4 157 ms 149 ms 155 ms gb-lth-c-r2-pos00.inet.ntl.com [80.1.209.222]
5 158 ms 149 ms 160 ms gb-ldk-c-r1-pos150.inet.ntl.com [80.1.209.121]
6 158 ms 149 ms 155 ms pop-ic-1-ge-030-0.inet.ntl.com [62.253.184.253]
7 166 ms 149 ms 155 ms pop-bb-a-ge-700-0.inet.ntl.com [62.253.184.242]
8 166 ms 166 ms 154 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 162 ms 166 ms 155 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 171 ms 155 ms 155 ms 212.58.238.129
11 166 ms 155 ms 155 ms 212.58.238.33
12 166 ms 155 ms 155 ms pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
13 161 ms 155 ms 158 ms bogons.mh.bbc.co.uk [212.58.228.154]
Trace complete.
------------------------------------------------------------------
__________________
OK, given this a bit more thought and messed around a little more, now havint the following thoughts I could do with comments on:
1 - Based on the facts that this site and game seem to be the only problem ones, plus it all works fine on my home connection...I think I can eliminate my own machine as the problem?
2 - The fact that tracert doesnt manage even a single hop suggests it is also unlikely that the destination site is at fault (eg if my IP range was blocked) - wouldn't tracert still work until it got to the faulty/blocking point?
3 - Gathering all this together, my personal suspicion at present is that the problem is caused by some sort of routing problem. The DNS is returning the correct IP for the site but it appears the routing to that IP is..well...broken

. I've exhausted my limited knowledge of how all this works however - I don't know where this routing information comes from or how (or even if) I can force my computer to go elsewhere to find the correct info...
HELP