Marvin Huffaker Consulting: Novell Support Specialist  

Contact Information
Marvin Huffaker Consulting
3454 N San Marcos Place
Suite 7
Chandler, AZ 85225

Toll Free: 1-888-690-0013
Local AZ: 480-988-7215
Fax: 480-988-7216

http://www.redjuju.com

Accessing IPX Network from Windows XP

Problem: Some users running Windows XP and the Novell Client are unable to browse, attach to, or login to an IPX based network. An IPX network is typically used by Novell NetWare servers running NetWare 3.1x and NetWare 4.1x. It is possible to also have NetWare 5.x and NetWare 6.x servers that are configured with IPX. Therefore, this tutorial could potentially apply to any Novell server configuration. This tutorial would not apply if running NetWare 5.x and NetWare 6.x servers in an IP only environment.

ISSUE: There are two likely causes. First, you may not have IPX installed on the workstation. Second, the Windows XP system may not be correctly identifying the correct IPX network. This essentially makes it impossible to locate any Novell services when relying on IPX. This problem seems to be more prevalent on laptop computers.

SOLUTION 1: The first solution is to install the latest Novell client, do a CUSTOM install, and make sure to choose "IP and IPX" during the process. The screen shot below demonstrates the setting that needs to be configured during the Novell Client installation routine:


Solution 2: If solution #1 doesn't fix the problem, it may be necessary to manually configure IPX within the Networking Properties of the workstation to correctly identify the IPX information. Before it can be manually configured, you need to know what to configure it with. The screen shots below demonstrate how to get the information and configure it on the Windows XP system.

From the NetWare Server Console, Type "CONFIG" to identify the Frame Type and NetWork Segment Number.

These values will be used to configure the IPX component in the NetWare Client.

On the Windows XP Workstation, open the Network Properties for the Local Area Connection, and find:

"NWLink IPX/SPX/NetBIOS Compatible Transport Protocol"

Click on Properties.

In general, The Internal NetWork Number should always be "00000000" (eight zeros).

The Frame type and Network number should be configured so that it is the same as the settings that were discovered from the server console in the first step.

NOTE: By default, the frame type is set to "Automatic" which seems to be a problem with some workstations. Forcing the frame type manually has resolved the problem for myself a number of times.


Do you have a serious problem with your Novell systems? Marvin Huffaker Consulting can solve it. Contact us here.

novell support consultant
we are novell experts
Marvin Huffaker Consulting: Novell Support Specialist. Nationwide Support. Based in Phoenix and serving the entire Phoenix Metro Area including Tempe, Scottsdale, Mesa, Chandler, Tempe, and Gilbert.

Marvin Huffaker Consulting, Inc. is a professional services consulting firm. Our areas of expertise are premium contract services, messaging and collaboration, virtualization, disaster recovery / business continuity, workgroup network solutions, and turnkey appliance solutions. Our comprehensive offerings include email management and support, server infrastructure support, managed services, email implementation and support, and more. We utilize virtualization in many of our solution sets, and we recommend and support best in class solutions from Virtual Iron, Compellent, Lefthand Networks, Novell, Gwava, Messaging Architects, Astaro, and more. Copyright © 2002-2008 Marvin Huffaker Consulting, Inc. all rights reserved. REDJUJU and the MHC logo are trademarks of Marvin Huffaker Consulting, Inc. All other trademarks are property of their respective owners. Read our Privacy Statement