Resultados 1 al 10 de 1027

Tema: Proxy - Posible solucion para Fibertel

Ver Modo Hilado

Mensaje Anterior Mensaje Anterior   Próximo Mensaje Próximo Mensaje
  1. #30

    Re: Proxy - Posible solucion para Fibertel

    Es un problema de Gateways... Mi primo tambien tiene fiber al = que yo y vive a 3 cuadras de mi casa y a el no le pasa esto mientras que a mi si, porke fibertel nos asigna diferentes gateways. Lo que no te es ke si tenes en rango de ip viejo de fibertel (24.232.X.X) etenes un gateway distinto a los que tienen los rango de ips nuevas (190.x.x.x)


    Aca las pruebas que hice usando simples herramientas, Ping, y Tracert.


    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\Real>ping 190.224.162.69 -t

    Pinging 190.224.162.69 with 32 bytes of data:
    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 190.224.162.69: bytes=32 time=13ms TTL=51
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=25ms TTL=51
    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.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=49ms TTL=51
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=16ms TTL=51
    Request timed out.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=17ms TTL=51
    Request timed out.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=16ms TTL=51
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=30ms TTL=51
    Request timed out.
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=11ms TTL=51
    Request timed out.
    Reply from 190.224.162.69: bytes=32 time=16ms TTL=51
    Request timed out.
    Request timed out.

    Ping statistics for 190.224.162.69:
    Packets: Sent = 46, Received = 9, Lost = 37 (80% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 49ms, Average = 21ms

    C:\Users\Real>tracert 190.224.162.69

    Tracing route to host69.190-224-162.telecom.net.ar [190.224.162.69]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 14 ms 15 ms 14 ms GW-22.fibertel.com.ar [24.232.22.1]
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 13 ms 14 ms 18 ms 17-165-89-200.fibertel.com.ar [200.89.165.17]
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 15 ms 12 ms 44 ms 76C-G10-V616-NAC.mrse.com.ar [200.51.235.81]
    10 12 ms 14 ms * cli02ra-se-4-2-2.tasf.telecom.net.ar [200.3.34.133]
    11 * 15 ms * host141.200-3-81.telecom.net.ar [200.3.81.141]
    12 * * * Request timed out.
    13 * * 14 ms host69.190-224-162.telecom.net.ar [190.224.162.69]


    Trace complete.

    C:\Users\Real>


    O es problema de Telecom.net.ar o de fiber, no lo se.
    Última edición por sNsReal; 24/07/2009 a las 21:35

Etiquetas para este Tema

Permisos de Publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •  

ESCORTS Capital Federal | ESCORTS Zona Sur | ESCORTS Zona Norte | ESCORTS Zona Oeste | ESCORTS Mar del Plata | ESCORTS La Plata | ESCORTS Cordoba | ESCORTS Rosario | ESCORTS Tucuman | Escorts Almagro | Escorts Belgrano | Escorts Caballito | Escorts Centro | Escorts Flores | Escorts Microcentro | Escorts Once | Escorts Palermo | Escorts Recoleta | Escorts Tribunales | Escorts Devoto | Escorts Villa Urquiza | Escorts Caba