1.
Nessoft Knowledge Base - How is MOS calculated in PingPlotter Pro?
Nessoft Knowledge Base. Knowledgebase, Top : PingPlotter Pro. How is MOS calculated in PingPlotter Pro? ID: 000050 .... Copyright © 1998, 2009 Nessoft LLC.
2.
Nessoft Knowledge Base - Socket error 11004 when testing an alert
The most common cause of this error in either PingPlotter or MultiPing is an invalid SMTP server specified. The error means that the name entered couldn't ...
3.
Nessoft Knowledge Base - Errors when running Kaspersky Antivirus
regsvr32 /u "C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0\scrchpg.dll". (If you're using Kasperksy internet security, or have installed to a ...
4.
CallerID Home Page
This Windows program uses your CallerID modem to track incoming calls. Incoming calls are announced using .WAV files or Creative Labs Text Assist (depending ...
5.
Nessoft Knowledge Base - Slow first ping, faster following
The first ping that I send somewhere is always slow the first time, then every subsequent time it is significantly better (the first hop is really fast; ...
6.
Upgrade to PingPlotter Pro
To take advantage of this upgrade pricing, enter your PingPlotter Standard or MultiPing license key here (if you own both, just enter one - we'll find the ...
7.
Nessoft – Downloads
Note: All PingPlotter editions and MultiPing run on the Microsoft Windows platform, including Windows 98, ME, NT4, 2000, XP, 2003, Vista and 2008. ...
8.
Nessoft Knowledge Base - But ... I hear that traceroute (and ...
When you see packet loss in your route, you almost certainly want to resolve that problem. If the packet loss appears at a link you know is slow, ...
9.
Nessoft Knowledge Base - Socket error 10060 when testing an alert
The 10060 error indicates a connection problem with the SMTP server. ... which SMTP server you have specified: In PingPlotter, go to Edit -> Email Setup. ...
10.
Nessoft Knowledge Base - Socket error 10060 when testing an alert
The 10060 error indicates a connection problem with the SMTP server. There are a number of possible reasons ... Socket error 10053 when testing email alerts ...
