This is my scenario. What do I do? System Management Server 2.0 SP3, SQL 7.0. Windows 2000 clients (SP2) crash...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
under these scenarios:
- When they're disconnected from a dial-up connection
- When we release the IP address (if client is using DHCP)
- If the TCP/IP settings are changed either to DHCP from static or from DHCP to a static address
- If connected via Ethernet link to network and the cable is disconnected
Problems occur on a variety of hardware platforms, using either McAfee or Norton antivirus software. The system log records entry:
The Event ID = 1001, Source = Save Dump
Description = The computer has rebooted from a bugcheck. The bugcheck was:
0x00000050(0xfffffff0, 0x00000000, 0xbd472b57, 0x00000000). Microsoft Windows 2000[v15.2195]. A dump was saved in: C: WINNTMinidumpxxxxxxxx.dmp.
We've also narrowed it down to a Windows 2000 client, as the above were tested on an NT 4.0 machine without incident. Once the SMS client is uninstalled, the problems disappear.
I'm guessing the crash dump was not forwarded to Microsoft for analysis?
Despite that, the issue sounds more like its due to the network driver itself, or a compatibility issue between SMS and the network driver. I heard of this issue long ago, pre-SP3, but it sounds like she has SP3 installed. I suggest looking for updated network drivers for the Windows 2000 client.
Dig Deeper on Microsoft Windows 2000 Server Administration
Related Q&A from Rod Trent
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.