From: "Steve Norton" 
Subject: HELP ME PLEASE! Novell, token ring and AS400 PC Support
Date: 1998/07/25
Message-ID: #1/1
Organization: @Home Network Canada
NNTP-Posting-Date: Sat, 25 Jul 1998 14:16:01 PDT
Newsgroups: comp.dcom.lan.novell,comp.dcom.lans.token-ring,comp.networks,comp.sys.ibm.pc.hardware.networking,fido.novell,il.novell

Hi!

I'm definately not a computer novice, but my Novell experience is just
awful - as is my token ring experience. Any help that can be provided will
be greatly appreciated.

The systems I'm working on are running DOS with Novel 3.12 using IBM token
ring cards (IBM Auto 16/4 or IBM Turbo 16/4) on RJ-45 cabling. The users
long on in DOS. When logging on, some custom files are loaded which starts
"PC Support" to connect to an AS400 system. Windows for Workgroups 3.11
starts so they can use cc:Mail, MS Office and Rumba. Rumba is configured to
connect to the AS400 using the PC Support that was started in DOS.

Now, the problem is this... at boot, the system tries to link into the token
ring. On a working system, the drive comes back stating that it's
connected - 2 SAPs, etc... But on a few systems this does not happen.

When it doesn't happen, the PC Support does not start - reporting too few
SAPs. I can configure the driver to create the SAPs, but I don't think this
is accomplishing what I need. The users can still log onto the Novell
network but Rumba does not work.

There are a number of PCs that are working properly, but I do not know
enough about this environment to move the files from these PC's to the
broken ones - which files are NIC specific? Where can I find the
identification info that is unique to each PC?

Can anyone tell me what I might be doing wrong? Why isn't the token ring
card starting properly? Why can the users use the Novell network, but not
the PC Support?

I have downloaded the drivers disks for the network card from IBM. What
other drivers will I need?

Please help!
Steve

P.s. I have tried installing TCP/IP 3.11b for WFWG, but couldn't ping
anything except 127.0.0.1 and my own IP address. I don't think the network
card is being started correctly during boot.