🚀 go-pugleaf

----------------------------Original message----------------------------
> ----------------------------Original message----------------------------
> I'm hoping that some of you who use Novell 3.12 might be able to help me
> with this:
>
> I've got a Novell 3.12 LAN in my computer lab. Recently, some electronic
> classrooms were setup on campus, each with a Macintosh and a Dell Windows
> for Workgroups (3.11) machine. These have been connected to our campus
> ethernet backbone, setup for tcp/ip, and connected to the Internet. Now
> faculty want those computers to have access to my Novell LAN.
>
> My problem is exactly how to do this. I have been able to connect to the
> campus ethernet by putting an additional NIC in my server. I configured
> that for tcp/ip using the tcp/ip nlm that comes with NetWare. Now, does
> anyone know how I can get my computers to recognize the NetWare Network
> using tcp/ip. It doesn't work now, so I'm sure that there must be
> something else I need to do, but I don't know what it is.
>
> I would appreciate any help with this. Thanks.

Barbara,

There are quite a few options depending on your setup.

If you can run IPX on the backbone, you can do this fairly easily.  Just load
IPX on the PCs and bind IPX to the backbone NIC in your server.  You can use
NETX and the IPX and real mode NDIS drivers that comes with WFW or use VLMs.
If you use VLMs, you will need to use ODI based drivers and load ODIHLP to
provide an NDIS layer on top of these for WFW's TCP/IP stack.  This should
all be covered in the WFW Resource Kit from Microsoft.

If the backbone does not let IPX through and you need TCP/IP for WFW's file
and print services then you are stuck.  The only reasonable way to run
NetWare over TCP/IP is to use NetWare/IP.  To do this you need NetWare/IP on
the server and Novell's TCP/IP stack (included) on the client. Unfortunately
this stack doesn't support WFW's file and print services.  If you need
Windows and NetWare file and print services then you need to upgrade the
backbone to IPX; run a local NetWare/IP server (single user runtime is OK)
for the WFW machines to act as an IP/IPX gateway; or wait and upgrade the
WFW PCs to Windows 95 and Novell's Client32 NetWare client which will allow
Windows and NetWare to share the one TCP/IP stack.

In our case, we use the first option with VLMs and run IPX (routed) on the
backbone.

regards,

Chris

Chris Owen                           |  E-mail: c.owen@qut.edu.au
Systems Manager                      |
Computer Based Education Department  |
Queensland University of Technology  |  phone:  +61 7 3864 2912
GPO Box 2434                         |  FAX:    +61 7 3864 1525
Brisbane 4001, Australia             |