Where I’m @

20060825

Baffled
We are trying to sort out a self-hating server. It is still running Windows 2000 (story of printing issues with the firewall in Server 2003 and an uncommunicative printer), and the event log, backed up by nbtstat -n is showing a conflict for the NetBIOS name in its workstation entry. But the source IP address in the event properties is the server itself.

And when we tried to poke around with winscl from an administering machine, we received the modal error “The procedure entry point WinsCheckAccess could not be located in the dynamic link library WINSRPC.dll”. Searching for this error message online gave us bupkes. Perhaps posting it here along with a contact email (trip_wins at this domain) will help us as well as others.

posted by Tk at 10:08 • • sealed in amber

20060801

So Easy to Do, So Easy to Forget
That describes so many things for us. But in this case, we just wanted to enter into this, our own personal KB something about what to do when the problem on a Dell PowerEdge server (2850, in our case) has been fixed but the LCD is still flashing. One way to stop the blinking, in addition to those provided by Dell, is to use DSET. In our GUI, we access Start --> Programs --> DSET --> Clear ESM Log. You will get a confirmation in a command window. The same thing can be achieved on the command line with clearesm -pause, either from the DSET bin directory or with that directory included in PATH.

posted by Tk at 09:04 • • sealed in amber