cluberti

You need to add the following registry values, as the KB article I referenced instructed you to do: Key: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management Value: PoolUsageMaximum Type: REG_DWORD Radix: Decimal Data: 20 Key: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management Value: PagedPoolSize Type: REG_DWORD Radix: Hexadecimal Data: FFFFFFFF Hopefully after you add the above reg entries and reboot, you'll not have the problem.

No, that's the Application section. Scroll down a little further and follow the instructions for a memory dump of a complete system - it involves keystrokes, not command lines - you'll know you're in the right place when you are adding the "CrashOnCtrlScroll" value to your registry .

For the most part it's built-in to keep people from running XP or Vista as a server OS - the server versions of Windows have no such connection limitations, whereas the desktop OS products are limited to 10 connections on purpose mostly for this reason. Microsoft wants you to purchase a server OS version to run on a server (or a workstation you're using as a server, which I guess does make it a server ).

You're running out of kernel paged pool memory (that's the "storage" that becomes unavailable, because you've used it up) - follow the KB below and reboot, and see if that resolves the issue. If it does not, set the "PoolUsageMaximum" value to 20 (decimal) and reboot, to see if that resolves it.

svchost.exe is crashing, and it's probably the one that contains the audio service. The first suggestion is to make sure you have the very latest drivers for your audio card installed, and see if that resolves the problem. If it does not, download autoruns from Sysinternals and disable all non-Microsoft items and reboot, to see if that resolves the problem. If it does not, let me know and I'll give instructions on how to generate a memory dump of the process the next time it crashes.

The Win32_BaseBoard class has some good info (if the vendor actually provides the data to the OS, and I know at least most Intel boards respond very well to this), as well as the Win32_MotherboardDevice class. Win32_BaseBoard: strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery( _ "SELECT * FROM Win32_BaseBoard",,48) For Each objItem in colItems Wscript.Echo "-----------------------------------" Wscript.Echo "Win32_BaseBoard instance" Wscript.Echo "-----------------------------------" Wscript.Echo "Caption: " & objItem.Caption If isNull(objItem.ConfigOptions) Then Wscript.Echo "ConfigOptions: " Else Wscript.Echo "ConfigOptions: " & Join(objItem.ConfigOptions, ",") End If Wscript.Echo "CreationClassName: " & objItem.CreationClassName Wscript.Echo "Depth: " & objItem.Depth Wscript.Echo "Description: " & objItem.Description Wscript.Echo "Height: " & objItem.Height Wscript.Echo "HostingBoard: " & objItem.HostingBoard Wscript.Echo "HotSwappable: " & objItem.HotSwappable Wscript.Echo "InstallDate: " & objItem.InstallDate Wscript.Echo "Manufacturer: " & objItem.Manufacturer Wscript.Echo "Model: " & objItem.Model Wscript.Echo "Name: " & objItem.Name Wscript.Echo "OtherIdentifyingInfo: " & objItem.OtherIdentifyingInfo Wscript.Echo "PartNumber: " & objItem.PartNumber Wscript.Echo "PoweredOn: " & objItem.PoweredOn Wscript.Echo "Product: " & objItem.Product Wscript.Echo "Removable: " & objItem.Removable Wscript.Echo "Replaceable: " & objItem.Replaceable Wscript.Echo "RequirementsDescription: " & objItem.RequirementsDescription Wscript.Echo "RequiresDaughterBoard: " & objItem.RequiresDaughterBoard Wscript.Echo "SerialNumber: " & objItem.SerialNumber Wscript.Echo "SKU: " & objItem.SKU Wscript.Echo "SlotLayout: " & objItem.SlotLayout Wscript.Echo "SpecialRequirements: " & objItem.SpecialRequirements Wscript.Echo "Status: " & objItem.Status Wscript.Echo "Tag: " & objItem.Tag Wscript.Echo "Version: " & objItem.Version Wscript.Echo "Weight: " & objItem.Weight Wscript.Echo "Width: " & objItem.Width Next Win32_MotherboardDevice: strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery( _ "SELECT * FROM Win32_MotherboardDevice",,48) For Each objItem in colItems Wscript.Echo "-----------------------------------" Wscript.Echo "Win32_MotherboardDevice instance" Wscript.Echo "-----------------------------------" Wscript.Echo "Availability: " & objItem.Availability Wscript.Echo "Caption: " & objItem.Caption Wscript.Echo "ConfigManagerErrorCode: " & objItem.ConfigManagerErrorCode Wscript.Echo "ConfigManagerUserConfig: " & objItem.ConfigManagerUserConfig Wscript.Echo "CreationClassName: " & objItem.CreationClassName Wscript.Echo "Description: " & objItem.Description Wscript.Echo "DeviceID: " & objItem.DeviceID Wscript.Echo "ErrorCleared: " & objItem.ErrorCleared Wscript.Echo "ErrorDescription: " & objItem.ErrorDescription Wscript.Echo "InstallDate: " & objItem.InstallDate Wscript.Echo "LastErrorCode: " & objItem.LastErrorCode Wscript.Echo "Name: " & objItem.Name Wscript.Echo "PNPDeviceID: " & objItem.PNPDeviceID If isNull(objItem.PowerManagementCapabilities) Then Wscript.Echo "PowerManagementCapabilities: " Else Wscript.Echo "PowerManagementCapabilities: " & Join(objItem.PowerManagementCapabilities, ",") End If Wscript.Echo "PowerManagementSupported: " & objItem.PowerManagementSupported Wscript.Echo "PrimaryBusType: " & objItem.PrimaryBusType Wscript.Echo "RevisionNumber: " & objItem.RevisionNumber Wscript.Echo "SecondaryBusType: " & objItem.SecondaryBusType Wscript.Echo "Status: " & objItem.Status Wscript.Echo "StatusInfo: " & objItem.StatusInfo Wscript.Echo "SystemCreationClassName: " & objItem.SystemCreationClassName Wscript.Echo "SystemName: " & objItem.SystemName Next

This seems to me like what you should be focusing on. If the system freezes, and doesn't come back, gather a memory dump of the entire system the next time it "hangs" and let me know when you've got it (I'll provide a location for you to upload it for analysis). I can analyze it and likely tell you what's causing this.

You'll find that under one of the menus at the top, you can hide all Microsoft entries. Do that and click the refresh button, and you'll have a better idea of what to research. You can even try unchecking everything after hiding the Microsoft items (and then rebooting) to see what happens, then start re-checking things a few at a time and restarting to see which ones seem to cause the errors you are seeing.

You are correct. Windows 2000 Professional does not include any terminal services components, and as such you cannot RDP to it. You must use another remote control software package other than RDP, such as VNC. Windows 2000 Servers can be connected to via RDP, if you install terminal services in remote administration mode.

DHCP, DNS, and WINS databases can be replicated or backed up and restored manually, and AD-related data is already replicated to any additional DC in the domain (make sure they're both set as global catalog servers, though). As to file services, that can be taken care of with the second DC via DFS (clustering would also work, but you really shouldn't cluster domain controllers).

You could always use the backup utility (start > programs > accessories > system tools) to back up vital files and system state data - however, again, this will only be able to restore data backed up with this tool. If you have a server that has gone south and you need to repair it, your only options are repair install (there are special steps if it's a domain controller) or rebuild completely if repair install doesn't work. It is almost always better to have a backup (either to tape or to another disk-based location) than to rely on system restore or a repair install - you should always back up your servers.

If you created a restore point on said date, then yes, you would be able to do a system restore to that point using the utility (assuming it had not been deleted due to low disk space or age). However, system restore cannot restore to any point if you don't have a saved point to restore to - it's not a "smart" utility, and it can't magically go back in time. If you have a restore point you created, you can restore to it. If you don't have any restore points created, you can't restore the server to a previous time and date.

No, actually, you don't. Starting it at thread priority 15 will more than likely hang your box entirely. And really, you shouldn't run any processes at priority 15 - you can really screw with the scheduler and slow critsec handling, possibly causing race conditions that can be unrecoverable. Take a good read of the Windows Internals book if you want to know more about why this is a bad idea to set any process to priority 15 for any length of time. One question springs to mind - why exactly do you need task manager at high priority?

No problem. What I mean, in basic terms, is to visit this page and click the "Download Autoruns" link at the bottom of the page. Once autoruns is downloaded, extract and run "autoruns.exe". Instructions on using autoruns are on the page I linked to, if you need help using it.

Is this the only DC at the site or on the domain? If so, I strongly, STRONGLY recommend not doing what you're about to do.

Have you gathered network traces on the client and server simultaneously, to see what's happening on the wire when the error occurs? Also, it is possible it's a client issue - but if you've reinstalled multiple times, unless you've reinstalled each time _exactly_ the same as before... I'd start with network traces on client and server simultaneously, and go from there.

Perhaps network traces and replmon data would assist - that error code signifies a bus reset, usually due to TCP timeouts. You'll likely need network traces and replmon data to catch this.

There aren't really any ways to "lock" someone to a logged-on status, but setting a notification message before logon is a good start, and disabling remote connections via RDP is another good one (and use VNC or some other remote desktop solution to access the console). Not really a whole lot else you can do, honestly.

Well, if it's crashing in ntdll.dll, then it's crashing when accessing something either in, or through, the kernel. Download autoruns and disable all non-Microsoft items, reboot, and see if the problem still occurs.

This would be a good business justification for terminal servers running Citrix, publishing said applications - the apps run as admins on the server, but the user can only interact with the redirected application running on their (non-admin, low-rights-user) machine, and can theoretically not screw up their machine or the TS they have high rights to (because they can only run the app on their workstation, and cannot actually log into the TS to get a full desktop). Just a thought .

Take a look here: http://www.jameskovacs.com/blog/DebuggingAsANonAdmin.aspx

Well, it could be the router you're hitting at Telcove, or it could be the hop before it that's misconfigured. You really should get with your ISP to trace this through their network - i.e., a trace by the ISP on your switch port and their border router before you hit telcove (good luck, some do, some don't provide this kind of help). You could at least see the packets on your ISPs network to know if it's your ISP or telcove. If that's the case, and it really is telcove, your only real options are switching ISPs so you don't go through telcove to hit this site, or having your ISP route your packets destined for that site through a different route (again, good luck). An ISP with fewer hops to a core backbone is preferable, but you will pay for the privilege (and it is worth it, if you're a heavy user). It's not your problem, and the likelihood that it's your ISP is also very slim. Again, if telcove won't give you (or your ISP, if you can get them behind you) any help, switch ISPs so you don't ever go through telcove to hit that site. Others obviously don't, so it should at least be a possibility .

You could change the guest account to proxy to 127.0.0.1 or use a .pac file, but otherwise you really can't do that, at least not without someone being able to just turn things like that off. The best way is something external to the machines, before the ADSL modem - a proxy would be needed, and could be used to only allow access to valid user ids and passwords (regardless of account being used on the machine at the time, guest or otherwise).

Check this KB: http://support.microsoft.com/kb/320855 The relevant part: Configure Outlook 2003 or 2007 to use Exchange RPC over HTTP (make sure your admin has configured this on the Exchange servers!), and it will work. RPC connections do not work through ICS, and Outlook uses RPC to talk to Exchange by default. That's why it works to POP or SMTP, but not Exchange native.

That error message (0x80070020) means that there's a sharing violation - something on the system has a file locked that the update needs to install. Perhaps run Process Monitor (from sysinternals) while attempting the update, to see what file is locked (either Access Denied or Sharing Violation will be reported in ProcMon).