CCTV in Digitel DSL, remotely viewable only with Digitel DSL

Discussion in 'Digitel DSL' started by bensy, Aug 13, 2010.





  1. I have two CCTV setups. Both are previously on Digitel DSL (separate location/account).

    I noticed that they can be viewed flawlessly via internet with remote Digitel DSL. However, using Globe or PLDT DSL, viewing remotely is always flawless. I frequently get disconnected after 2 or 3 seconds, then connected / disconnected again and again.

    Using GLOBE or PLDT DSL as server of the CCTV, same thing happens using a remote Digitel DSL connection. But flawless using Globe or PLDT connections.

    However, during late night up to early morning, remote viewing is ok using any server and any remote ISP

    What could be the problem?????
    Solution?

    thanks
     
  2. josekym

    josekym Member




    From the flawed connection, try doing a tracert or pathping to the target IP (CCTV). Compare that with using the flawless connection and you will get your answer. ;)

    Solution is to use a better peered ISP, or same ISP on both ends.
     



  3. I tried the pathping and tracert. below are the results. I do not understand these. can you please interpret for me. thanks

    ==================
    C:\Users\Me>pathping 222.127.xxx.xxx

    Tracing route to 222.127.xxx.xxx over a maximum of 30 hops

    0 PC1.domain.name [192.168.1.2]
    1 dsldevice.domain.name [192.168.1.1]
    2 * * *
    Computing statistics for 25 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 PC1.domain.name [192.168.1.2]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.domain.name [192.168.1.1]

    Trace complete.

    ===================================================



    C:\Users\Me>tracert 222.127.xxx.xxx

    Tracing route to 222.127.xxx.xxx over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms dsldevice.domain.name [192.168.1.1]
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 38 ms 42 ms 39 ms 202.138.144.214
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 205 ms 205 ms 204 ms 120.28.0.1
    11 203 ms 210 ms 212 ms 120.28.0.182
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 248 ms 239 ms 236 ms 222.127.xxx.xxx

    Trace complete.
     
  4. josekym

    josekym Member




    ^^You should remove the public IPs on your post if you are on static IP for the location...

    What is your DSL modem/router? It seems to be breaking the tracert and pathping commands. We can't inerpret it properly at that.

    Anyway, I did a similar test from my end (using Globe DSL):

    Tracing route to 222.127.xxx.xxx over a maximum of 30 hops

    1 36 ms 36 ms 38 ms 180.191.92.1
    2 37 ms 41 ms 55 ms 120.28.64.57
    3 36 ms 42 ms 37 ms 10.163.111.129
    4 36 ms 37 ms 36 ms 10.109.9.46
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * ^C

    I stopped already at that point since there is no reason to continue. The IP seems to be unreachable now?
     



  5. i have dynamic ip address. And it changed now. and everyday around starting around 8pm to 8am, there is no more trouble or disconnection. so its no point testing now. maybe tomorrow again.

    prolink + Edimax BR6226n

    thanks
     
  6. josekym

    josekym Member




    ^^Ah, then consider also that Digitel applies bandwidth management on its subscribers' connections. It may be affecting your setup too.
     



  7. but is it possible that their bandwidth management does not affect digitel dsl remote viewing on a cctv with another digitel dsl connection?
     
  8. josekym

    josekym Member




    ^^Yes it is possible, since that is "local" traffic within their IP network. However, without further testing, we can't say for sure.
     



  9. From my globe dsl today, when i view the cctv, it it working fine. And when I pathping and tracert the digitel dsl (note my cctv is portwarded to a port not the default 80).



    C:\Users\Me>pathping 124.217.xxx.xxx

    Tracing route to 124.217.xxx.xxx
    over a maximum of 30 hops:
    0 P2CORE [192.168.2.106]
    1 192.168.2.1
    2 192.168.1.1
    3 222.127.121.1
    4 10.109.9.45
    5 120.28.0.189
    6 120.28.0.50
    7 218.188.104.149
    8 * * *
    Computing statistics for 175 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 P2PC [192.168.2.106]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1
    0/ 100 = 0% |
    2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    3 29ms 0/ 100 = 0% 0/ 100 = 0% 222.127.121.1
    0/ 100 = 0% |
    4 31ms 0/ 100 = 0% 0/ 100 = 0% 10.109.9.45
    0/ 100 = 0% |
    5 30ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.189
    0/ 100 = 0% |
    6 32ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.50
    0/ 100 = 0% |
    7 170ms 0/ 100 = 0% 0/ 100 = 0% 218.188.104.149

    Trace complete.



    C:\Users\Me>tracert 124.217.xxx.xxx

    Tracing route to 124.217.xxx.xxx
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.2.1
    2 1 ms 1 ms 1 ms 192.168.1.1
    3 25 ms 24 ms 23 ms 222.127.121.1
    4 23 ms 24 ms 27 ms 10.109.9.45
    5 53 ms 23 ms 24 ms 120.28.0.189
    6 97 ms 24 ms 24 ms 120.28.0.50
    7 161 ms 162 ms 161 ms 218.188.104.149
    8 * * * Request timed out.
    9 188 ms 188 ms 188 ms 202.138.144.170
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\Users\Me>
     



  10. From a Digitel DSL PC, pathping and tracert results when I accessed CCTV based in Globe DSL server.


    C:\Documents and Settings\BSy>pathping 222.127.xxx.xxx

    Tracing route to 222.127.xxx.xxx
    over a maximum of 30 hops:
    0 BsyPC [192.168.2.100]
    1 192.168.2.1
    2 192.168.1.1
    3 1-4-217.124.adsl-pool.digitelone.com [124.217.4.1]
    4 202.138.144.153
    5 202.138.144.214
    6 Se5-0-1.gw1.hkg3.asianetcom.net [203.192.153.201]
    7 203.222.33.57
    8 sl-gw10-hk-9-0-0.sprintlink.net [203.222.38.106]
    9 203.222.160.98
    10 120.28.0.85
    11 120.28.0.1
    12 120.28.0.186
    13 222.127.223.34
    14 * * *
    Computing statistics for 350 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 BsyPC [192.168.2.100]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1
    0/ 100 = 0% |
    2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    3 28ms 0/ 100 = 0% 0/ 100 = 0% 1-4-217.124.adsl-pool.digitelone.com [124.217.4.1]
    0/ 100 = 0% |
    4 28ms 0/ 100 = 0% 0/ 100 = 0% 202.138.144.153
    0/ 100 = 0% |
    5 31ms 0/ 100 = 0% 0/ 100 = 0% 202.138.144.214
    0/ 100 = 0% |
    6 211ms 0/ 100 = 0% 0/ 100 = 0% Se5-0-1.gw1.hkg3.asianetcom.net [203.192.153.201]
    0/ 100 = 0% |
    7 421ms 1/ 100 = 1% 1/ 100 = 1% 203.222.33.57
    0/ 100 = 0% |
    8 428ms 1/ 100 = 1% 1/ 100 = 1% sl-gw10-hk-9-0-0.sprintlink.net [203.222.38.106]
    0/ 100 = 0% |
    9 82ms 0/ 100 = 0% 0/ 100 = 0% 203.222.160.98
    0/ 100 = 0% |
    10 192ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.85
    0/ 100 = 0% |
    11 197ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.1
    0/ 100 = 0% |
    12 191ms 0/ 100 = 0% 0/ 100 = 0% 120.28.0.186
    0/ 100 = 0% |
    13 277ms 0/ 100 = 0% 0/ 100 = 0% 222.127.223.34
    100/ 100 =100% |
    14 --- 100/ 100 =100% 0/ 100 = 0% BsyPC [0.0.0.0]

    Trace complete.



    C:\Documents and Settings\BSyPC>tracert 222.127.xxx.xxx

    Tracing route to 222.127.xxx.xxx
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.2.1
    2 1 ms 1 ms 1 ms 192.168.1.1
    3 22 ms 21 ms 20 ms 1-4-217.124.adsl-pool.digitelone.com [124.217.4.1]
    4 20 ms 23 ms 29 ms 202.138.144.153
    5 23 ms 21 ms 21 ms 202.138.144.214
    6 206 ms 209 ms 204 ms Se5-0-1.gw1.hkg3.asianetcom.net [203.192.153.201
    ]
    7 398 ms 393 ms 397 ms 203.222.33.57
    8 378 ms 371 ms 377 ms sl-gw10-hk-9-0-0.sprintlink.net [203.222.38.106]

    9 51 ms 50 ms 49 ms 203.222.160.98
    10 194 ms 193 ms 192 ms 120.28.0.85
    11 193 ms 193 ms 192 ms 120.28.0.1
    12 194 ms 192 ms 191 ms 120.28.0.186
    13 196 ms 195 ms 193 ms 222.127.223.34
    14 * * * Request timed out.
    15 222 ms 223 ms 219 ms 222.127.xxx.xxx
    16 263 ms 220 ms 218 ms 222.127.xxx.xxx

    Trace complete.

    C:\Documents and Settings\BSyPC>
     
  11. josekym

    josekym Member




    I notice you have 2 routers? Or maybe the modem-router (in router mode) and a router?

    Did you port forward the CCTV ports on both devices?

    Anyway, your traces seem to be ok from the Digitel connection. I traced your Digitel gateway from my Globe DSL and got this:

    Tracing route to 1-4-217.124.adsl-pool.digitelone.com [124.217.4.1]
    over a maximum of 30 hops:

    1 37 ms 36 ms 36 ms 180.191.42.1
    2 37 ms 37 ms 36 ms 10.109.9.73
    3 46 ms 46 ms 48 ms 120.28.0.197
    4 38 ms 44 ms 37 ms 120.28.0.5
    5 37 ms 36 ms 37 ms 120.28.0.66
    6 174 ms 175 ms 175 ms 218.188.104.149
    7 * * * Request timed out.
    8 198 ms 199 ms 199 ms 124.217.4.1

    Trace complete.

    That said, you should be able to access your CCTV on the Globe network without much problems. Are you having issues now?
     



  12. i have a prolink (modem-router) and edimax router on both Digitel and Globe.

    Both are double port forwarded.
    I'm having trouble accessing the digitel based cctv from globe dsl and vice versa..
     
  13. josekym

    josekym Member




    But can you access the CCTV at times, or not at all?

    Which browser are you using to view? I'd try IE first.

    Also, can you do a comparative tracert and pathping from Digitel to Digitel?
     



  14. I can acccess CCTV at night until morning, without error.
    I'm using IE or firefox - same error
    I just have my other Digitel DSL disconnected (because of throttling) and replaced with Globe DSL, thus i can no longer tracert digitel to digitel.
     
  15. josekym

    josekym Member




    If you can access at certain, predictable times only, then it appears to be a link-up issue between the ISPs, or some intermediate network issue. IMO, it is more likely Digitel's bandwidth management at work.
     



  16. and there is nothing we can do about it (Digitel's bandwidth MISmanagement) ? What is I port forward more ports say 100 to 110, will it make any difference?
     
  17. josekym

    josekym Member




    ^^Basically, yes. It is Digitel's network policy, so it can't be helped.

    Forwarding more ports will not help either, as these are just openings on the firewall at your side. Traffic will still pass thru the constricted (i.e. bandwidth managed) upstream link.
     



  18. Hi Sirs,

    I am relatively new here in PINOY DSL and an internet newbie. I just wanted to seek assistance regarding my CCTV Setup.

    Setup is PROLINK 9200AR + TPLink TL-WR740N + CCTV.

    I have already bridged the modem and set the router at PPOE with username and password already defined. I have already enrolled my IP at NO-IP.com. Problem is I cant view my CCTV at IE neither at FF. How can I define my Port Forwarding Correctly?

    Your usual assistance will be greatly appreciated.

    Thanks.
     

    Attached Files:

  19. josekym

    josekym Member




    I suggest you refrain from using port 53 as your service port... Try mo port 8080 or 8088 or 8888, or the port which is suggested by your CCTV equipment manufacturer.
     



  20. Sir tama ba yung setup ko na bridged ko yung modem then set ko yung PPPOE sa router? Pareho lang po ba yung port forwarding sa virtual server o sa port trigerring? Kung idederetso ko naman sa modem (9200AR), and without the router, yung port forwarding, ano yung mga value na kelangan ko ilagay?

    Protocol:
    Local IP Address: Local Port:
    Remote IP Address: Public Port:
    Interface:

    Thanks sir for the very prompt response. 5.JPG

    4.JPG
     
                                 

Share This Page