If PuTTY does not work for some reason, consider sending the developers a bug report. Even if the problem seems obscure to you, a solution may already be known, or your report may contain that additional piece of data that is needed to solve the puzzle. If nobody knows about your problem, they certainly cannot help you solve it.
This page lists some bug reporting tips, and gives a list of the information you should include in your report. Please try to report as much of the information listed as possible, even if it seems irrelevant.
This section lists the information to include in your bug reports.
Desribe the exact PuTTY release you are using. If you are unsure about the version number, the installation package file name should be sufficient (e.g. putty_s60_1.3beta1.zip).
Include the make and model of the handset you use (e.g. Nokia 3650) and the device software version. You can get the software version by typing "*#0000#" in the main phone screen.
If the problem is deterministic, include exact steps on how to reproduce the problem, preferably down to each individual keypress. Try to find the shortest possible way to reproduce the issue.
Specify the operator you are using, and the GPRS access point in use. In Series 60 you can find the access point name in the settings application, under "Connections" and "Access points". If you use CSD or HSCSD, describe the ISP or dialup service you use. Note that PuTTY does not work with most WAP access point or dialup servers, you should instead use the access point your operator recommends for internet access from a PC.
Can you connect to the same SSH server from a PC using the handset as a modem and using same access point or dialup server? Include information if this works, does not work, or you haven't tried it.
If the application starts and a network connection is set up, but the SSH connection does not get established, the PuTTY log file might contain useful information. See the troubleshooting page for documentation on how to enable logging. When you get a log file, check that it doesn't contain confidential data such as passwords before sending it. Attach the log file to your report.
If PuTTY crashes suddenly, the crash is usually caused by a software panic. The panic category and code can be very helpful in determining the reason, especially since PuTTY internal assertion failures also cause panics. The Nokia 9200 Communicator series displays the panic category and code by default (for example "KERN-EXEC 3"), include that information in your bug report.
Series 60 does not display the panic code by default, showing instead just an "Program Closed" message. You can enable panic display by creating a file called c:\system\bootdata\errrd with a file manager application (note the spelling!) and rebooting. The file should be empty. The next time a panic occurs the device will show the panic category and code, include those in the report.
There are two main ways to send bug reports on PuTTY: E-mailing the developers directly, or using the bug tracking system in SourceForge. The SourceForge bug tracking system is the preferred method, so please use it when possible! See the contact information page for details. Note that the SourceForge reports are public, so reports on new security vulnerabilities should be sent directly to the developers to avoid publishing them until a solution has been found.
Before filing a new bug report, take a few minutes to browse the bug tracking system at the SourceForge project page to avoid sending duplicate reports. If a report for the same bug exists already, consider adding your information to that report as a comment instead.
Bug reports with solution proposals or code patches are always welcome.