I would advise whoever wants Banda Ancha Movil to AVOID Vomistar at all costs. Ever since they unified their business units (land line telephony/cellular communications/internet provision/others) with this "Marca Unica" last November, it was nothing but problems.
There is a router in the GPRS infrastructure that is failing and they are unable to recognize that fact. I don't know if they simply refuse to run the necessary diagnostics or what, but there is an ongoing problem which is obvious to users. It shows all the symptoms of overheated equipment, which during the day fail and reboot constantly. Because the nighttime temperatures allow the equipment to function within expected parameters, ie, it works. Connectivity is excellent during this time. Daytime is horrible. The GPRS signal can be excellent, and the local (ie between your modem and the router in the tower) connection is perfect, the next hop constantly fails.
Your computer will diagnose this as an inability to communicate with the DNS server. Even if you configure for an Open DNS server (like Google has at 8.8.8.8 and 8.8.4.4) you will still not be able to communicate with a DNS server, which indicates a lack of connectivity within the network.
>nslookup
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 200.28.4.130 // DNS server for Vomistar.
> facebook.com
Server: UnKnown
Address: 200.28.4.130
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Here is a traceroute to Google's DNS:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 * * * Request timed out.
2 2087 ms 1589 ms 1499 ms 10.178.165.174
3 * * * Request timed out.
4 * * * Request timed out.
5 2526 ms 3356 ms 2808 ms 10.0.250.46
6 * * * Request timed out.
7 * * * Request timed out.
8 392 ms 199 ms * Xe0-3-0-0-grtmiabr7.red.telefonica-wholesale.net.124.142.94.in-addr.arpa [94.142.124.10]
To explain what is going on here: the second hop shows 2087ms (over two seconds) and the fifth hop shows 3356ms (over 3 seconds). The addresses 10.178.165.174 and 10.0.250.46 are part of the INTERNAL private network that Movistar uses. Networks that use 10.x.x.x are unrouteable from the outside, so this is a security feature. BUT, the problem is that response time is ten to twenty times greater than what is acceptable. The hops where the request times-out are perfectly normal, indicating equipment which will not respond to traceroute requests. This behaviour is a result of security measures. In the old days, you would see each hop with its address and response time.
Tracing route to entelpcs.cl [200.111.151.42]
over a maximum of 30 hops:
1 * * * Request timed out.
2 3428 ms 1109 ms 559 ms 10.178.165.190
3 * * *
Here we have the same problem. Equipment failure.
Tracing route to facebook.com [69.63.181.11]
over a maximum of 30 hops:
1 * * * Request timed out.
2 3776 ms 278 ms 759 ms 10.178.165.158
3 * * * Request timed out.
4 173 ms 199 ms 209 ms 201.220.232.2
Anyone see a pattern here?
What does Movistar do about the problem? DENY DENY DENY DENY.
As has been suggested, you might want to get the cellphone signal extender from WEI.cl but whatever you do, avoid Vomistar like the plague. Get ENTEL or CLARO. ENTEL is probably your best bet. If you have VOMISTAR already, demand that they FIX their system.
Also, see RECLAMOS.CL for more info about these problems.
Here's an explanationBut don't take my word for it.