>>>>>>>>For the last week or so, when I try to view all messages in a thread, UT just hangs and produces no results.
>>>>>>>>
>>>>>>>>Thanks,
>>>>>>>>
>>>>>>>>dg
>>>>>>>
>>>>>>>What is this thread ID? It works OK for me in IE, but there may be a specific thread causing troubles.
>>>>>>
>>>>>>
>>>>>>I'm using FireFox 3.6.6 and am updating to 3.6.12... I just used an old IE 6.0... and it took almost 4 minutes to load this thread. It is any thread that I try to view in it's entirety. Will check again after the FF update...
>>>>>>
>>>>>>dg
>>>>>
>>>>>Strange. Works OK for me in IE 8. IE 6 is too old - may be you'd like to upgrade. It took me ~1sec. to open this thread.
>>>>
>>>>
>>>>
>>>>Just installed the FireFox upgrade, removed all from the cache and re-booted. It took over 90 seconds to load all messages for this thread. This is a marked degrade from prior performance. And no real improvement for having taken these steps.
>>>
>>>Are you using an antivirus package that checks web links?
>>
>>Al are you suggesting that UT is riddled with a virus? hehehehe! Just kidding; not using any av package.
>>
>>As for other threads, it's all... even a current thread with only several messages.
>>
>>Different IP? I have a Verizon air card and get a dynamic ip with each login.... no difference.
>>
>>I'll just be glad to know that I'm so special.... the only one in the universe with such a condition!
>>
>>dg
>
>
>
>ps. Just checked a fairly active thread from the "View all messages starting from this thread only..." and it populated 10plus messages rapidly.

Well, if you want to get technical you could run traceroute to the UT and see if there are any links with high latencies:

* In a command (CMD) window, run
tracert levelextreme.com

My results are:

Tracing route to levelextreme.com [205.205.57.4]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2     *        *        *     Request timed out.
  3    12 ms     9 ms    10 ms  rd1wh-ge14-0-0-1.vc.shawcable.net [64.59.159.35]

  4    10 ms     7 ms     9 ms  rc2wh-tge0-15-0-0.vc.shawcable.net [66.163.69.17
3]
  5    14 ms    14 ms    11 ms  rc4wt-pos0-0.wa.shawcable.net [66.163.76.154]
  6    14 ms    13 ms    17 ms  rc5wt-tge0-15-0-0.wa.shawcable.net [66.163.68.45
]
  7    19 ms    16 ms    82 ms  xe-11-0-0.edge1.Seattle3.Level3.net [4.71.152.25
]
  8    14 ms    13 ms    16 ms  ae-14-51.car4.Seattle1.Level3.net [4.68.105.5]
  9    16 ms    15 ms    13 ms  mci-level3-oc48.seattle1.Level3.net [4.68.63.230
]
 10     *       14 ms    16 ms  0.so-1-2-0.XT2.SEA1.ALTER.NET [152.63.106.6]
 11    92 ms    92 ms    93 ms  0.xe-0-0-0.XT4.MTL1.ALTER.NET [152.63.128.46]
 12    92 ms    90 ms    92 ms  192.ATM6-0.GW1.MTL2.ALTER.NET [152.63.130.69]
 13    92 ms    92 ms    92 ms  transfo4-gw.customer.alter.net [216.95.146.106]

 14    93 ms    94 ms    94 ms  205.205.57.4

Trace complete.

My trace is typical. Latencies are quite short to my ISP (Shaw), to Level3 in Seattle, and even to Alter.Net in Seattle (under 20 milliseconds [ms]). The bulk of the latency/delay (90 - 94 ms) is within Alter.Net, going between Seattle and Montreal.

Some of the links will time out because they don't respond to a tracert (those marked with a *) but that's normal and won't affect your connection. Of the links that do report a time, hopefully none are much over 100 milliseconds. My understanding is cellular links can suffer from very bad latency, if you see any numbers like 300, 500 or even more milliseconds that's probably a big part of your performance problem.