Windows Forum

Ask something
Discussion Locked

Spool/Connectivity/SNMP Problems

0 helpful
5 replies

by trudy's support

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a stand alone nt 4 file/print server that houses our accounting software. I have two workstations running WinME and Win2K. After rebooting server, all can talk to each other. After other workstations (10 in all minus the two mentioned) print, recieve the following error. Spoolss.exe entry point not found. SnmpSvcGetEnterpriseOID could not be located in snmpapi.dll. SNMP had been installed and then removed. So...what else could be calling that dll to fire? Only concern is that I have to OK through the message before any workstations can print, and then the two machines I mentioned can't connect to the server.

5 replies

by mckaytech

The timing on your question is interesting because just this past weekend, I had two NT workstations with the SnmpSvcGetEnterpriseOID error message and that was the first time I had seen it. These machines also could not connect to the network, as in your case.

In our case, the hard drives were full (less than 4meg free) and once I created some free space by deleting unneeded files and rebooting, the network connection problems resolved but the SNMP error message persisted until I disabled the SNMP service in Control Panel.

I don't know if this helps, but I was just struck by the co-incidence.

paul

by matt_help

Could be a couple of things..
Try applying the latest Service Pack after you've installed SNMP.
Or, in your SNMP config.. allow for read/create access which allows for SNMPSVCGET requests.
I hope this helps!

This discussion is closed to new replies.