Learn how to a build a cloud-first strategyRegister Now


Winsock error loading httpstk.nlm

Posted on 2005-04-22
Medium Priority
Last Modified: 2008-02-07
Running Netware 6.5 sp1. Upgraded to NICI 2.6.7 and applied SECUPD7 (PKI 2.7.5, etc.)

Now httpstk.nlm won't load. Message:

Error accessing WinSock Services, ccode = 0x273B

I tracked down the error code and it's defined as follows:
Protocol not supported. Either the requested protocol is not installed on the system or no implementation exists for it. For example, if TCP/IP is not installed on the system, attempting to create either a TCP or a UDP socket will generate this error.

Questions: What protocol is not supported/installed? How do I find out? Most importantly, how do I fix it?!
Question by:Gazaway
  • 2
LVL 34

Accepted Solution

PsiCop earned 1500 total points
ID: 13850397
HTTPSTK's load statement probable ends with a command-line switch to designate the SSL Certificate file. If the file name is wrong, or the file is not in the location where HTTPSTK is looking, or the SSL certificate is corrupt, then problems like this can occur. In that case, the "protocol not supported" is SSL.

Use the PKIDIAG utility at the server console to verify the state of the SSL certificate and re-generate it if needed. See Novell TID #10079373.

Also, you might try applying NetWare v6.5 Support Pack 2 (or even Support Pack 3) to make sure you have all the latest fixes for the support modules. Could be a discrepance between your SP level of NetWare and the NICI and PKI updates you applied. A newer SP will  let you make sure everything is at a compatible version.

If all else fails, look at the LOAD order of the relevant modules. Novell TID #10073617 shows the recommended order.

Author Comment

ID: 13859884
Sorry for the delay in responding! Thanks for taking the time to reply!

The problem is solved - but I don't know how! After working on this problem all Friday night and early Saturday morning, I shut down the server and went home for some sleep. HTTPSTK was not working at this time.  Before shutting it down, I edited the autoexec.ncf file so that nothing but the topmost commands (setting time, server name, etc.) were executed. After bringing the server back up Saturday afternoon and reading your message, I ran PKIDIAG. It found no errors. So I tried HTTPSTK again just for kicks - and it worked! I don't know if running PKIDIAG, even though it didn't find errors, did something magic, or the fact that nothing else was loaded played a part.

There was another problem I was dealing with that I don't think was related (it persisted even after I got HTTPSTK working), but just in case, I'll record it here for posterity. My original autoexec.ncf loaded the security modules in the following order (the same as recommended in the TID #10073617 you suggested):

(load all other stuff)
LOAD HTTPSTK.NLM /SSL /keyfile:"SSL CertificateIP"

Unless I executed the first set of commands manually, loading the very next command after NILE.NLM - whatever that command might be - locked the system. I finally tracked down Novell TID #10082078 which stated the version needed and recommended the following load order:

Load HTTPSTK.NLM /SSL /keyfile:"SSL CertificateIP"

This still failed. It appeared that GAMS.NLM, autoloaded by NILE.NLM, wasn't getting loaded before the next command was executed. Also, TID #10060090 (though an old one) indicated that there was a timing issue between Java (which was loaded previously) and NILE.NLM.  So I put in a 60 second delay before and after loading NILE.NLM. That's probably overkill, but by that time I was tired and just wanted to go home! Now my server is  a happy camper.

PsiCop, I'll accept your answer.  If you think that running PKIDIAG fixed the problem, even though it turned up no problems, I'll give you an A; otherwise, a B. I'll wait to hear from you on this before I close the problem.

LVL 34

Expert Comment

ID: 13860326
Honestly, no, if PKIDIAG did not report any problems, I would tend to doubt it was the source of the fix. It just eliminated one possibility and let you concentrate on others.

Sounds to me like it was more of a timing issue, like the TID I cited (#10073617) suggested.

In any event, I'm glad to hear its working. Assign a grade as you think proper.

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Sometimes MS breaks things just for fun... In Access 2003, only the maximum allowable SQL string length could cause problems as you built a recordset. Now, when using string data in a WHERE clause, the 'identifier' maximum is 128 characters. So, …
Last month Marc Laliberte, WatchGuard’s Senior Threat Analyst, contributed reviewed the three major email authentication anti-phishing technology standards: SPF, DKIM, and DMARC. Learn more in part 2 of the series originally posted in Cyber Defense …
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question