ALI Blog

Executive and Technical Blogs

  • Home
    Home This is where you can find all the blog posts throughout the site.
  • Categories
    Categories Displays a list of categories from this blog.
  • Login
    Login Login form
Some Lexmark printer software and/or drivers can cause problems whereby the Print Spooler service conflicts with the Server service on Windows workstations and servers.  Symptoms include very long (15 minute) waits on first starting Windows before it responds, as well as events logged in the System section of Event Viewer for "The Server service hung on starting".  The Print Spooler is attempting to start at the same time, which causes Server service to hang.
 
The solution is to make the Print Spooler service dependent on the Server service, so it will not start until after the Server service is started.
  1. Click Start, and then click Run.
  2. In the Open box, type regedt32, and then click OK.
  3. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler
  4. Click Add Value on the Edit menu.
  5. Type DependOnService in the Value Name box.
  6. Click REG_MULTI_SZ in the Data Type box, and then click OK.
  7. Type LanmanServer in the Data box, and then click OK.
  8. Click Exit on the Registry menu to quit Registry Editor.
  9. Restart your computer.
For steps 4 through 7: If the "DependOnService" value already exists and has an entry, you can add another by double-clicking the value and entering it on a new line.

If you need help with this or any other support issue, please don't hesitate to contact me at the ALI Technical Assistance Center at (540) 443-3398.

Brice Stevens
Advanced Logic Industries
Technical Assistance Center (TAC)
tac@ali-inc.com

Hits: 20146

On HP workstations and laptops that use high-density (750GB-1TB) hard drives and are running Windows, older versions of the Intel Rapid Storage Technology driver can cause various problems including the inability to run Windows Update. 

The error message will state that the Windows Update service is not started, but if you check it, it is running. 

The solution is to download version 9.5.6.1001 (software package SP47845) or newer of the Intel Rapid Storage Technology driver from HP's support website.  

If you need help with this or any other support issue, please don't hesitate to contact me at the ALI Technical Assistance Center at (540) 443-3398.

Brice Stevens    
Advanced Logic Industries
Technical Assistance Center (TAC)
tac@ali-inc.com

Hits: 13761
Our TAC has recently been encountering another variation on the "fake antivirus/scanner/fixer/etc." plague of malware. 
 
This one presents itself as Windows Repair and does the usual scare tactics of saying your workstation is infected, files/registry/hard drive sectors are damaged/missing, and so forth.  This one, however, goes a step further and sets various folders--including the current user profile folder--to be Hidden.  A telltale symptom, beyond the fake Windows Repair window, is a completely blank desktop with no program, file, or folder icons of any sort.  This can make it seem as if you have lost everything.
 
Here's how you handle this: 
 
Open an Explorer or My Computer window (use the WindowsKey-E combination if needed, or type explorer.exe into the Run command in the Start Menu)
Go to the Tools menu>Folder Options, then the View tab 
Scroll down and choose the radio button to "Show hidden files and folders".  This will let you see the items that the virus set to Hidden. 
If you then right-click your user profile folder (under Documents and Settings for Windows XP, or under the Users folder for Windows Vista and 7) and choose Properties, you will see a checkbox for "Hidden" at the bottom.  Uncheck that, and choose to apply to all files and folders when it gives you that option. 
 
You may have to do this for several other folders, depending on what the virus touched, but again they should all show up once you choose to "Show hidden files and folders" as described above.
 
You'll also need to contact your IT support to update your virus protection.  If you need assistance, please do not hesitate to contact us!
 
 
 
ALI Technical Assistance Center (TAC)
(540) 443-3398

Posted by on in Technical

GroupWise 8 & 7 users should check their security patches RIGHT AWAY! 
The GroupWise Internet Agent (GWIA) has a vulnerability.

If you need assistance with resolving this GWIA issue, please do not hesitate to contact our TAC.


 

Security Vulnerability - GroupWise 8 Internet Agent TZID (VCALENDAR) Variable Parsing

This document (7007638) is provided subject to the disclaimer at the end of this document.

Environment

Novell GroupWise 8
Novell GroupWise 8 Internet Agent
 Affected versions: GroupWise 8.0x, 8.01x, 8.02, 8.02HP1
Previous versions (such as GroupWise 7.x) of GroupWise are likely also vulnerable but are no longer supported. Customers on earlier versions of GroupWise should, at a minimum, upgrade their GWIAs and associated Domains to version 8.02HP2 in order to secure their system.

Situation

The GroupWise Internet Agent (GWIA) has a vulnerability in the way that it parses the TZID variable within a received VCALENDAR message, which could potentially allow an unauthenticated remote attacker to execute arbitrary code on vulnerable installations of GWIA.  This vulnerability affects GWIA running on all supported server OS platforms (Windows, SuSE Linux, & NetWare).
 
This vulnerability was discovered and reported by Anonymous working with TippingPoint's Zero Day Initiative (http://www.zerodayinitiative.com), ZDI-CAN-967
 
Novell bug 657818, CVE-2010-4325

Resolution

To resolve this security issue, update GWIA to version 8.02 Hot Patch 2 (or later).

Bug Number

657818

Document

Document ID: 7007638
Creation Date: 01-21-2011
Modified Date: 01-28-2011
Novell Product: GroupWise

Disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

Posted by on in Technical

Are you running DHCP on your OES 2 server?
Would you like to view the DHCP leases in use?
Well, now you can in OES 2 SP3!

Please contact the ALI TAC to schedule the upgrade and configure DHCP for this feature!


 


 

 

Viewing Dynamic Leases Under The DNS/DHCP Management Console From OES 2

This document (7006450) is provided subject to the disclaimer at the end of this document.

Environment

Novell DHCP Management Console
Novell DNS Management Console
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3

Situation

Starting with OES 2 SP 3, administrators can view DHCP leases utilizing the DNS/DHCP management console; however, before doing so one of the following errors or messages may be encountered:
  • Configure the "DHCP server IP address" to view the leases
  • Configure the "omapi-key" setting of the DHCP server object to view the leases
  • Configure the following DHCP server settings to view the leases: DHCP Server IP address, omapi-key
  • ERROR: EOMAPI1
  • ERROR: DHCP server connection failed

Resolution

To address the "DHCP server IP address" portion of the message(s), do the following:

  1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
  2. Click on the 'DHCP (OES Linux) tab toward the top of the console
  3. Find the DHCP Server object at the bottom of the console and select it
  4. Toward the top-right hand side of the console select the GENERAL tab and find the section called DHCP SERVER
  5. Click the ADD button and enter the IP address of the DHCP server
    • NOTE:  If doing this step on OES 2 SP 2 the buttons may be greyed out.  This is due to the schema not being extended.  This option is officially supported on OES 2 SP 3
  6. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)
To address the "omapi-key" portion of the message(s), do the following:
  1. The first step in addressing this issue is to create a TSIG key if one has not already been created.
    • NOTE:  At the time this TID (Technical Information Document) was created, the secret for the TSIG key must be divisible by four (4).  If it is not DHCP will not load.  For instance, if the key's secret is set to SECRET then DHCP will fail to load as the secret is not divisible by four; however, if SECRET12 is used instead, then DHCP will load as the secret is now divisible by four.
      1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
      2. Click on the 'DHCP (OES Linux) tab toward the top of the console
      3. Highlight the SERVICE object (assuming it has already been created) and click on the CREATE button located at the top, left-hand side of the console (looks like a 3-dimensional box)
      4. Select 'TSIG Key" and assign the KEY NAME and SECRET.  Keep in mind the note above regarding the secret to make sure the number of characters used in the secret is divisible by four
      5. After hitting CREATE on the key the key should show up under the service object that was highlighted
  2. The second step in addressing this issue is to add the omapi-key setting itself
    1. While in the DNS/DHCP management console, and with the 'DHCP (OES Linux)' tab selected, highlight the DHCP SERVER object toward the bottom of the console
    2. Select the SETTINGS tab toward the top, right-hand side of the console (next to the GENERAL tab)
      • NOTE:  At this point the administrator should see a setting for the OMAPI-PORT already configured for port 7911.  If it is not there, the click the MODIFY button, find the setting, add it and assign it a port of 7911 (which is the default)
    3. Click on MODIFY and find the OMAPI-KEY setting (likely at the bottom of the list).  A drop down menu should appear after adding it, and a list of found TSIG keys should be presented.  Select the appropriate key
      • NOTE:  If the key doesn't show up at this point, review the steps above and create the key as specified
    4. Review the settings and make sure there is an OMAPI-PORT and OMAPI-KEY setting, each assigned a valid value
    5. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)

At this point it may be necessary to hit the TREE REFRESH button located at the top, left-hand side of the console.  It is found next to the SAVE button.  Once the tree refresh is complete, expand the SUBNET and then the POOL to view any current leases that may be assigned out.  If one of the following errors is encountered, it is likely due to the fact that the leases file has not yet been populated with any leases.  This error should resolve itself once there is a lease to be found in the dhcpd.leases file on the server:

  • ERROR: EOMAPI1
  • ERROR: DHCP server connection failed

NOTE: The 'omapi-port' and 'omapi-key' settings cannot be added, modified, or managed from iManager in any way at the time this TID was written.  This has been reported to Engineering.   The steps described in this TID should be completed from the DNS/DHCP Management Console.