NETAPI.DLL Failure code is 02 ?

Hermann Berg

unread,

Nov 18, 1996, 3:00:00 AM11/18/96

to

Hello!

When I start Win3.11 the following strange behaviour occurs:

-Win3.11 seems to start normal
-a few seconds after banner and 'xylophon'-sound appears, the cursor is
blocked, system seems to be crashed
-after approx. 1 min. the cursor can be moved again and system boots to end
-very often system crashes; no system crash, if Windows is startet with '/n'

I started Windows with the '/b'-parameter. The only error I can recognize is
the following:

LoadStart = NETAPI.DLL
LoadFail = NETAPI.DLL Failure code is 02

Does anybody has a hint?

further informations:
486 EISA 50MHz PC
Network Adapter: 3Com 3C509B-COMBO

Thank you very much!!!

Hermann

Jaime Metcher

unread,

Nov 19, 1996, 3:00:00 AM11/19/96

to

Well, this sounds very much like a network problem. The 1 minute pause
could be any number of things - difficult to say without knowing
anything about your network (probably difficult to say *with* knowing).
Any time the system looks for the network this can happen - looking for
DHCP server, broadcasting for name conflicts, re-establishing old
connections.

As for the NETAPI.DLL code, this is generated when WFW is installed and
is not a problem *at that time*. The /b option appends to any existing
bootlog.txt, so to get the real story, delete bootlog.txt before running
Windows.

--
Jaime Metcher
Systems Programmer (i.e. plugger-in of printers and replacer of toner)
University of Queensland, Australia.

Hermann Berg

unread,

Nov 20, 1996, 3:00:00 AM11/20/96

to

Hello Jaime,

thanks for your answer.

>Well, this sounds very much like a network problem. The 1 minute pause
>could be any number of things - difficult to say without knowing
>anything about your network

The network is a big LAN in our research facility. For exactly which
spezifications it would be helpful to get informations; so I can ask for
details in the LAN-Group?

>(probably difficult to say *with* knowing).
>Any time the system looks for the network this can happen - looking for
>DHCP server, broadcasting for name conflicts, re-establishing old
>connections.

Maybe this observation is important:

If I try to link a drive the network error 2242 (What does it mean? Where can
I look up such error codes, I didn´t found it in the user's guide?) occurs.
Furthermore, I can´t see my machine in the host-list.

>As for the NETAPI.DLL code, this is generated when WFW is installed and
>is not a problem *at that time*. The /b option appends to any existing
>bootlog.txt, so to get the real story, delete bootlog.txt before running
>Windows.

... yes, I tried it, you're absolutely right...

bye, Hermann

Jaime Metcher

unread,

Nov 21, 1996, 3:00:00 AM11/21/96

to

Hermann Berg wrote:
>
> Hello Jaime,
>
> thanks for your answer.
>
> >Well, this sounds very much like a network problem. The 1 minute pause
> >could be any number of things - difficult to say without knowing
> >anything about your network
>
> The network is a big LAN in our research facility. For exactly which
> spezifications it would be helpful to get informations; so I can ask for
> details in the LAN-Group?
>

> Maybe this observation is important:
>
> If I try to link a drive the network error 2242 (What does it mean? Where can
> I look up such error codes, I didn´t found it in the user's guide?) occurs.
> Furthermore, I can´t see my machine in the host-list.
>

SNIP
> bye, Hermann
>
For information on error codes, try typing NET HELP [errornum] at the
command line. I typed NET HELP 2242 and it said this is a password
expired error. Bear in mind that these error messages are the system's
best guess - you might get the same message for other reasons.

Anyway, it seems that you may be having some kind of authentication
difficulty. It's possible that you can't see the server (is it in the
host list - use NET VIEW), your account has been disabled (ask your
sysadmin), your password really has expired (a long shot - too easy),
the disk you are trying to link to has its own password separate from
the user access control (bad luck), or you have a bad or flaky network
card or driver (install updated drivers/try another network card).

Useful troubleshooting information is: your server's OS; your client
OS; your client network software; network protocols in use; network card
and driver version; and what network functionality, if any, you *do*
have. It would also be useful to know how long you wait before deciding
the machine has crashed - as you have seen, a machine waiting on a
network timeout can look very much like it has crashed. Try walking
away and doing something else, and see if it wakes up after a while.
You decide how long a "while" is - I give it 10-15 minutes if I'm really
keen.