1. No category

How to transition
from IPX to pure IP
Networking Services
DEPLOYMENT GUIDE
w w w. n o v e l l . c o m
table
of
contents
How to transition
from IPX to pure IP
2
M O V I N G TO A P U R E I P
ENVIRONMENT
2
WHY MOVE?
2
T H E PAT H T O P U R E I P
8
HOW NOVELL ADDRESSED IPXD E P E N D E N T S E RV I C E S
9
M A I N TA I N I N G I P X S E R V I C E S
T E M P O R A R I LY I N A P U R E I P
ENVIRONMENT
10
A D D I T I O N A L I N F O R M AT I O N
How to
transition from
IPX to pure IP
2
Moving to a
pure IP
environmeNt
With the release of Novell NetWare 5 (and above), you can now move to a pure IP
¨
¨
environment, even if you are still using NetWare Core Protocols. ThatÕs because in
NetWare 5 (and above), all NetWare Core Protocols can use the TCP/IP transport protocol
giving you the ability to run in a pure IP environmentÑpure in the sense that it doesnÕt
retain an IPX-based encapsulation (or, in the case of NT Server, a NetBIOS encapsulation).
In some cases, you will need to continue to
WHY MOVE?
Why would you want to move to a pure IP
maintain IPX services temporarily in your new pure
environment? There are many possible
IP environment. The section of this document,
reasons, including:
ÒMaintaining IPX Services Temporarily in a Pure IP
¥ To simplify your routing infrastructure by
moving to a single protocol.
Environment,Ó describes a practical solution.
T H E PAT H T O P U R E I P
¥ To create a more uniform WAN and remote
Once youÕve decided to make the transition
connectivity options.
to Pure IP you need to answer two questions:
¥ Your router vendor may charge more for
support and upgrades of multiple protocols.
¥ To reduce the load on NetWare/NDS servers
¨
that currently support the IPX protocol and
its Name Space Providers, Bindery and SAP.
1. What are your IPX dependencies?
2. How quickly do you need to make the
transition?
The answer to the first question is important
The following section of this document,
because your ultimate goal is to eliminate all IPX
ÒThe Path To Pure IP,Ó describes a stepÐby-step
dependencies. The answer to the second question
procedure for moving to pure IP. Novell
determines whether you must move your entire
developed this procedure in migrating their
network to pure IP all at once, or whether you
large, global network to pure IP. (During the
can make the transition in phases.
transition, Novell migrated over 750 servers and
You can move from an IPX environment
more than 6,000 workstations.) In some of the
(or a mixed IPX/IP environment) to a pure IP
steps, NovellÕs approaches to some of the tasks
environment by performing the 12 steps presented
are pointed out to help you address certain issues.
in this section.
How to
transition from
IPX to pure IP
3
Step 1. Implement TCP/IP Routing,
Security and Management
Step 2. Implement DNS/DHCP
DNS allows you to refer to network resources by
To make the transition to pure IP, you must
begin to route the protocol. But before you
route your first IP packet, you should have a
user-friendly DNS names rather than obscure IP
addresses. With NetWare 5, you can access a server
using its IP address or fully-qualified DNS name.
TCP/IP security infrastructure (such as firewalls)
Anyone who has had to manage IP addresses on
in place. If you have already been using TCP/IP,
a large scale is probably already familiar with the
you may already have a security infrastructure
HELPFUL
D O C U M E N TAT I O N
Migrating to Pure IP with
NetWare 5:
http://developer.novell.com
/research/appnotes/1998/se
ptembe/a3frame.htm
IP address management simplification provided by
Migrating from NetWare/IP
DHCP. DHCP is especially useful with NetWare 5
to NetWare 5 and Pure IP:
because it not only simplifies the assignment and
http://developer.novell.com
administration of client IP addresses, but also
/research/appnotes/1999/fe
allows you to distribute Novell Client configuration
bruary/a6frame.htm
in place.
YouÕll also need tools to monitor the health of
your TCP/IP network. If you have already been
using TCP/IP, you may already have a monitoring
infrastructure in place. You may also be able to
use some of the tools you have for monitoring the
health and performance of your IPX network to
monitor your IP network.
You may also need to tweak your network to
accommodate the new TCP/UDP ports used by
NetWare 5:
TCP 524ÑNCP RequestsÑSource port will be
a high port (1024-65535).
information such as Preferred Tree, Preferred
Server, SLP Directory Agent addresses, SLP Scope
and Migration Agent addresses.
DHCP also simplifies network usage.
For example, you can use DHCP to give clients
HELPFUL
the name of the corporate tree, the name of a
D O C U M E N TAT I O N
local server holding replicas, any local Directory
Protocols and ports used
Agents and other information. That allows users
by NetWare 5 IP:
to login from any location without wrestling with
http://support.novell.com/
IP settings or client configuration.
cgi-bin/search/
UDP 524ÑNCP for time synchronizationÑ
Source port will be a high port.
searchtid.cgi?/
UDP 123ÑNTP for time synchronizationÑ
Step 3. Design SLP Implementation
10013531.htm
Source port will be the same.
UDP 427ÑSLP RequestsÑSource port will be
the same (427).
TCP 427ÑSLP RequestsÑSource port will be
the same (427).
TCP 2302ÑCMDÑSource port will be a high port.*
UDP 2645ÑCMDÑSource port will be the same
(2645).*
*These ports are only necessary if your organization
is planning to use CMD as part of the IPX to IP
Migration strategy.
Running NetWare in a pure IP environment
eliminates IPX SAP packets. IPX SAP provides two
services: dynamic discovery and the ability to use
short names. As a result, in a pure IP environment,
youÕll have to deal with name resolution.
In the IPX world, if you want to attach to a
particular server, you donÕt need to know where
that server is located, its IP address, its domain,
or the NDS context in which the server resides.
You simply refer to the server by its short name.
How to
transition from
IPX to pure IP
4
HELPFUL
D O C U M E N TAT I O N
This is not the case in the world of Pure IP.
2. Partition the SLP Scope Units in the tree and
For example, if you want to get to YahooÕs Web
ensure that the servers designated to run the
Novell DNS/DHCP Services:
site, you canÕt simply type the word ÒyahooÓ into
DA service hold replicas of all Scope Units
Design Issues and
your browser. Instead, you must type the Yahoo
that they service.
Troubleshooting:
Web serverÕs fully qualified DNS name:
http://developer.novell.com/
www.yahoo.com.
research/appnotes/1998/
The opposite is also true, that is, you can
november/a1frame.htm
refer to a single server by any number of names.
For example, in the IP world you can refer to the
DNS resolves short names by taking the name
and concatenating the current DNS sub-domain
onto the end. For example, prv-botanica becomes
prv-botanica.provo.novell.com.
NDS resolves short names by taking the name
Novell GUI Map utility that maps a drive to the
and concatenating the current NDS context.
server on your desk, in a number of ways:
(For example, prv-botanica becomes
USEFUL
D O C U M E N TAT I O N
SLP Deployment Guide:
www.novell.com/
Use the fully qualified DNS name:
\\serverut.provo.novell.com\sys
Use the fully qualified NDS name:
\\novell_inc\.serverut_sys.gta.prv.novell
prv-botanica.gta.prv.novell.)
The Windows NT client requests information
from all of the Name Service Providers at once and
uses the one that responds first.
products/netware/
Use the IP address: \\xxx.xx.xxx.xxx\sys
Step 4. Upgrade To NetWare 5
Using SLP to provide dynamic discovery in a
In this step you will upgrade your servers and clients
deployment_solutions
Pure IP environment can go a long way toward
to NetWare 5, and at the same time implement the
easing the transition from IPX. With SLP, you can
SLP design you developed in Step 3.
refer to the server in the above example in the
HELPFUL
D O C U M E N TAT I O N
An overview of SLP:
http://support.novell.com/
cgi-bin/search/searchtid.cgi?/
10014788.htm
same way that you have been using with IPX,
NetWare 4.11 to NetWare 5.1 UpdateÑto help
that is, with the serverÕs short name:
you upgrade from NetWare 4.11 to NetWare 5.
\\serverut\sys SLP resolves short names by
YouÕll find information on this course at:
looking for an SLP object type of Òbindery.novellÓ
http://novell.netpub.com/cgi-bin/edcatalog/
with that particular name.
ilt_one_sresult?m=689
At this point, you should design your SLP
implementation in preparation for deploying
Dynamically Discovering
Services on an IP Network
with SLP:
http://developer.novell.com/
Novell offers an Education courseÑCourse 529
Upgrade servers to NetWare 5
SLP in the following step (Step 4) as you upgrade
You need to upgrade your servers to NetWare 5
your servers to NetWare 5. To design your SLP
including the currently recommended service pack.
implementation, you need to perform the
following steps:
NOTE: The first server you upgrade should be a
replica of the root partition. The next servers
research/appnotes/1999/
1. Determine the number of Directory Agents
you upgrade should be the servers you will use
march/a2frame.htm
(DAs) to host the scope(s).
as the SLP DAs for the environment. You need
How to
transition from
IPX to pure IP
5
HELPFUL
How Novell implemented SLP
D O C U M E N TAT I O N
Novell implemented SLP on a per site basis. Novell decided on this approach because not rolling out
an enterprise-wide SLP implementation would allow each site to migrate from IPX to IP independently
of the other sites on the network.
SLP Console and Set
Commands:
http://support.novell.com/
At smaller sites (less than 100 clients), Novell did not install a Directory Agent and simply allowed
the individual systems to use multicasting to advertise their presence and look for services. At larger
cgi-bin/search/searchtid.cgi?/
10014868.htm
sites, Novell installed two Directory Agents (for redundancy and load balancing), but that SLP
information was replicated only locally. Using SLP locally allows it to provide dynamic discovery of
local resources (the resources users are most likely to need). Novell then trained users to use fullyqualified DNS names to perform such actions as login and drive mapping.
Novell standardized on fully-qualified DNS names, using DNS as the primary name resolver
(followed by NDS, SLP, and then, if all else fails, local host files). ThatÕs because DNS is the only
SLP, How to use it with
DNS and DHCP:
http://support.novell.com/
cgi-bin/search/searchtid.cgi?/
10014570.htm
naming standard that is independent of the userÕs location and the location of the desired network
resource. Fully-qualified DNS names work everywhere. For example, DNS works regardless of whether
the user is mapping a drive locally, across the Internet from a customer site, via a VPN client, or
dialing in with RADIUS.
TIDs: These documents can
be found by searching at:
http://support.novell.com/
search/kb_index.jsp
to implement SLP on each of these servers
NOTE: When upgrading your servers to
after you upgrade that server to NetWare 5.
NetWare 5, Novell recommends that you run
To do so, perform the following steps:
both IP and IPX during the transition to pure IP,
TID 10025313—
Frequently Asked
Questions about SLP
that is, run a dual stack. That enables your
TID 10014396—
1. Load the SLP DA service.
NetWare servers to communicate with both
2. Configure/tune the various server SLP SET
parameters (Set the NCP PROTOCOL
PREFERENCES = TCP IPX UDP. You must also
put in the AUTOEXEC.NCF because it is not
“SLP Terms and
your IP-based clients and services, and your
Configuration Reference”
IPX-based clients and services during the
TID 10014467—
transition. The dual stack approach helps
ensure a smooth migration from IPX to pure IP.
“Configuring a
LAN/WAN infrastructure
persistent between server reboots).
Upgrade Clients To NetWare 5
3. Configure the SLP.CFG on every NW 5.x server
(define the 2 ÒclosestÓ DAs in the SLP.CFG,
You need to upgrade your clients to NetWare 5.
In addition, although it is not necessary to do so at
REGISTER TYPE commands for regional vs.
the time you upgrade your servers to NetWare 5,
global scoping).
you should perform the client-side configuration
You can then upgrade all remaining servers to
NetWare 5.
for SLP. This may require you to reinstall the
client if is not currently installed with IP support.
for SLP”
TID 10014466—
“Configuring SLP for a
NetWare Client”
TID 10027163—
“Configuring SLP for a
NetWare Server”
How to
transition from
IPX to pure IP
6
HELPFUL
NOTE: When upgrading your NetWare Clients
servers, itÕs easier to allow servers to continue to
to NetWare 5, you may want to ensure that
communicate via IPX until they can all communicate
For information on
they can run both IP and IPX if you need the
via IP. ThatÕs why Novell recommends taking the
Automatic Client Upgrade
two protocols to coexist during the transition
dual stack approach in Step 3.
(ACU), search
to pure IP. That ensures that your NetWare
support.novell.com
Clients can communicate with your IP-based
typically eliminates most IPX dependencies,
for “ACU” or look in the
servers and services, and with your IPX-based
you still need to look at all of the other network
Novell Client documentation.
servers and services during the transition.
services you have to see what IPX dependencies
D O C U M E N TAT I O N
Although upgrading all servers to NetWare 5
they may have.
Step 5. Set Up DNS
Some applications make the transition
Set Up DNS Entries for All NetWare 5
Servers
to a Pure IP environment easier than others.
For example, with Novell GroupWise , all you have
¨
You need to set up DNS entries for all NetWare 5
to do is set the clients to use client/server mode.
servers. This will allow DNS to provide name
Other applications, however, are not that easy.
resolution when dealing with your new IP-based
Although some services may not use IPX on
servers. (Name resolution will be discussed in
HELPFUL
the client side, they may have IPX hooks in their
more detail in Step 7.)
management pieces. Some services may use IPX for
D O C U M E N TAT I O N
How Novell Deployed
Convert Server Names in Login Scripts to
Fully-qualified DNS Names
DNS and DHCP in its
Global Network:
www.novell.com/
products/netware/
deployment_solutions
Once you turn off IPX, referring to servers by their
short name will no longer work. Therefore, it is
important that you convert the server names in
all login scripts to fully-qualified DNS names.
Step 6. Identify IPX Dependencies and
Transition Those Services To IP
dynamic discovery to show a list of available
servers in a dialogue box, or they may be able to
communicate with the server via IP, but they may
rely on SAP (Service Advertising Protocol) to
actually discover the address of the server.
You will also need to check for short name
dependencies. Some applications may not be
capable of referring to servers by their fully-
Your largest source of IPX dependencies
qualified DNS names, and depending on your
will probably be NetWare, NDS and Printing
setup, short name resolution may not work
(queue-based printing is IPX-based) on your
enterprise-wide. Step 6 will help you resolve
NetWare 4.x servers. Depending on your tree
this problem.
design, NDS background processes may require
For help in ferreting out the IPX dependencies
that all the servers in your tree be able to
in your network, you can use the NetWare IPXCON
communicate with all the other servers in the tree.
utility to see what SAPs are out on the wire.
Rather than researching, diagramming and
coordinating which servers must talk to which
Two other useful tools are SAP List and SAP Snoop.
You can find utilities that will help you detect
How to
transition from
IPX to pure IP
7
SAPs at: http://www.netwarefiles.com/ and at
Step 8. Change Timesync Time Sources to
Use IP Addresses
http://www.novellshareware.com/
Timesync doesnÕt currently resolve fully-qualified
Step 7. Convert to Fully-qualified DNS
DNS names. In this case you must specify an
Names
IP address.
Convert Login Scripts to Use Fully-qualified
DNS Names
Step 9. Turn Off IPX SAP at the Routers
In this step, you must convert login scripts to use
This step does not shut down IPX entirely. It turns
fully-qualified DNS names. For example,
off only IPX SAP. You need to continue to route IPX
Change the script line:
RIP until you have upgraded every server in the
map z:=s16:=\\prv-botanica\sys\public
tree to NetWare 5.
to:
NOTE: Before performing Step 9, you should
map z:=s16:=\\prv-botanica.provo.novell.com\
make sure that there are no other services
sys\public
using SAP.
Train Users to Use Fully-qualified DNS Names
Remember, SAP packets and IPX packets are
You must train users to use fully-qualified DNS
not equivalent. SAP is merely the aspect of the
names in performing such operations as login and
protocol that provides service advertisement.
drive mapping.
It is analogous to a telephone directory in that it
HOW NOVELL
TRAINED USERS
You need to give users a
way to determine the fully-
H O W N O V E L L A D D R E S S E D I P X - D E P E N D E N T S E RV I C E S
qualified DNS names of
servers. Novell did this
The table below shows some of the services that Novell had to migrate in moving the Novell network
by creating a simple but
infrastructure to pure IP. The table also shows the solutions on which the company standardized at
effective CGI script that
the time of transition.
allows a user to type in the
Service
Product
Anti-Virus
McAfee NetShield 4.0.x
Backup
BackupExec 8.0 (Build 251)
In response, the script
Caching/Proxy
Novell BorderManager 3.0
returns the fully-qualified
DNA/DHCP
Novell DNS/DHCP 3.0
E-Mail/Messaging
GroupWise 5.5
short name of any server.
¨
FTP
NetWare NFS 2.4
Network Management
ManageWise 2.6, HP OpenView 5.01
NFS
NetWare NFS 2.4
Printing
NDPS
Remote Access (RADIUS)
Novell BorderManager 3.0
Web Server
Netscape Enterprise/Fastrack Server for NetWare
DNS name for that server.
How to
transition from
IPX to pure IP
8
simply maps server names into server addresses.
Step 12. Turn Off IPX At The Servers
IPX RIP, on the other hand, is used to transfer
Finally, turn off IPX on every server.
information from point A to point B.
To ensure the network remains operational,
NOTE: Do not perform this step until you have
upgraded every server in the tree to NetWare 5.
turn off SAP using the following procedure:
Congratulations, you have just made the
¥ Turn off SAP at the routers.
transition to pure IP.
¥ Wait for 5-10 minutes.
¥ At the server console, enter RESET ROUTER
a few times.
M A I N TA I N I N G I P X S E R V I C E S
T E M P O R A R I LY I N A P U R E I P
ENVIRONMENT
¥ Wait a few more minutes.
In some cases, you will have to maintain IPX
¥ At the server console, enter DISPLAY SERVERS.
You should see only a list of IPX servers from
the local site.
¥ At the server console, enter DISPLAY
NETWORKS. You should see the full list of
services temporarily in your new pure IP
environment. That could be due to a variety of
reasons. For example, you may not be able to
migrate all your servers to NetWare 5 in the time
allotted for transition to pure IP, yet you still need
IPX networks on both sides of the router,
to be able to access those resources from areas
not just the IPX networks from the local site.
that are pure IP. In these cases, you must allow
This step provides a good test for IPX
dependencies. Once youÕve turned off SAP at
the routers, you may find that some applications
that you assumed didnÕt have IPX dependencies
actually do have IPX dependencies.
your IPX-dependent services to continue to
function in a world where IPX no longer exists,
until you can move them to IP.
NetWare 5 provides a solutionÑthe NetWare 5
Migration AgentÑa NetWare 5 server running
Compatibility Mode Drivers (CMD) with the Migration
Step 10. Check NDS Synchronization
Agent option enabled. The Migration Agent lives
Go into DSRepair and force a synchronization to
in the IPX world and acts as the intermediary
make sure that NDS is synchronizing properly
between the IP and IPX worlds. It allows IP-only
without SAP.
clients and servers to communicate with their
IPX-based counterparts, and vice-versa.
Step 11. Verify Client Logins
To take advantage of the NetWare 5 Migration
At this point, you should make sure that users
Agent, you must be running IPX Compatibility
can still login to the network. Make sure that
Mode Drivers (IP/CMD) on all clients and servers
both container and personal login scripts are
that reside in the IP-only world. If applications
working properly.
on these IP-only devices make an IPX call or
How to
transition from
IPX to pure IP
9
communicate with IPX devices, the CMD drivers
The Migration Agent also translates between
USEFUL
intercept the IPX call, encapsulate it in an IP
IPX SAPs and SLP. It takes IPX SAPs and registers
D O C U M E N TAT I O N
packet and route it to the Migration Agent.
these advertised services with the Directory
Configuration Parameters
The Migration Agent accepts that request and
Agents so that they are available via SLP to
for the Compatibility
makes the IPX call on behalf of the IP-only
IP-only devices. The Migration Agent also takes
Mode Driver:
device, receives an IPX response and then
the SLP information from the IP-only devices
http://developer.novell.com/
delivers that response back to the original
and broadcasts SAPs on their behalf so they are
research/appnotes/1999/
requester via IP.
visible to the IPX services.
april/a4frame.htm
A D D I T I O N A L I N F O R M AT I O N
SCMD: Frequently
For additional information on day-to-day management of Novell NetWare, product features, Q&A, etc.
Asked Questions:
please see the following links:
http://support.novell.com/
Product Information:
http://www.novell.com/products/netware/producinfo.html
cgi-bin/search/searchtid.cgi?/
NetWare Documentation:
http://www.novell.com/documentation/lg/nw51/docui/index.html
10014705.htm
Novell Cool Solutions:
http://www.novell.com/coolsolutions/netware/
Developer Notes:
http://developer.novell.com
App Notes:
http://developer.novell.com/research/index.htm
Customer Support Knowledge Base:
http://support.novell.com/search/kb_index.jsp
Novell Developer Kit (NDK):
http://developer.novell.com/ndk/doc.htm
Novell Solution Search:
http://developer.novell.com/nss/
Novell Consulting Services:
http://www.novell.com/consulting/
Novell Consulting Business Solutions Offerings (BSOs):
http://www.novell.com/consulting/bso/
Novell Education
http://www.novell.com/education
Novell Partner Network:
http://www.novell.com/partners/locator.html
NetWare Case Studies:
http://www.novell.com/success/by_product.html
N O V E L L
Novell Corporate Headquarters
1800 South Novell Place
Provo, Utah 84606
USA
Tel: (801) 861 7000
Toll-free: (800) 453 1267
O F F I C E S
Novell de Panam‡
Calle 53 Marbella,
World Trade Center
Piso 2, Oficina 10
Ciudad de Panama
Panama
Tel: (507) 206-8714
Fax: (507) 206-8777
Novell Hungary
East-West Business Center
R‡k—czi œt 1-3
1088 Budapest
Hungary
Tel: (36) 1 235 7656
Fax: (36) 1 266 6360
Novell del Perœ
Pasaje Martir Olaya 129,
Of. 1701, Miraflores
Lima 18
Peru
Tel: (511) 214 1340
Fax: (511) 214 1087
Novell Israel
Ackerstein Building
Medinat Hayehudim St 103
Herzliya 46776
Israel
Tel: (972) 99 51 44 55
Fax: (972) 99 51 44 66
EUROPE, MIDDLE EAST,
AFRICA REGION
Novell Italia
Piazza Don Mapelli 75
20099 Sesto San Giovanni
Milano
Italy
Tel: (39) 02 26295.1
Fax: (39) 02 26295 800
AMERICAS REGION
Novell Canada
3100 Steeles Avenue East
Suite 500
Markham, Ontario L3R 8T3
Canada
Tel: (905) 940 2670
Fax: (905) 940 2688
Novell de Argentina S.A.
Ing. Butty 240, piso 6
Edificio Laminar
(1001) Capital Federal
Argentina
Tel: (54) 11 4 510 2626
Fax: (54) 11 4 510 2656
Novell do Brasil
Software Limitada
Avenida das Na•›es
Unidas, 12.995
8¼ Andar
04578-000 S‹o Paulo - SP
Brasil
Tel: (55) 11 5505 4040
Fax: (55) 11 5505 4041
Novell Chile
Edificio Nuevo Centro
Providencia
Av. 11 de Septiembre 1881,
Of. 615
Providencia, Santiago
Chile
Tel: (56) 2 3769211
Fax: (56) 2 3769776
Novell de Colombia
Teleport Business Park
Calle 114 No. 9 - 45
Torre B - Of. 709
SantafŽ de Bogot‡
Colombia
Tel: (57) 1 629-2969
Fax: (57) 1 629-3509
Novell de MŽxico
Blvd. Manuel Avila
Camacho #138-1
Col. Lomas de Chapultepec
Mexico D.F., C.P. 11000
Tel: (52) 5 284 2700
Fax: (52) 5 284 2799
Novell Central America
One East Broward Blvd.
Suite 700
Ft. Lauderdale, FL 33301
USA
Tel: (954) 713 2869
Fax: (954) 356 0409
Novell Austria
HeiligenstŠdter LŠnde 27c
1190 Vienna
Austria
Tel: (+43) 1 367 74 44
Fax: (+43) 1 367 74 44 20
Novell Belgium NV
Koningin Astridplein 5,
(3rd floor)
2018 Antwerpen
Belgium
Tel: (32) 3 206 1793
Fax: (32) 3 206 1799
Novell Praha s.r.o.
Praha City Center
Klimentska 46
110 02 Praha 1,
Czech Republic
Tel: (420) 2 2185 66 11
Fax: (420) 2 2185 66 22
Novell Danmark a/s
Slotsmarken 12
DK 2970 H¿rsholm
Danmark
Tel: (+45) 45 16 00 20
Fax: (+45) 45 16 00 40
Novell Finland
Lars Sonckin karri 14
02600 Espoo
Finland
Tel: (358) 9 502 951
Fax: (358) 9 502 95 300
Novell France
Tour Framatome
1, place de la Coupole
92084 Paris La DŽfense cedex
France
Tel: (33) 1 47 96 60 05
Fax: (33) 1 47 78 94 72
Novell Germany
Monschauer Strasse 12
40549 DŸsseldorf
Germany
Tel: (49) 211 5631 0
Fax: (49) 211 5631 250
Novell Nederland
Barbizonlaan 25
2908 MB Capelle a/d Ussel
PO Box 85024
3009 MA Rotterdam
The Netherlands
Tel: (31) 10 286 44 44
Fax: (31) 10 286 40 10
Novell Norge AS
¯stensj¿veien 34
P.O. Box 6555 Etterstad
0606 Oslo
Norway
Tel: +47 23 37 77 70
Fax: +47 23 37 77 71
Novell Polska
ul. Wsp—lna 47/49
00-684 Warszawa
Poland
Tel: (48) 22 537 5000
Fax: (48) 22 537 5099
Novell Portugal
Centro Empresarial Torres
de Lisboa
Rua Tom‡s da Fonseca,
Torre G
1600-209 Lisboa
Portugal
Tel: (351) 21 723 06 30
Fax: (351) 21 722 35 33
Novell Russia and CIS
Suite 524, Business Center
Radisson-Slavyanskaya Hotel
2, Berezhkovskaya
Naberezhnaya
121059 Moscow, Russia
Tel: +7 095 941 8075/8073
Fax: +7 095 941 8066
W O R L D W I D E
Novell South Africa
Morning View Office Park
214 Rivonia road, morningside
P.O. Box 1840
Rivonia 2128 Johnannesburg
Republic of South Africa
Tel: (27) 11 322 8300
Fax: (27) 11 322 8400
Novell Hong Kong
Room 4601-5
China Resources Building
26 Harbour Road
Wanchai
Hong Kong, China
Tel: (852) 2 588 5288
Fax: (852) 2 827 6555
© Copyright 2001, Novell, Inc. All rights
reserved. Novell is a registered trademark
of Novell, Inc. in the United States and
other countries.
Novell Spain, S.A. (Madrid)
Paseo de la Castellana, 95
Planta 27
Edificio Torre
Europa
28046 Madrid
Spain
Tel: (34) 91 555 65 67
Fax: (34) 91 555 29 15
Onward Novell
Software (l) Ltd.
62 MIDC, 13th Street
Andheri (East)
Mumbai 400 093
India
Tel: +91 (022) 8342244
Fax: +91 (022) 8342223
For more information about
Novell’s worldwide product
training, certification programs,
consulting and technical support
services, please visit:
www.novell.com/services
Novell Sweden
KronborgsgrŠnd 1
164 87 Kista
Sweden
Tel: +46 (8) 477 41 00
Toll-free: +46 (20) 35 30 30
Fax: +46 (8) 477 41 01
Novell (Schweiz) AG
Leutschenbachstrasse 41
8050 ZŸrich
Switzerland
Tel: (41) 1 308 47 47
Fax: (41) 1 302 04 01
Novell United Kingdom Ltd.
Novell House
1 Arlington Square
Downshire Way Bracknell
Berkshire RG12 1WA
United Kingdom
Tel: +44 (0)1344 724000
Fax: +44 (0)1344 724001
ASIA PACIFIC REGION
Novell Pty Ltd
Level 18, 201 Miller Street
North Sydney NSW 2060
Australia
Tel: +61 2 9925 3000
Fax: +61 2 9922 2113
Novell New Zealand Limited
L12, 44 - 52 Wellesley Street
Auckland 1
New Zealand
Tel: +64 9 308 1400
Fax: +64 9 308 1409
Novell China
Floor 11 Canway Building
No. 66 Nan Li Shi Road
Beijing 100045, China
Tel: (86) 10 68028855
Fax: (86) 10 68028720
Novell Japan Ltd.
Toei Mishuku Bldg.
1-13-1 Mishuku
Setagaya-Ku
Tokyo 154-8561
Japan
Tel: (81) 3 5481 1294
Fax: (81) 3 5481 1934
Novell Corporation (Malaysia)
Sdn Bhd
Unit 501, Level 5, Uptown 1
1 Jalan SS21/58
Damansara Uptown
47400 Petaling jaya
Selangor Darul Ehsan
Malaysia
Tel: (60) 3 7722 6100
Fax: (60) 3 7722 6155
Novell Philippines, Inc.
28th Floor, Tower 2,
The Enterprise Center
6766 Ayala Avenue,
Paseo de Roxas
1226 Makati City, Philippines
Tel: (632) 849 3878
Fax: (632) 849 3861
Novell Singapore Pte Ltd
8 Temasek Boulevard
#32-01/02 Suntec Tower Three
Singapore 038988
Tel: (65) 395 6888
Fax: (65) 395 6777
Novell Software
(Thailand) Ltd.
16th Flr., TISCO Tower
48 North Sathorn Rd.
Silom, Bangrak,
Bangkok 10500
Thailand
Tel: (662) 638 0310
Fax: (662) 638 031
Last updated May 14, 2001
462-001162-001
Novell Product Training
and Support Services
For More Information
Contact your local
Novell Authorized Reseller,
or visit the Novell Web site at:
www.novell.com
You may also call Novell at:
1 888 321 4272 US/Canada
1 801 861 4272 Worldwide
1 801 861 8473 Facsimile
Novell, Inc.
1800 South Novell Place
Provo, Utah 84606 USA
www.novell.com