Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: hgomez on December 20, 2004, 05:54:06 PM

Title: www.banesco.com take too much time with 5.6
Post by: hgomez on December 20, 2004, 05:54:06 PM
Hi everybody, I am using e-smith 5.6, lately the site from Banesco Bank begun to take to much time to load, I don’t why?, check it www.banesco.com, only who has e-smith 5.6 please, but this page load well: http://www.banesco.com/banesco24horas.asp?B24=B24#telefonica and it is in same site. Anyone can explain it????
Title: www.banesco.com take too much time with 5.6
Post by: raem on December 21, 2004, 04:41:11 PM
check your spelling
www.banesco.com,

try
www.banesco.com
instead. It opens fine for me.
Title: That is not the problem
Post by: hgomez on December 21, 2004, 06:41:31 PM
Quote from: "RayMitchell"
check your spelling
www.banesco.com,

try
www.banesco.com
instead. It opens fine for me.


That is not the problem, it open here too. You open it? inside back my squid, this page take 3 minutes or more to load!(normal time is 25 sec), in your env, how many time it took to load?
Title: www.banesco.com take too much time with 5.6
Post by: raem on December 22, 2004, 04:04:04 AM
It loads in around 4 secs.
Title: www.banesco.com take too much time with 5.6
Post by: cydonia on December 22, 2004, 05:55:29 AM
yeh, took 2-4 seconds for me also (1500/256 adsl).
Title: www.banesco.com take too much time with 5.6
Post by: hgomez on December 22, 2004, 07:01:09 PM
Quote from: "cydonia"
yeh, took 2-4 seconds for me also (1500/256 adsl).


Ok, I don't understand, I have 2 way to reach internet, 1.- e-smith 5.6 2.-InstaGate EX2, both are having same problem, however if I try direct from my DMZ work fine...Well thanks for your help.
Title: www.banesco.com take too much time with 5.6
Post by: raem on December 23, 2004, 07:13:16 AM
Check the way DNS is setup on your server.
Title: ping and traceroute
Post by: hgomez on December 23, 2004, 03:03:08 PM
Quote from: "RayMitchell"
Check the way DNS is setup on your server.


[root@proxy root]# tracert www.banesco.com
bash: tracert: command not found
[root@proxy root]# traceroute
Version 1.4a12
Usage: traceroute [-dFInrvx] [-g gateway] [-i iface] [-f first_ttl]
        [-m max_ttl] [ -p port] [-q nqueries] [-s src_addr] [-t tos]
        [-w waittime] [-z pausemsecs] host [packetlen]
[root@proxy root]# traceroute www.banesco.com
traceroute to www.banesco.com (216.72.89.136), 30 hops max, 38 byte packets
 1  Red_200.41.12_Cust_30.static.impsat.net.ve (200.41.12.233)  0.865 ms  0.757 ms  0.705 ms
 2  200.41.116.197 (200.41.116.197)  855.653 ms  1382.989 ms  1386.321 ms
 3  trunk_I.rcoretlp1.impsat.com.ve (64.76.64.219)  1589.740 ms  1662.622 ms  1666.161 ms
 4  itxcell-portoviejo_IN.us.impsat.net (200.31.0.65)  1895.624 ms  2058.339 ms  2367.087 ms
 5  g0-10.na21.b002802-1.mia01.atlas.cogentco.com (38.112.4.121)  2213.880 ms  2196.830 ms  2155.762
 ms
 6  g11-2.core01.mia01.atlas.cogentco.com (38.112.36.197)  2239.151 ms  2369.493 ms  2238.188 ms
 7  francetelecom.mia01.atlas.cogentco.com (154.54.11.78)  1711.991 ms  1847.984 ms  1955.719 ms
 8  So6-0-0.MIACR2.Miami.opentransit.net (193.251.129.197)  2258.850 ms  2361.634 ms  2427.545 ms
 9  So2-0-0.ATLCR2.Atlanta.opentransit.net (193.251.128.130)  2482.282 ms  1964.706 ms  1658.867 ms
10  * * *
11  57.74.0.94 (57.74.0.94)  2026.708 ms  2339.062 ms  2589.842 ms
12  * bccs433-fe3-0-0.gip.net (206.49.192.242)  908.085 ms  870.753 ms
13  206.49.192.190 (206.49.192.190)  788.468 ms 206.49.192.186 (206.49.192.186)  975.012 ms 206.49.192.190 (206.49.192.190)  1151.585 ms
14  * * *
....
30  * * *

[root@proxy root]# ping www.banesco.com
PING www.banesco.com (216.72.89.136) from 200.41.12.238 : 56(84) bytes of data.
From 206.49.192.186 icmp_seq=1 Packet filtered
From 206.49.192.70 icmp_seq=2 Packet filtered
From 206.49.192.186 icmp_seq=3 Packet filtered
From 206.49.192.186 icmp_seq=4 Packet filtered
From 206.49.192.186 icmp_seq=5 Packet filtered
From 206.49.192.186 icmp_seq=7 Packet filtered            

now, from windows

ping www.banesco.com
Haciendo ping a www.banesco.com [216.72.89.136] con 32 bytes de datos:

Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.

Estad¡sticas de ping para 216.72.89.136:

    Paquetes: enviados = 4, recibidos = 0, perdidos = 4 (100% perdidos),

Tiempos aproximados de recorrido redondo en milisegundos:

    m¡nimo = 0ms, m ximo =  0ms, promedio =  0ms

traceroute www.banesco.com
Traza a la direcci¢n www.banesco.com [216.72.89.136]

sobre un m ximo de 30 saltos:
  1   <10 ms   <10 ms   <10 ms  Red_200.41.12_Cust_30.static.impsat.net.ve [200.41.12.233]
  2  2266 ms  2359 ms  2297 ms  200.41.116.197
  3  2250 ms  2390 ms  2297 ms  trunk_III.rcoretlp1.impsat.com.ve [64.76.64.211]
  4  1563 ms  1437 ms  1422 ms  itxcell-portoviejo_IN.us.impsat.net [200.31.0.65]
  5  1719 ms  1843 ms  1954 ms  g0-10.na21.b002802-1.mia01.atlas.cogentco.com [38.112.4.121]
  6  2218 ms  2313 ms  2328 ms  g11-2.core01.mia01.atlas.cogentco.com [38.112.36.197]
  7  2296 ms  2297 ms  2282 ms  francetelecom.mia01.atlas.cogentco.com [154.54.11.78]
  8  1734 ms  1172 ms  1344 ms  So6-0-0.MIACR2.Miami.opentransit.net [193.251.129.197]
  9  1500 ms  1718 ms  2235 ms  So2-0-0.ATLCR2.Atlanta.opentransit.net [193.251.128.130]
 10     *        *        *     Tiempo de espera agotado para esta solicitud.
 11  2047 ms  1687 ms  1641 ms  57.74.0.94
 12  2344 ms  2359 ms  2406 ms  bccs433-fe3-0-0.gip.net [206.49.192.242]
 13  206.49.192.186  informes: Red de destino inaccesible.
Traza completa.

Windows in DMZ reach the destiny, but e-smith does not.

May yo test it?