![]() |
Why Winsock 2? |
Kenn's
20001013: Why Winsock 2?
October/2000
|
Our final Tech Note of the month is numbered 13, and while of course technicians are not at all superstitious, this note is a bit of an oddity, falling into the category of "well, it worked, but we don't know why". Jim L encountered this problem while connecting a Windows 95B client to an NT server on a different TCP/IP segment. Although the Windows 95B client could ping the NT server in question, it could not access shared directories on that server using a valid username and password. Confusing the issue was the fact that, from the same location, Windows 95, 95A, 95C, 98 and NT clients all could access that server's shares! Due to concerns and issues not related to the problem, it was important that Windows 95B be used on this system: switching to a different operating system was not considered a satisfactory solution. What Jim found, after exhausting all the normal network troubleshooting options, was that installing the Winsock 2 update fixed the problem! The Winsock 2 Update is on the WSD#1 Backup CD issue 16 and newer, under \OPSYS\WIN95\UPDATES. Or, you can download the Winsock 2 update from Microsoft or from the shop ftp site. Regardless of whether you experience an unusual network problem or not, the Winsock 2 update is a worthwhile upgrade for all Windows 95 systems. When our WAN was the object of a hacker's attack last year, the only Windows 95 clients which were not affected were those which had this upgrade installed. For more information about Winsock 2, see Microsoft's Release Notes for this product. |