Nice job on the email to InTech...it's quite understandable that they cant do much i guess =\

I think it's better to start gentle but firm, give indication that if they are going to brush the issue aside, we wont stand down anymore... 

However if we start gently and they brush us aside, it will be quite hard and weird for us to suddenly go on rampage.

Even today, a BASIC network infrastructure like DNS which is used to translate normal webpage request into "internet language" (IP address) does not seem to respond well. This problem seems to be fixed at around 6.38pm. Below is a ping comparison to TM's DNS and a free, open source and public DNS system OPEN DNS.

PING TM DNS
C:\Documents and Settings\Andrew>ping 202.188.0.133 -n 25

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=11ms TTL=247
Reply from 202.188.0.133: bytes=32 time=10ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=14ms TTL=247
Reply from 202.188.0.133: bytes=32 time=13ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=21ms TTL=247
Reply from 202.188.0.133: bytes=32 time=17ms TTL=247
Reply from 202.188.0.133: bytes=32 time=16ms TTL=247
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.188.0.133:
  Packets: Sent = 25, Received = 10, Lost = 15 (60% loss),
Approximate round trip times in milli-seconds:
  Minimum = 9ms, Maximum = 21ms, Average = 12ms
PING OPEN DNS
C:\Documents and Settings\Andrew>ping 208.67.222.222 -n 25

Pinging 208.67.222.222 with 32 bytes of data:

Reply from 208.67.222.222: bytes=32 time=213ms TTL=55
Reply from 208.67.222.222: bytes=32 time=243ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=210ms TTL=55
Reply from 208.67.222.222: bytes=32 time=216ms TTL=55
Reply from 208.67.222.222: bytes=32 time=235ms TTL=55
Reply from 208.67.222.222: bytes=32 time=210ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=234ms TTL=55
Reply from 208.67.222.222: bytes=32 time=207ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=242ms TTL=55
Reply from 208.67.222.222: bytes=32 time=214ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=243ms TTL=55
Reply from 208.67.222.222: bytes=32 time=206ms TTL=55
Reply from 208.67.222.222: bytes=32 time=215ms TTL=55
Reply from 208.67.222.222: bytes=32 time=235ms TTL=55
Reply from 208.67.222.222: bytes=32 time=205ms TTL=55
Reply from 208.67.222.222: bytes=32 time=211ms TTL=55

Ping statistics for 208.67.222.222:
  Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 205ms, Maximum = 243ms, Average = 217ms

------------------------------------------------------------------------------------------------------------------------------------