JohnnyCool wrote1. I am not getting an "Empty Response". I'm getting "Connection Reset", frequently.
2. This only started to happen about a month ago. Why?
3. The last Telkom tech told me that Telkom [B]does[/B] have a known problem with its default DNS, but isn't addressing the "problem".
4. He told me the problem started around Nyepi time and continues.
5. Telkom rang me this morning and I'm waiting for another tech to arrive.
6. A small bar near my place has the same IndiHome package as me. The problem is there, too.
I have tried different DNS settings, including Google, OpenDNS, and others. No joy anywhere so I believe it [B]is[/B] something to do with Telkom itself.
I'll question the tech again when he arrives.
[ATTACH=CONFIG]2705[/ATTACH]
I occasionally get Connection Reset, but not often. Microsoft Technet expxlains it thus
Explanation:
A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
User Action:
Check the following: 1. Ping the remote host you were connected to. If it doesn't respond, it might be offline or there might be a network problem along the way. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again). 2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step). 3. Ping your local router address. If you are on a serial connection, your local router is the IP address of the host you initially logged on to using SLIP or PPP. 4. Ping a host on the same subnet as the host you were connected to (if you know of one). This will verify that the destination network is functioning. 5. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.
The "peer" is the remote web-site you are going to (sometimes you contact many remote sites before all the ads pop up so it could be any of them). The message back from that remote site is roughly "What I am receiving from you does not make sense so I will force a reset, then you can try again". Microsoft's suggestions for diagnosis is a series of pings aimed at identifying where along the path the problem may be.
So you have a problem, but I still say it has nothing to do with DNS - note that Microsoft does not suggest you ping your DNS server. Your PC did a DNS lookup before the communication was initiated. Then you browser is contacting an Internet number and the problem pops up.
So your Telkom techs may be correct to say that this started around Nyepi and is still a problem, but IMHO they are talking though their hats when they blame DNS.
