Windows Forum

Ask something
Discussion Locked

Startup Failures in WinNT4W S/P6a

0 helpful
7 replies

by rawright

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a WinNT4W PC in a P2P network with 2 Win95 PCs which reports one or more services failing at startup. The Event Viewer info is, as usual, completely uninformative, as is the Knowledge Base. The messages are, in order:
>WINS Client (TCP/IP)service failed to start - the system cannot find the file specified.
>The SNMP Service is ignoring extension agent.dll. C:\WINNT\System32\inetmib1.dll because it is missing or misconfigured.
>The TCP/IP NetBIOS Helper service terminated: The specified module could not be found.

Has anyone any idea what specified module is missing???!! And where do I configure inetmib.dll?

7 replies

by duwaned

Hi.

Have you recently made any system changes without re-installing the NT service pack? If so, re-install SP6a, and see if that helps.

The following TechNet article describes some of your errors: Q163595

This article can be seen by going to www.microsoft.com, and searching for the article number above.

Hope this helps.
Regards.
Duwane

by rawright

Although there have been no changes, I re-applied SP6a, just for good measure. None of the errors were resolved by it.

by david__

There are several things you can try, the order may or may not matter that they are performed in. One of the event logs may be corrupted.
1. Boot into DOS. 2. Change directory to %SYSTEMROOT%\SYSTEM32\CONFIG 3. Delete the files SYSEVENT.EVT, SECEVENT.EVT, and APPEVENT.EVT. 4. Reboot NT. This is ment more for sever, but should work in workstation. You might try renameing the files first, incase you want to put them back. Or you can try removeing the NIC drivers and all networking components and adding them back. Try the service pack then.

by rawright

I've R&Rd the drivers and network components several times, each time followed by the service pack, to no avail.

by magetower

On thing to look at is the fact that you are trying to start up a WINS client on a workstation that doesn't need it. You are on a P2P with 95 systems, there is no WINS. The same probably goes for the SNMP. Look at your network properties and see what services you have loaded. You could probably eliminate a couple (unless you are trying to play with SNMP).

Also remove any references to using WINS in your TCP/IP settings.

by rawright

Although this didn't solve the problem, it did provide some clues as to where I should be looking. It appears that Micron installs only a tiny subset of WinNT on a system; the rest has to be manually located as needed.

This discussion is closed to new replies.