home about bayan products customer support bayan cares
 
Welcome Guest Search | Active Topics | Members | Log In | Register

Medyo Unstable after Basyang Options · View
Xentar
Posted: Tuesday, August 03, 2010 3:07:17 PM
Rank: Advanced Member
Groups: Member

Joined: 10/20/2008
Posts: 348
Points: 856
Maganda Nga Connection mo. Youtube Problem ganyan talagayan sa Bayan, try mo download Add-on Sa Firefox "Mytube" sana mag improve kahit maliit lang

Since Bingyan mo ako ng Tracert .
Eto Akin Dalawang Connection Hindi Normal. May timeout sa Hop 5 , Mataas Ping naka stand alone Connection

Click Muna lang para Lumaki








jps001 wrote:
Mikos wrote:
For surfing normal ang tracert readings mo. I said SURFING... Baka me mga mag react na naman diyan na di nagbabasa kung ano ang naipost.

jps001 wrote:
Xentar wrote:
Bro Pwede ka dito post ng Tracert Facebook,. baka same tayo problem


Tracing route to facebook.com [69.63.189.16]
over a maximum of 30 hops:

1 13 ms 15 ms 13 ms lo1.pe2.leg.bayan.net.ph [202.78.96.58]
2 34 ms 22 ms 21 ms 121.96.0.218.bti.net.ph [121.96.0.218]
3 25 ms 24 ms 22 ms 121.96.0.218.bti.net.ph [121.96.0.218]
4 23 ms 28 ms 22 ms 121.96.1.105.BTI.NET.PH [121.96.1.105]
5 21 ms 23 ms 24 ms 7600-GW4.bti.net.ph [202.78.97.195]
6 216 ms * * facebook.com.any2ix.coresite.com [206.223.143.16
1]
7 289 ms 295 ms 290 ms xe-1-3-0.br01.dfw1.tfbnw.net [204.15.21.7]
8 330 ms 315 ms 346 ms ae1.br01.mia1.tfbnw.net [74.119.77.73]
9 332 ms 324 ms 321 ms xe-8-3-0.bb01.iad2.tfbnw.net [74.119.77.75]
10 316 ms 313 ms 321 ms ae1.dr01.ash2.tfbnw.net [74.119.76.77]
11 317 ms 318 ms 321 ms eth-18-1.csw01a.ash2.tfbnw.net [74.119.76.111]
12 317 ms 315 ms 316 ms www-11-01-ash2.facebook.com [69.63.189.16]

Trace complete.


ano ba to, pag tanghali hanggang mga 10PM ng gabi walang kwenta mag youtubeBrick wall


oo kasi gabi na yan ng kinuha ko^^

pag tanghali hanggang gabi pangit talaga Youtube experience ko Y_Y
jps001
Posted: Tuesday, August 03, 2010 9:28:58 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
eh mga 11:30PM or 12AM ko na yata yun kinuha kayo ayun maganda yun connection. Isa lang nakikita ko, may sumpong si bayan. may mga times na ok ang connection kahit anong oras pa yan at maraming time naman na pag madaling araw lang ang magandang connection.



Xentar
Posted: Tuesday, August 03, 2010 9:55:07 PM
Rank: Advanced Member
Groups: Member

Joined: 10/20/2008
Posts: 348
Points: 856
Sa tingin ko maramin atang connection na route dahil sa effect ni basyang, pag maayos na yan babalik diin sa normal, kung may ibang bagyong darating hindi rin gano karami problema kagaya dinulot ni basyanag, Sana.

Mayroon kasi dito Reclamo sa Forum then pagbalik niya, ok na yong Net. Kung tama ako area niya may inayos so sa area diin yon maganda yong connection.

Sana Yong Bayantel May Advisory: "We are Currently Restoring Our Service to Normal due to Bagyo Basyang" kagaya ginagawa ng ibang Telecoms
jhonny
Posted: Wednesday, August 04, 2010 12:25:50 PM
Rank: Newbie
Groups: Member

Joined: 8/4/2010
Posts: 2
Points: 6
Location: Davao City
Ganun rin kami dito sa Davao, yung dati na smooth na garena session ngayon kahit sa Bayantel rooms kami sumali grabe ang lag, kapag kami naman ang nag create ng isang game session, sila naman ang lag, kahit sa ibang online games tulad ng crossfire at warrock ganun din grabe ang lag halos isang linggo na. Minsan pa mawawalan ng net tapos babalik ulit, kahit isang pc lang ang ginagamit ganun pa rin

Speed test

1st try


2nd try


3rd try




Tracert


Ilang beses na ito namin itinawag, first na pinagawa sa amin eh yung bypass yung router, nagpagawa ng dialer tapos yun seems ok naman tapos sabi nila baka sa config daw ng router ang problema at hindi na daw nila sakop yun, tinanong ko kung pwede maka affect yung recent events (yung bagyo) sabi niya hindi naman daw, nung unang beses na sabi nila na magpapadala sila ng techinician eh inabot na ng 2 days bago may dumating, nung dumating nag speedtest sa iexplorer, gumamit ng proxy (proxy.dvo.bti.net.ph) lumabas ang mga speeds na naglalaro sa 1.5, 1.4, 1.3 (isang pc lang ang ginagamit nung time na yun) nag try mag open ng ibang pc at nagstream, expected na bumababa talaga ang speed kasi madaming pc ang nakashare pero iba talaga quality ng connection kesa sa dati kasi kahit lahat ng 8 pc ang nakaconnect eh walang ganung klaseng lag. Could this be a problem not only sa side ng bayan kundi sa side din ng mga servers ng mga local online games?

Ewan ko lang ha I know this might not the right place to rant pero yung technician na ipinadala nila walang maisuggest or masabi na posibleng problema ng connection namin, ni ayaw rin magtanong, na kesyo bumalik na eh nagmamadali na umalis at sabi na tumawag na lang daw kami ulit kapag nag kaproblema na naman which is nangyayari ulit ngayon, syempre hindi lahat ng nagtatayo ng icafe eh marunong sa computer particularly sa networking. Mahirap ang ganito kasi relied na sa internet ang mga customers ng shop at kapag walang net, walang customer na nagtyatyaga sa offline games, walang customer walang income, walang income walang pang bayad sa monthly dsl.

Siguro dapat may official statement or advisory ang Bayantel pero naiisip ko kung meron man silang inaayos, kaya siguro ayaw nila maglabas ng advisory na maaring ma interrupt ang services nila due to repair eh baka bahain sila ng mga tawag from different customers, pero honestly mahirap mangapa sa dilim kasi napakadaming factors eh.
Mikos
Posted: Wednesday, August 04, 2010 1:04:36 PM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
If you are having prblems with your connection, then by all means start your own thread.

This thread is dedicated to the concern of jps001. If we continue to discuss your concern here, it will drown and mislead already the development of the thread of jps001. The post would have been highly appreciated if you just focus your inputs on the possible causes of jps001's problem, instead of mentioning and posting your own screenshots and caps along side your own problems. We are free to start our own thread and discuss our problems there. But in the threads of other fourmers, it is only moot and academic that we focus on their concerns unless the thread is opened by the thread starter to all like in a survey thread or opinion seeking thread. In cases where it is not opened to all, the discussion is limited only to the concern of the one starting the thread.

While I understand you and jps001 have the same problems, it would be to the efficiency of the forum if we follow the rules outright.

Please read the rules. Thank you.


jhonny wrote:
Ganun rin kami dito sa Davao, yung dati na smooth na garena session ngayon kahit sa Bayantel rooms kami sumali grabe ang lag, kapag kami naman ang nag create ng isang game session, sila naman ang lag, kahit sa ibang online games tulad ng crossfire at warrock ganun din grabe ang lag halos isang linggo na. Minsan pa mawawalan ng net tapos babalik ulit, kahit isang pc lang ang ginagamit ganun pa rin

Speed test

1st try


2nd try


3rd try




Tracert


Ilang beses na ito namin itinawag, first na pinagawa sa amin eh yung bypass yung router, nagpagawa ng dialer tapos yun seems ok naman tapos sabi nila baka sa config daw ng router ang problema at hindi na daw nila sakop yun, tinanong ko kung pwede maka affect yung recent events (yung bagyo) sabi niya hindi naman daw, nung unang beses na sabi nila na magpapadala sila ng techinician eh inabot na ng 2 days bago may dumating, nung dumating nag speedtest sa iexplorer, gumamit ng proxy (proxy.dvo.bti.net.ph) lumabas ang mga speeds na naglalaro sa 1.5, 1.4, 1.3 (isang pc lang ang ginagamit nung time na yun) nag try mag open ng ibang pc at nagstream, expected na bumababa talaga ang speed kasi madaming pc ang nakashare pero iba talaga quality ng connection kesa sa dati kasi kahit lahat ng 8 pc ang nakaconnect eh walang ganung klaseng lag. Could this be a problem not only sa side ng bayan kundi sa side din ng mga servers ng mga local online games?

Ewan ko lang ha I know this might not the right place to rant pero yung technician na ipinadala nila walang maisuggest or masabi na posibleng problema ng connection namin, ni ayaw rin magtanong, na kesyo bumalik na eh nagmamadali na umalis at sabi na tumawag na lang daw kami ulit kapag nag kaproblema na naman which is nangyayari ulit ngayon, syempre hindi lahat ng nagtatayo ng icafe eh marunong sa computer particularly sa networking. Mahirap ang ganito kasi relied na sa internet ang mga customers ng shop at kapag walang net, walang customer na nagtyatyaga sa offline games, walang customer walang income, walang income walang pang bayad sa monthly dsl.

Siguro dapat may official statement or advisory ang Bayantel pero naiisip ko kung meron man silang inaayos, kaya siguro ayaw nila maglabas ng advisory na maaring ma interrupt ang services nila due to repair eh baka bahain sila ng mga tawag from different customers, pero honestly mahirap mangapa sa dilim kasi napakadaming factors eh.




FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


The Forum is NOT an Online Technical Support.
For your DSL/Phone concerns please call the hot lines FIRST before posting it in the Forum.
This includes requests for port resets, DSL connection footprints (ATT and SNRs), requests for technicians and repairs.
Please read the Bayan Forum Rules.


If the post is in size 6 or big sized font, it means I am addressing you as a moderator. If the post is in the default size, it means I am Mikos the plain subscriber.


Bayan Forum Rules
jps001
Posted: Monday, August 09, 2010 2:09:56 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
ano Bayan!?
ano to lokohan na?

Request timed out.
Reply from 74.125.71.147: bytes=32 time=460ms TTL=56
Reply from 74.125.71.147: bytes=32 time=956ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=348ms TTL=56
Reply from 74.125.71.147: bytes=32 time=731ms TTL=56
Reply from 74.125.71.147: bytes=32 time=358ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=481ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=614ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=747ms TTL=56
Reply from 74.125.71.147: bytes=32 time=1130ms TTL=56
Reply from 74.125.71.147: bytes=32 time=861ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=358ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=1180ms TTL=56
Reply from 74.125.71.147: bytes=32 time=1497ms TTL=56
Reply from 74.125.71.147: bytes=32 time=1061ms TTL=56
Reply from 74.125.71.147: bytes=32 time=803ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=1167ms TTL=56
Reply from 74.125.71.147: bytes=32 time=1188ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=578ms TTL=56
Reply from 74.125.71.147: bytes=32 time=2040ms TTL=56
Reply from 74.125.71.147: bytes=32 time=387ms TTL=56
Reply from 74.125.71.147: bytes=32 time=249ms TTL=56
Reply from 74.125.71.147: bytes=32 time=401ms TTL=56
Reply from 74.125.71.147: bytes=32 time=391ms TTL=56
Reply from 74.125.71.147: bytes=32 time=738ms TTL=56
Reply from 74.125.71.147: bytes=32 time=499ms TTL=56
Reply from 74.125.71.147: bytes=32 time=267ms TTL=56
Reply from 74.125.71.147: bytes=32 time=452ms TTL=56


dapat putol putol din bayad namin -.-
steady ang ilaw ng DSL kaya maaaring sainyo nanggagaling ang problem at di sakin.
ilang araw lang ako pinatikim ng medyo "maayos" na connection pag umaga hanggang gabi tapos ngaun balik na sa "normal". ganito pala ang normal sa inyo. uulitin ko, pag madaling araw eh smooth ang connection ko at 99% of the time yan. alangan naman na palaging gagamit ako pag madaling araw para lang maganda surfing experience ko? di naman yata tama yan.


after a few minutes eto gumanda ng konti per mayat' maya ay balik na naman sa dati

Reply from 74.125.71.147: bytes=32 time=87ms TTL=56
Reply from 74.125.71.147: bytes=32 time=90ms TTL=56
Reply from 74.125.71.147: bytes=32 time=86ms TTL=56
Reply from 74.125.71.147: bytes=32 time=111ms TTL=56
Reply from 74.125.71.147: bytes=32 time=72ms TTL=56
Reply from 74.125.71.147: bytes=32 time=102ms TTL=56
Reply from 74.125.71.147: bytes=32 time=88ms TTL=56
Reply from 74.125.71.147: bytes=32 time=86ms TTL=56
Reply from 74.125.71.147: bytes=32 time=239ms TTL=56
Reply from 74.125.71.147: bytes=32 time=243ms TTL=56
Reply from 74.125.71.147: bytes=32 time=460ms TTL=56
Reply from 74.125.71.147: bytes=32 time=81ms TTL=56
Reply from 74.125.71.147: bytes=32 time=203ms TTL=56
Reply from 74.125.71.147: bytes=32 time=78ms TTL=56
Reply from 74.125.71.147: bytes=32 time=185ms TTL=56
Reply from 74.125.71.147: bytes=32 time=118ms TTL=56
Reply from 74.125.71.147: bytes=32 time=139ms TTL=56
Reply from 74.125.71.147: bytes=32 time=78ms TTL=56
Reply from 74.125.71.147: bytes=32 time=267ms TTL=56
Reply from 74.125.71.147: bytes=32 time=106ms TTL=56
Reply from 74.125.71.147: bytes=32 time=182ms TTL=56
Reply from 74.125.71.147: bytes=32 time=147ms TTL=56
Reply from 74.125.71.147: bytes=32 time=343ms TTL=56
Reply from 74.125.71.147: bytes=32 time=109ms TTL=56
Reply from 74.125.71.147: bytes=32 time=253ms TTL=56
Reply from 74.125.71.147: bytes=32 time=467ms TTL=56
Reply from 74.125.71.147: bytes=32 time=134ms TTL=56
Reply from 74.125.71.147: bytes=32 time=157ms TTL=56
Reply from 74.125.71.147: bytes=32 time=188ms TTL=56
Reply from 74.125.71.147: bytes=32 time=218ms TTL=56
Reply from 74.125.71.147: bytes=32 time=185ms TTL=56
Reply from 74.125.71.147: bytes=32 time=134ms TTL=56
Reply from 74.125.71.147: bytes=32 time=229ms TTL=56
Reply from 74.125.71.147: bytes=32 time=144ms TTL=56
Reply from 74.125.71.147: bytes=32 time=264ms TTL=56
Reply from 74.125.71.147: bytes=32 time=185ms TTL=56
Reply from 74.125.71.147: bytes=32 time=243ms TTL=56
Reply from 74.125.71.147: bytes=32 time=162ms TTL=56
Reply from 74.125.71.147: bytes=32 time=294ms TTL=56
Reply from 74.125.71.147: bytes=32 time=157ms TTL=56
Reply from 74.125.71.147: bytes=32 time=283ms TTL=56
Reply from 74.125.71.147: bytes=32 time=248ms TTL=56
Reply from 74.125.71.147: bytes=32 time=124ms TTL=56
Reply from 74.125.71.147: bytes=32 time=118ms TTL=56



jps001
Posted: Monday, August 09, 2010 4:17:52 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
CHEERS!!!

Reply from 74.125.71.147: bytes=32 time=522ms TTL=56
Reply from 74.125.71.147: bytes=32 time=207ms TTL=56
Reply from 74.125.71.147: bytes=32 time=209ms TTL=56
Reply from 74.125.71.147: bytes=32 time=369ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=414ms TTL=56
Reply from 74.125.71.147: bytes=32 time=607ms TTL=56
Reply from 74.125.71.147: bytes=32 time=425ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=141ms TTL=56
Reply from 74.125.71.147: bytes=32 time=579ms TTL=56
Reply from 74.125.71.147: bytes=32 time=643ms TTL=56
Reply from 74.125.71.147: bytes=32 time=530ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=212ms TTL=56
Reply from 74.125.71.147: bytes=32 time=652ms TTL=56
Reply from 74.125.71.147: bytes=32 time=577ms TTL=56
Reply from 74.125.71.147: bytes=32 time=183ms TTL=56
Reply from 74.125.71.147: bytes=32 time=255ms TTL=56
Reply from 74.125.71.147: bytes=32 time=254ms TTL=56
Reply from 74.125.71.147: bytes=32 time=83ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=182ms TTL=56
Reply from 74.125.71.147: bytes=32 time=134ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=98ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=294ms TTL=56
Reply from 74.125.71.147: bytes=32 time=186ms TTL=56
Reply from 74.125.71.147: bytes=32 time=78ms TTL=56
Reply from 74.125.71.147: bytes=32 time=272ms TTL=56
Reply from 74.125.71.147: bytes=32 time=482ms TTL=56
Reply from 74.125.71.147: bytes=32 time=467ms TTL=56
Reply from 74.125.71.147: bytes=32 time=269ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=291ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

sinubukan ko mag reconnect = CHEERS!!!

Reply from 74.125.71.147: bytes=32 time=177ms TTL=56
Reply from 74.125.71.147: bytes=32 time=687ms TTL=56
Reply from 74.125.71.147: bytes=32 time=242ms TTL=56
Reply from 74.125.71.147: bytes=32 time=217ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
General failure.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=642ms TTL=56
Reply from 74.125.71.147: bytes=32 time=185ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=146ms TTL=56
Reply from 74.125.71.147: bytes=32 time=139ms TTL=56
Reply from 74.125.71.147: bytes=32 time=100ms TTL=56
Reply from 74.125.71.147: bytes=32 time=329ms TTL=56
Reply from 74.125.71.147: bytes=32 time=468ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.71.147: bytes=32 time=707ms TTL=56
Reply from 74.125.71.147: bytes=32 time=287ms TTL=56
Reply from 74.125.71.147: bytes=32 time=672ms TTL=56
Reply from 74.125.71.147: bytes=32 time=86ms TTL=56
Request timed out.
Reply from 74.125.71.147: bytes=32 time=694ms TTL=56



jps001
Posted: Tuesday, August 10, 2010 12:46:40 AM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
ngaung araw to: 8-10-10 @ 12:47AM

Reply from 74.125.71.99: bytes=32 time=46ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=54ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=52ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=48ms TTL=56
Reply from 74.125.71.99: bytes=32 time=60ms TTL=56
Reply from 74.125.71.99: bytes=32 time=60ms TTL=56
Reply from 74.125.71.99: bytes=32 time=60ms TTL=56
Reply from 74.125.71.99: bytes=32 time=66ms TTL=56
Reply from 74.125.71.99: bytes=32 time=50ms TTL=56
Reply from 74.125.71.99: bytes=32 time=54ms TTL=56
Reply from 74.125.71.99: bytes=32 time=59ms TTL=56
Reply from 74.125.71.99: bytes=32 time=57ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=48ms TTL=56
Reply from 74.125.71.99: bytes=32 time=50ms TTL=56
Reply from 74.125.71.99: bytes=32 time=55ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=51ms TTL=56
Reply from 74.125.71.99: bytes=32 time=68ms TTL=56
Reply from 74.125.71.99: bytes=32 time=54ms TTL=56
Reply from 74.125.71.99: bytes=32 time=54ms TTL=56
Reply from 74.125.71.99: bytes=32 time=46ms TTL=56
Reply from 74.125.71.99: bytes=32 time=46ms TTL=56
Reply from 74.125.71.99: bytes=32 time=49ms TTL=56
Reply from 74.125.71.99: bytes=32 time=49ms TTL=56
Reply from 74.125.71.99: bytes=32 time=54ms TTL=56
Reply from 74.125.71.99: bytes=32 time=52ms TTL=56
Reply from 74.125.71.99: bytes=32 time=46ms TTL=56
Reply from 74.125.71.99: bytes=32 time=62ms TTL=56
Reply from 74.125.71.99: bytes=32 time=48ms TTL=56
Reply from 74.125.71.99: bytes=32 time=52ms TTL=56
Reply from 74.125.71.99: bytes=32 time=58ms TTL=56
Reply from 74.125.71.99: bytes=32 time=47ms TTL=56
Reply from 74.125.71.99: bytes=32 time=50ms TTL=56

sagwa pag umaga pero pag madaling araw ganyan parati result 99.99%
hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm



Mikos
Posted: Tuesday, August 31, 2010 2:19:13 PM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
Thread closed as per request of the TS in his thread: Keep up the good work.



FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


The Forum is NOT an Online Technical Support.
For your DSL/Phone concerns please call the hot lines FIRST before posting it in the Forum.
This includes requests for port resets, DSL connection footprints (ATT and SNRs), requests for technicians and repairs.
Please read the Bayan Forum Rules.


If the post is in size 6 or big sized font, it means I am addressing you as a moderator. If the post is in the default size, it means I am Mikos the plain subscriber.


Bayan Forum Rules
Users browsing this topic
Guest


Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

SoClean Theme Created by Jaben Cargman (Tiny Gecko)
Powered by Yet Another Forum.net version 1.9.1.2 (NET v2.0) - 9/27/2007
Copyright © 2003-2006 Yet Another Forum.net. All rights reserved.
This page was generated in 0.219 seconds.