ns1.jaring.my-----161.142.201.17
ns2.jaring.my-----192.228.188.61
ns3.jaring.my-----161.142.227.17
ns4.jaring.my-----161.142.212.17
ns5.jaring.my-----61.6.38.139
ns6.jaring.my-----192.228.128.16

Those are Jaring's DNS servers, i think jaring block TMNet users, but it takes like 20/30 mins before it kicks you out, just switch the server. Its just a temporary fix if u really cant access thru tm's DNS

OR u can use

ns2.p1.com.my-----122.255.96.133

P1 Wimax DNS(secondary). I'm not providing the main DNS so that we do not overcrowd their service.


C:\Documents and Settings\Andrew>ping 122.255.96.133 -n 8

Pinging 122.255.96.133 with 32 bytes of data:

Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=10ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245
Reply from 122.255.96.133: bytes=32 time=11ms TTL=245

Ping statistics for 122.255.96.133:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms


This post has been edited by andrew9292: Jun 8 2009, 05:52 PM

i changed to

ns2.p1.com.my-----122.255.96.133 (P1 Wimax Secondary DNS)

this is what i get....

edit-deleted quote

hey, if possible...take down the 1st DNS, as it is P1's primary DNS...if we all use the primary DNS, it will be overloaded and end up like streamyx's DNS. just use the 2nd one should be good enough

edit- thanks for taking it down

This post has been edited by andrew9292: Jun 8 2009, 07:17 PM

OMG...did we just blew up their secondary DNS??? holy...



edit: okay its working again now...LOL scary man


edit again...sorry: secondary p1wimax dns seems to be sluggish now and randomly stops responding. I'm switching to opendns

This post has been edited by andrew9292: Jun 8 2009, 07:24 PM

their secondary DNS seems to be sluggish and sometimes not responding, i'm switching to opendns

Weird situation, speed was slow. THEN....

RADIUS server down, DNS unreachable...

But when using other DNS, speed was at maximum...


Any hypothesis on what happened? ...

Mine (hater's view) : Because RADIUS had failed and DNS overload, TM engineers panic and thought that by turning off the throttling will help improve the situation. but it did not. however, we the SMART ones used other DNS and managed to take advantage of their "off-throttling"

OR

(positive view)
They really are finally giving us what we pay for ; )

This post has been edited by andrew9292: Jun 8 2009, 07:46 PM

You want to know why we are getting fast speed

It's because the whole of Malaysia Streamyx users got DNS problem, how many of them will know it's a DNS problem if they do not come here and see our threads? Those people will only know if it get through TM's call center and are informed by TM. Come on, even in the main page of this forum,, it says..."Most users ever online was 4,779 on May 4 2009, 10:46 PM"

Malaysia has how many thousands/million? of streamyx users. We are getting fast speed because we are switching to another DNS. While the rest that dont know its a DNS problem will not be able to connect and use the bandwidth. Thats why, we are actually using the extra bandwidth that is left by those users that cant connect or did not change their DNS

TM's DNS is up and running fine as for now (12pm)



Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Andrew>ping cns3.tm.net.my

Pinging cns3.tm.net.my [202.188.0.133] with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=17ms TTL=247
Reply from 202.188.0.133: bytes=32 time=13ms TTL=247
Reply from 202.188.0.133: bytes=32 time=10ms TTL=247
Reply from 202.188.0.133: bytes=32 time=11ms TTL=247

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 17ms, Average = 12ms

C:\Documents and Settings\Andrew>ping cns2.tm.net.my

Pinging cns2.tm.net.my [202.188.1.5] with 32 bytes of data:

Reply from 202.188.1.5: bytes=32 time=11ms TTL=247
Reply from 202.188.1.5: bytes=32 time=12ms TTL=247
Reply from 202.188.1.5: bytes=32 time=12ms TTL=247
Reply from 202.188.1.5: bytes=32 time=11ms TTL=247

Ping statistics for 202.188.1.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

you can always set the DNS at your WinXP...it's the same thing with router config.....

infact my router cant config DNS so i have to config it at my comp...

This post has been edited by andrew9292: Jul 28 2009, 03:58 PM

Just config it on your computer, if you can load pages after that, means the DNS is working.

http://www.infoarch.net/s_broadband.htm ... a page of all DNS to use in this region

HOWEVER, Jaring DNS has blocked non Jaring users, do using Jaring DNS you will not get good conenctivity. P1 DNS also, only their 1st DNS responds to non P1 users now. all other p1 DNS do no respond to outsiders.

that is because that website blocks ICMP pings, same goes with www.hotmail.com....

If a website is pingable, but shows some packet loss, then it has problems

If a website is pingable and show 100% PL, but accesible, that means it is blocking pings.

Ig a website is not pingable and canot access..means its DOWN

yes but only a very small amount of webpages practice this method.

---

Added on August 1, 2009, 12:00 pmYes, just input 202.188.1.5 into the box @ preferred DNS server when you change your DNS through computer. It will be then used as the primary DNS for your connections.

Then you can also input another non-TM DNS (like OPENDNS) at the alternate DNS server box.

This post has been edited by andrew9292: Aug 1 2009, 12:00 PM

nice DNS there... thanks... using it now...

but it blocks ICMP pings, so we wont be able to tell if it's having problems or not... and also to check the latency... =\