PuTTY bug win95-resolution

This is a mirror. Follow this link to find the primary PuTTY web site.

summary: Problems with host name resolution on Win95; WinSock 2 implicated?
class: bug: This is clearly an actual problem we want fixed.
priority: historic: This is an old bug report that we think is either fixed without noticing, or confined to old systems, or too vague.
absent-in: 0.52 0.53b
present-in: 0.54 0.56 2005-02-14

We've had a couple of reports that recent versions of PuTTY have trouble resolving hostnames, while other apps such as Windows Telnet, and old versions of PuTTY, work fine. However, the only Win95 system I (JTN) have access to appears to work fine in this regard; on that system the Windows Sockets 2 upgrade is not installed, whereas on all of the problem systems WinSock2 does appear to be installed. (We changed to dynamically loading WinSock 2 where available in all applications between 0.53b and 0.54; previously all the apps except Plink linked against WinSock 1.)

The error reported is "ssh_init: Host does not exist".

I (JTN) have had a brief look at the 0.56 name resolution code and can't see anything obviously wrong or potentially dubious about it.

Reports:

E1Bq1Ni-00053V-00@smtp6.mindspring.com (looks like WinSock 2 is installed)
Pine.SOL.3.96.1040920100623.8845A-100000@langs (WinSock 2 is installed)
20041115005023.GA28326@radon.dcs.kcl.ac.uk (WinSock 2 is installed)

SGT, 2024-11-17: classifying this bug as historic. Win95 is very obsolete, so flakiness specific to it is probably not important.

If you want to comment on this web site, see the Feedback page.

Audit trail for this bug.

(last revision of this bug record was at 2024-11-17 15:29:37 +0000)