Niakwa, Inc.

    

 


What's News
NPL Products
NPL Support
NPL Downloads
System Integration
swiggle_small.gif (991 bytes)

swiggle_small.gif (991 bytes)

September 7, 2004 No. 100

Issues with XP Service Pack 2

One of the features Service Pack 2 for Windows XP adds is Windows firewall.  By default the firewall is enabled to function for internet and local area network access.  In order for NPL Secure type security to function properly, the firewall must be disabled or configured to allow rtiwin32 and rtpwin32 to run.  Additionally, a Network Access policy must be modified. 

If the application uses a feature, like NDM, that relies on third party software, such as Pervasive, to function, additional steps may be needed to enable the third party application.  Proper configuration advice can only be supplied by the third party’s software support team.

Contents:

NPLSecure installations

Scenario 1

NPL is installed on a Windows server.
XP Pro workstation.
NPL Secure type security.
NPL was working properly until SP2 was applied to the XP workstation.  

Executing NPL, the NPLSecure monitor displays for a long time (Approx. 45 seconds), and a message box displays with

NPLSecure error  0x24 “The RPC server is unavailable”.

NOTE: Usually when this error occurs, pinging the fully qualified server name fails.  When NPL is being blocked by XP’s firewall, pinging the fully qualified server name succeeds. 

The simplest and fastest way to correct this error message is to disable XP’s firewall.   If  XP’s firewall is to remain active it must be configured to allow NPL to function. 

Follow these steps to configure XP’s firewall to allow NPL to run:

  1. Log in to the XP workstation as administrator
  2. From the START button open Control Panel / Windows Firewall.
  3. Under the “General” tab leave the “Firewall” setting on.
  4. Under the “Advanced” tab, leave the check mark for “Local Area Connection”
  5. Under the “Exceptions” tab, select “Add Port”, enter “NPLSecure” for the name, 135 for the port, and select “TCP”.
  6. Click on the “Change Scope” button and select “My Network”.
  7. Still under the “Exceptions” tab, select  “Add Program”, and “Browse” to rtiwin32.exe and rtpwin32.exe, again select “My Network”  for the scope.

Scenario 2

After applying Service Pack 2 to Windows XP, starting NPL causes the error:

“Access Denied”

These are the steps to fix this.

  1. Log in to the XP workstation as administrator
  2. From the START button open Control panel / Administrative Tools / Local Security Policy / Security Options.
  3. Scroll down to “Network Access: Let everyone permissions apply to anonymous users” and change the setting from “Disabled” to “Enabled”.

Close the windows.  NPL should run as before.

Scenario 3

NPL is installed on a Windows server

XP Pro workstation.

NPL Secure type security.

NPL was working properly.

SP2 is added to the XP workstation and NPL stopped working.

When trying to execute NPL the NPL monitor displayed for a long time (Approx. 35 seconds), then  a message box displays with the error:

Not enough space is available to complete this operation”.

The simplest and fastest way to correct this error message is to disable XP’s firewall.   If  XP’s firewall is to remain active it must be configured to allow NPL to function. 

Follow these steps to configure XP’s firewall to allow NPL to run:

  1. Log in to the XP workstation as administrator
  2. From the START button open Control Panel / Windows Firewall.
  3. Under the “General” tab leave the “Firewall” setting on.
  4. Under the “Advanced” tab, leave the check mark for “Local Area Connection”
  5. Under the “Exceptions” tab, select “Add Port”, enter “NPLSecure” for the name, 135 for the port, and select “TCP”.
  6. Click on the “Change Scope” button and select “My Network”.
  7. Still under the “Exceptions” tab, select  “Add Program”, and “Browse” to rtiwin32.exe and rtpwin32.exe, again select “My Network”  for the scope.

NOTE: By default DCOM uses port 135.  You may need to enable logging for the firewall and inspect the log to determine if a different port is being used.

Novell installations

For XP workstations on a Novell server the Novell client must be updated to the latest version.

Scenario 4

Novell server with XP workstation using Novell client v 4.90 SP1.

The runtime was operating without a problem. 

Service Pack 2 is applied to the XP workstation.

The runtime would start and run but trying to “LISTDCT” the contents of any diskimage produced:

MS-DOS Error 7B - “Illegal character or malformed file system name.”

Downloading and applying Novell Client v 4.90 SP2 corrected the problem.

NetBIOS installations

There have been no reports where installing SP2 to XP effected NetBIOS runtimes.

 

 

blank.gif (841 bytes)


Niakwa, Basic-2C and NPL are trademarks of Niakwa, Inc. All other products mentioned are registered trademarks or trademarks of their respective companies.

Questions or problems regarding this web site should be directed to webmaster@niakwa.com.
Copyright © 1996-2010 Niakwa, Inc. All rights reserved.
Last updated: Thursday January 07, 2010.