User manual
126
• PhoneSweep identifies all numbers as a busy signal. This indicates a possible problem with
dialing out. PhoneSweep may be missing a dial tone or a connection to an outside line. If you
need to dial a prefix to reach outside lines and need to dial this prefix for each number in your
profile, enter the prefix in the appropriate field on the Dialing sub-tab. Increasing the delay
between calls on the Time sub-tab may help if the problem is not a missing prefix.
This may also be a problem with using modems programmed for American phone systems in
European countries whose dial tones sound like American busy signals.
• PhoneSweep identifies all extensions as second dial tones. This may occur if PhoneSweep is
dialing internal lines when it has been configured to always dial an access code for an external
number before each phone number. If a prefix has been specified on the Dialing sub-tab or in the
phonesweep.ini file, remove it. Also, try placing PhoneSweep outside the PBX, or disabling
Single Call Detect.
• PhoneSweep gives a call result other than CARRIER on a number known to have a modem
on it. The modem may not be set to auto-answer, in which case a VOICE response will occur if
your PBX system is set to forward the call to voicemail, or a TIMEOUT response if the phone
does not pick up. Also check to be sure that the number isn’t being used by a PhoneSweep
modem, in which case you would either get a BUSY or a VOICE response.
Important Tip: If a number is giving unexpected results with PhoneSweep, use your
phone and call the number yourself. This may help you identify the problem.
• PhoneSweep running in Identify or Penetrate mode fails to identify systems. It is possible
that PhoneSweep does not have the unidentified system(s) in its database. Contact Sandstorm
Enterprises with the response string from the unidentified system and we will add the system to
PhoneSweep’s database.
• A device was penetrated while PhoneSweep was running in Identify mode. This usually
means that PhoneSweep logged directly into the system with no username or password
authentication needed. This is a major security vulnerability.
• HTML help doesn’t work. Try running the HTML help installer hhupd.exe in the top-level
PhoneSweep directory. If this doesn’t work, try installing Internet Explorer 4.01 or 5.0 on your
computer or, on an NT system, upgrading to a newer service pack.
• PhoneSweep reports that a DLL file is missing. Copying DLL files from one computer to
another does not work. Installing Internet Explorer 4.01 or higher and reinstalling PhoneSweep
may clear up the problem. Upgrading the service packs may help; there may be a way to get DLL
files from the NT service packs.
• PhoneSweep stops working after an NT workstation upgrade. This is likely a Microsoft
problem; installing Internet Explorer 5.0 may clear up the problem.
• PhoneSweep is not making brute-force attempts when set to Penetrate mode. PhoneSweep
can only brute-force systems that it can at least partially identify.
• PhoneSweep is using the seconds-based timeout instead of the ring timeout. Most modems,
including those that support Single Call Detect, do not report remote ringing. Adjust the seconds-
based timeout on the Time sub-tab to coincide with the proper number of rings.