All about Smart Bro

[rlcrl]

---

Oh well, back to our f*cking predicament.

Pinging 192.168.224.1 with 32 bytes of data:

Reply from 192.168.224.1: bytes=32 time=6ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=7ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=7ms TTL=64
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=4ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=10ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=6ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=7ms TTL=64
Request timed out.
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=9ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=6ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=10ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=6ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=11ms TTL=64
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=7ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=10ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=13ms TTL=64
Reply from 192.168.224.1: bytes=32 time=9ms TTL=64
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=14ms TTL=64
Reply from 192.168.224.1: bytes=32 time=7ms TTL=64

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

try this:

goto http://portal.smartwifi.com.ph and do RESET Connection, upon rebooting don't turn off or unplugged your canopy power supply or even restart your router just simply reboot your pc and try to browse google or any other website and it will take you back to portal to enter the CODE, follow procedure, after rebooting the second time release/renew and flushdns, works all the time at my end if i experience the above ping problems on dsn server.

or:

do tracert ipaddress and send the result to customer service or talk to a customer service representative about the tracert result.

[RuSteD]

actually i have done all the things you've stated above. The result? they need to pass it to the higher technical group and then promise for a better connection after. What do i get? Still recurring problems that hound me from the time i availed of their service.

[ryan22]

bro it's clearly not a problem with our pc but on their end,
bati lang gyud tngali na ila technology gigamit or overloaded ra tngali...
kapuy na kaau balik2x ug troubleshoot mura raba ila mga tech support naa pud wifi or
internet man lang pra naa pud unta cla first hand experience sa actual troubleshooting....

[RuSteD]

indeed. Maski ila mga employees siguro are into another isp than patronizing ang ila service.

kung problema sa pc, do i have to refresh my system everyday para mo nindot ako connection? I dont think so.

[rlcrl]

check your canopy configuration "SectorUserCount" kung daghan mo bati gyud imo connection. Ako ra usa kasagaran sa ako connection pinakadaghan ako nakita 3 ra gyud.

RSSI=500+ Jitter=4 SectorUsercount=3Max

i tried other Colorcodes na mas ubos ug Jitter and mas taas ug RSSI as posted above pero SectorUsercount=7, putol-putol ang connection so nibalik ko sa lower usercount bisan ug mas ubos RSSI ug taas ang Jitter

ok man ako connection for over a year na ko naka subscribe, since meridian pa

[danoote]

check your canopy configuration "SectorUserCount" kung daghan mo bati gyud imo connection. Ako ra usa kasagaran sa ako connection pinakadaghan ako nakita 3 ra gyud.

RSSI=500+ Jitter=4 SectorUsercount=3Max

i tried other Colorcodes na mas ubos ug Jitter and mas taas ug RSSI as posted above pero SectorUsercount=7, putol-putol ang connection so nibalik ko sa lower usercount bisan ug mas ubos RSSI ug taas ang Jitter

ok man ako connection for over a year na ko naka subscribe, since meridian pa

unsaon ni buhaton bro?dili man gud ko familiar sa ani nga aspect...medyo hinay man gud ang connection nako.

[baboy]

4 now ok akng connection :mrgreen:

[curbz_canete]

question mga guys.. naa ko laptop and i need it connected sa net onsa need nako wifi card ra?

[baboy]

question mga guys.. naa ko laptop and i need it connected sa net onsa need nako wifi card ra?

u can connect man sa net in many ways by using baron dial up connection, lan connection, og kanang wifi card is only used kanang naay hotspot like sa bo's ba ron, etc ....

[rlcrl]

check your canopy configuration "SectorUserCount" kung daghan mo bati gyud imo connection. Ako ra usa kasagaran sa ako connection pinakadaghan ako nakita 3 ra gyud.

RSSI=500+ Jitter=4 SectorUsercount=3Max

i tried other Colorcodes na mas ubos ug Jitter and mas taas ug RSSI as posted above pero SectorUsercount=7, putol-putol ang connection so nibalik ko sa lower usercount bisan ug mas ubos RSSI ug taas ang Jitter

ok man ako connection for over a year na ko naka subscribe, since meridian pa

unsaon ni buhaton bro?dili man gud ko familiar sa ani nga aspect...medyo hinay man gud ang connection nako.

you need to know your canopy id address then manually change your pc ipaddress to the same class of your canopy ipaddress at least plus one para no confict, after that use ie explorer and enter the canopy ipaddress to see/change your canopy settings