Categories
Symantec Backup Exec Error id 34113
The Backup Exec error id 34113 was being displayed on my Windows 2003 server with Backup Exec 12 installed. This error corresponds to "out of memory." The error apparently stems from one the following two issues withe the volume shadow copy service:
The VSS simply lacks a required windows update, which is KB940349.
The VSS has a memory leak and needs to be patched with KB870973.
My problem ...
openSUSE 11 PDC using Samba and LDAP
Encountered an issue today while playing around with openSUSE 11 and setting it up as a primary domain controller using Samba and LDAP. After installing and configuring the required software on the openSUSE box I joined an XP workstation to the domain. I thought that success was mine at this point given it joined correctly, but alas as I tried the initial login to the ...
Network Adapter Priority Server 2008 Core
Ran into another issue with Server 2008 Core install. I wanted to change the network card priority... normally an easy task (advance settings in network connections,) but of course this doesn't exist in the core install.
The solution for this is to run a command to get the adapter id list, then to edit the registry. Run the following in an elevated command prompt: wmic nicconfig ...
OS X 10.4 VPN Service Wont Stop
Had a friend call me with an issue on his Mac OS X 10.4 server. It seems after enabling the VPN server it started to take up 50-80 percent of the CPU load. Now I would have prefered to troubleshoot this issue but he just wanted to disable the service and use a different peice of software for the VPN server (I would reccomend VPN-X ...
Configuring SNMP on Windows Server 2008 Core Installation
I've been messing around with Server Core for a little bit now. I've got a core installation running Hyper-V, and I would like to monitor the server via SNMP.
I've already enabled SNMP via start /w ocsetup SNMP-SC.... but I can't for the life of me figure out how to set the community strings, etc..
I've got remote administration enabled, and can add and see the services ...
KMS vs. MAK Vista/Server 2008 Activation
Key Management System vs Multiple Key Management
There seems to still be some confusion regarding the activation methods for of Microsoft Windows Vista and Server 2008. The two methods are Key Management System and Multiple Key Management. Microsoft recommends KMS for environments with more than 25 computers.
Pros for KMS include the fact that there is no client configuration necessary and the method only requires the client ...
Blue Screen – Page Fault in Non Paged Area
Encountered an error on a server today that I haven't seen in awhile. The system was BSOD'ing during windows loading. Almost always this issue is related to a bad stick of memory. Simple troubleshooting technique of trying one stick at a time showed that the second stick of memory was in fact bad. After replacing the stick with a new one and running Memtest 86+ ...
SLES 10 YAST Network Configuration
Noticed an issue with the latest release of SLES as I was configuring network options in YAST. The spot where the option for gateway would be was no longer there, and the server was grabbing the wrong gateway. In case anyone else encounters this and didn't know, you need to use the route command to add the gateway.
route add default gw mango-gw
adds a default route ...
Reset Domain Administrator Password
Today I encountered the situation where I had to do some administrative work on a server that no one knew the domain administrator password for. The following are the steps I used to reset the domain administrator password, I have tried to make it as foolproof as possible. This was performed on Microsoft Windows Server 2003 but will also work on server 2008.
The only two ...
OpenSuse 11.1 Install cd:/content:invalid signature Error
Encountered the "cd:/content:invalid signature" error today installing OpenSuse. The error presented itself selecting installation from the boot menu on the dvd. All of the following failed to help - re burning the ISO, downloading the ISO over, verified the MD5 checksum, burnt the ISO again, and still the same issue. The cause of the issue ended up being incorrect date settings in the bios. After ...