IPX to IP

To use TCP\IP instead of IPX you must bind IP to your network card in the server instead of, or in addition to, IPX.  Type Config at the console prompt and find the name of your Network card.  Bind IP to your card.  You must have a valid IP address for the server.  It will ask for one if you do not include it in the bind statement.  On your Windows machines you must add TCP\IP as a protocol in the Network properties.  You must give the machine an IP address.  If you are connected to the internet you cannot use just any address.  You must use one of the addresses assigned to you.  

So far, so good!  Using INETCFG.NLM, what should the settings bee for Packet Forwarding, RIP, OSPF, Static Routing, and the other options?  I have the NIC bound to IPX, AppleTalk, and TCP/IP with valid IP address.  All workstations/servers have valid IP addresses too.  Using Novell Client 32 for the workstations to log in, should some other client be used?

The Novell client is the one to use.  Are you trying to use IP instead of IPX to connect to the server?  Are you trying to use any other services (Web Server, FTP, IPX/IP gateway)?  If you are replacing IPX with IP, you need to remove IPX and on Win95 machines change the frame type.

OK.  I have the Novell client set to use all detected frame types.  Is it possible to use BOTH IPX and IP?  I can't experiment with this much during the day since there are about 120 users on line now.

I'll try restricting just one PC to IP only and see what happens.

Why would you want to use both?  You are just increasing the traffic on the network.  This will ultimately slow the network down.  Do you need both for any particular reason?

Need to have both only for a testing period, then go completely over to TCP/IP when it works right.

Do not forget to install NWIP if you have any NCP clients.

OK!  I have done all of the above but when I take IPX out of the Windows 95 client (NWCLIENT32), the whole client disappears and NO login is available!

What am I missing here?

Hmm, are you using the latest Client32 from Novell. Thay have added a lot of NWIP stuff to the latest version. Make sure you use that one.

Yes.  Just got the latest client from Novell.  Still, when I remove IPX, the entire client goes away!

Now what?

THANKS!

TCPIP vs NWIP w/ Client32  (Last modified: 16SEP1996)

     This document (2913430) is provided subject to the disclaimer at the end of this document.
         Forward this document to a colleague
         Submit comment about this document to its author

     Issue

     The Client 32 for Windows 95 & Client 32 for DOS/Windows 3.x ships with NetWare/IP stack as
     well as using either a third part TCP/IP stack or a TCPIP.NLM (DOS only) which ships with the
     client. There are distinct differences between NWIP and TCPIP. They are listed as follows:

     1) TCP/IP is a stand alone protocol stack which can be used with IPX/SPX.
     2) NetWare/IP requires TCPIP to be installed.
     3) NetWare/IP allows the client to talk only IP over the wire to NetWare servers thus replacing
     IPX. This is provided by adding an IP header to the IPX packet.
     4) If you install NetWare/IP on the client it can only communicate to NetWare servers which
     have NetWare/IP loaded.
     5) Once NWIP is installed your client can no longer talk IPX on the wire.

                    Please select if this document solved your problem.

      Document Title:
                          TCPIP vs NWIP w/ Client32
      Document ID:
                          2913430
      Creation Date:
                          16SEP96
      Modified Date:
                          16SEP96
      Document Revision:
                          2
      Novell Product Class:
                          NetWare OS
      Novell Product and Version:
                          NetWare Client32 for WIN95 2.1
                          NetWare Client32 for DOS/Windows 2.1


     DISCLAIMER

     The Origin of this information may be internal or external to Novell. Novell makes every effort within its means 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.