Search the Community
Showing results for tags 'ping'.
first, please excuse me if the answer was readily available but I went through all the following query results in vain. I'm using a NetLimiter on Windows 7, which a screenshot is attached, and it works as expected when I actually get a connection to programs/processes. 2/3 of the time, connection don't get through and the difficulties even reach low enough (ISO level) to affect ping (command-line). Ping will sometimes not get through and sometimes do get through although with a pathetic 1st or 2nd reply, effectively getting better, and other times get worse through the ping seeing such behavior, I'm wondering which process, image name or title/label, is responsible for DNS resolving ; so I could set it to high priority. I tried to set a few processes to high (network priority) but my attempts were failures. it's likely either the ones I tried (at high) weren't for DNS resolving or the netlimiter fail to consider DNS ; high = none, normal = some, low = lots. for my process screening I've looked at the process image names in reverse order of total downloaded bandwidth. the context is me using an offline downloader to low (bandwidth) priority, which seem to be the sole responsible for taking so much bandwidth that almost none is left for others. what usually happen using such program is the server bandwidth being lower than my provider maximum speed so I have some left out to do not-so-high internet usage, AKA non-video-streaming. now being on a limited connection, dial-up, I've set that high-bandwidth process to low priority using the netlimiter. I expected normal/high process to have no problem accessing internet just as there was about no other internt usage. the workaround I came up with is to cap the offline downloader, to 2-4 kbps, which leave me 1-3 kbps for other programs. the downside to this is all the time I'm actually not using that little bandwidth (chatting, reading forums, etc.), I'm taking even longer to complete the download. the workaround to the workaround was to keep turning that absolute limit on & off. I'd really like the netlimiter to do as expected, which is imposing relative limits, so I wouldn't have to use absolute ones ; the latter wasting bandwidth or annoying me to switch on & off regularly. I'd appreciate help with bandwidth relative limitation but my main concern ATM is to find which process(es) is/are responsible for DNS resolve. thank you kindly