lan netware 3.1
jason2329
like alot of people i have never installed a nic crad i guess the power
went out on me this weekend, and now it is not able to find the e100b
driver it says. right now it is at scanning tts backout file i know
this takes a long time but when it is done i do not know what to do
about getting the card back on the network. when it comes back up i
will post my startup and utoexec and the exact error message. wish me
luck and cant wait for someone to give me some suggestions. thanks alot
in advace.
Jasonj
* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Felton Green
I'd run the config utility and post the config.txt message here WITHOUT the
serial number so we can check you setup, but most likely you'll not need to
do much if you replace the NIC with the same type of NIC.
Here is a blurb on NIC loading:
Load LAN Drivers
Once the SYSTEM and PUBLIC files are copied, continue the installation
process by loading LAN drivers.
Select LAN drivers for the cabling system and the network boards you use.
Frame Types for Ethernet Networks
The default Ethernet frame type for NetWare v3.12 is 802.2.
If you have a mixed environment where you have NetWare v3.11 or earlier that
use the 802.3 frame type, you may need to specify both 802.2 and 802.3 frame
types.
To do this, you load the LAN driver twice and specify a different frame type
each time the LAN driver is loaded.
A workstation running the 802.3 frame type can't communicate with the
NetWare v3.12 server (which defaults to 802.2) until both frame types are
loaded.
IMPORTANT: Some routers may not support the Ethernet 802.2 frame type. Check
your router's documentation and load the frame type the router supports.
IMPORTANT: Loading both 802.2 and 802.3 frame types can affect network speed
and performance. Standardize your network on 802.2 if possible.
Procedure
1.Load the drivers with the default frame type.
LOAD LAN_driver <Enter>
Third-party drivers are also included with NetWare v3.12, including drivers
from 3COM®, Cabletron, Datacom, Hewlett Packard®, IBM, Intel®, Madge,
Proteon®, Racal, Standard Microsystems, Thomas-Conrad, and Ungermann-Bass®.
The LAN drivers are copied to SYS:SYTEM and can be loaded from there.
1a.(Conditional) If you are loading a Novell-supplied LAN driver, replace
LAN_driver with the driver listed in Table 2-4 for your cabling system and
network board.
1b.(Conditional) If you are loading a third-party LAN driver, load the
driver from SYS:SYSTEM or from the diskette that came with the network
board.
For example, if you have an Ethernet cabling system and an NE2000 network
board, type
LOAD NE2000 <Enter>
2.Answer the prompts for addresses and interrupts according to the
information you entered on the File Server Worksheet.
3.(Conditional) Load the drivers with another frame type. Type
LOAD LAN_driver FRAME=frame_type <Enter>
Replace frame_type with the frame type for your cabling system and network
board.
For example, if you have an Ethernet cabling system and an NE2000 network
board, type
LOAD NE2000 FRAME=ETHERNET_802.3 <Enter>
If the LAN driver has been loaded previously, a message similar to the
following appears:
Do you want to add another frame type for a previously loaded board? n
4.Type "Y" to continue.
5.Select the correct frame type from the confirmation list.
The following message appears:
Previously loaded module was used re-entrantly
For more information, see " Load LAN Driver" in System Administration.
Bind the Protocol to the LAN Driver
The final installation step is to bind the protocol to the LAN driver.
NetWare v3.12 allows protocols other than IPX to function on the network.
The steps below use IPX as an example protocol to bind each LAN driver in
the file server.
Procedure
1.Bind IPX to the LAN driver.
1a.To bind IPX to each LAN driver, type
BIND IPX TO LAN_driver
If you use multiple frame types on the same network board, NetWare v3.12
lists the frame types that are loaded and asks you to select the board you
want to bind IPX to.
You can bind IPX to all those frame types, as long as you give a different
network address to each frame type.
For more on network numbers, see "Network numbering" in Concepts.
1b.If you have loaded the same LAN driver several times (for several network
boards of the same type), select the board to be bound to the protocol.
1c.To bind a protocol to a driver that is loaded with two or more frame
types for the same network board, see " BIND" in System Administration.
2.Assign the network address.
Each LAN driver must be assigned the network address that identifies the
cabling system it uses to communicate with similar LAN drivers on the
network.
NOTE: This network address is not the same as the internal IPX network
number you assigned to the file server in Step 2.
At the prompt, type the number that enables the LAN driver and network board
in the file server to communicate with the network. The address must be
A hexadecimal number (base 16: using numbers 0 through 9 and letters A
through F).
One to eight digits.
NOTE: If you use multiple frame types with your LAN drivers, assign a
network address for each frame type.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
The worlds best convention on networking
Brainshare is coming!
March 18 - 23, 2001
http://www.novellbrainshare.com/
jason2329
it is doing the scanning tts backout file it usually takes a couple of
hours when it comes up i will do what you said thank you and hope to
talk to you more when it comes back up
Jason
Felton Green
Ok. We'll be here. 8- )
Felton Green
Is it still hung up?
jason2329
i just reboot again and go through it again. thanks for the help
jason2329
before(he is out with the flu) he hired me as the net admin but i am
not good with novell 3 i am a CNE5 but i still feel dumb that i do not
know what to do. He said to leave it it will come up in a couple of
hours(that is why novell does not support 3) but i will let you know
and i really appreciate all your help. Thnaks
Felton Green
Ok. We'll be waiting here.
Do you have the system duplexed or mirrored?
jason2329
concept) what really is not good i this is the main server i have three
netware 5 machines one netware 5.1 and this is the one they use the
most oh well i am getting them off of it but i just started here so we
will see. Have you ever heard of that taking a couple of hours to come
up. oh well,I will let you know what happens (so you can help) well
thanks alot for the responses and wish me luck
Felton Green
Ok. We'll be here. 8- )
jason2329
lan driver not loaded i type in config on the server it says the server
and the network number what do i need to do?
Felton Green
get the latest drivers from the mfr. and use those. Have you installed the
odi33g.exe update?
here is an example:
load e100b slot=1 port=dce0 mem=f7000000 FRAME=ethernet_802.3 name=802.3
bind ipx to 802.3 net=08500003
load e100b slot=1 port=dce0 mem=f7000000 frame=ethernet_II name=ether_II
bind ipx to ether_II net=08500004
jason2329
you asked about and what exactly do i need to do with the load file i
have such a headache i have two servesrs down one in another building
and this one thank you so much i hope you can help me figure it out
jason
Felton Green
At the console prompt you can test the loading of the NIC? I would print out
the sys:system\autoexec.ncf file so you can have something to go on. If you
have identical NIC's then it's a piece of cake.
What's wrong with the other server? ( start a new thread if you need help
with it )
jason2329
here is my autoexec.ncf file
File server name server
Ipx internal net c5002000
load e100b port=fce0 mem=fedfd000 int=b slot=16 frame ethernet_8 bind
ipx to e100b net =c5002001
load e100b port=fced mem=fedfd000 int=b slot=16 frame= ethernet_s load
e100b port=fce0 mem =fedfd000 int=b slot=16 frame=ethernet_I
mount all
what should i do do i have to replace the nic if so do the same load
files? what do i do thanks in advance]
Jaspn
Felton Green
8022
bind ipx to 8022 net =c5002001
load e100b port=fced mem=fedfd000 int=b slot=16 frame= ethernet_II name=II
bind ipx to II net=c5002002
You can load multiple frame types with the same files or use multiple NIC's
that are loading the same files.
Felton Green
using two NIC's?
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
The worlds best convention on networking
Brainshare is coming!
March 18 - 23, 2001
http://www.novellbrainshare.com/
"Felton Green" <felton...@bigfoot.com> wrote in message
news:8vur31$i2...@nexus.provo.novell.com...
jason2329
Jason
Felton Green
Then you're trying to load a different frame type on the same board.
load e100b port=fce0 mem=fedfd000 int=b slot=16 frame ethernet_802.2 name=
8022
bind ipx to 8022 net =c5002001
load e100b port=fced mem=fedfd000 int=b slot=16 frame= ethernet_II name=II
bind ipx to II net=c5002002
You need to check that port=fce0 or port=fced is the correct port. I'm
putting a letter in front of each line to speed things up:
A:) load e100b port=fce0 mem=fedfd000 int=b slot=16 frame ethernet_802.2
name=
8022
B:) bind ipx to 8022 net =c5002001
C:) load e100b port=fced mem=fedfd000 int=b slot=16 frame= ethernet_II
name=II
D:) bind ipx to II net=c5002002
If you have no LAN drivers loaded, then type line A: at the console prompt.
You should get a response. If it comes up loaded then no problem. Just
change line C:) to reflect the new port
I'll be standing by to see the results.
jason2329
those things at the console prompt right. I have to stay tonight untill
i get it working i am so lost. hope to here from you
Felton Green
I said I'd be here. 8- )
I may have to go home, but I have cable modem and I'll monitor the problem.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
The worlds best convention on networking
Brainshare is coming!
March 18 - 23, 2001
http://www.novellbrainshare.com/
"jason2329" <jason232...@hotmail.com.invalid> wrote in message
news:0af1953c...@usw-ex0107-050.remarq.com...
Felton Green
I'm headed for home right now. I'll be back online in about 25 minutes (
depends on traffic ) <sigh>
jason2329
to pay you back one way or another i promise. anyway when it comes up
will try and load the files and bind like you said hopefully it works i
will keep you posted.
Felton Green
Still here. 8- )
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming
Brainshare is COMING!
18 - 23 March 2001
http://www.novellbrainshare.com
"jason2329" <jason232...@hotmail.com.invalid> wrote in message
news:096a2c7b...@usw-ex0107-050.remarq.com...
jason2329
comming up i will keep you posted thansk alot man
Felton Green
You don't need to reboot each time. When you have confirmed that the NIC's
will load just edit the autoexec.ncf file with load install and run the
autoexec.ncf when it's done.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming
Brainshare is COMING!
18 - 23 March 2001
http://www.novellbrainshare.com
"jason2329" <jason232...@hotmail.com.invalid> wrote in message
news:00ae6d88...@usw-ex0107-050.remarq.com...
Felton Green
I waited until 12 MST then I went to bed. Any word?
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
The worlds best convention on networking
Brainshare is coming!
March 18 - 23, 2001
http://www.novellbrainshare.com/
"jason2329" <jason232...@hotmail.com.invalid> wrote in message
jason2329
still did not get it up here is my complete autoexec.ncf file
File server name STI_DOCS
IPX internal net c5002000
load E100B port=FCE0 mem=FEDFD000 int=b slot=16 frame=ethernet_802.3
name=ipx-net1
bind ipx to E100B net=c5002001
load E100B port=FCE0 mem=FEDFD000 int=B slot=16 frame=ethernet_snap
name=ETLK-net1
load E100B port=FCE0 mem=FEDFD000 int=B slot=16 frame=ethernet_II
name=ip-net1
mount all
that is the file also when the server comes up or i run autoexec.ncf it
says
unable to find load file E100B
lan driver E100B is not loaded
unable to find load file E100B
unable to find load file E100b
so i am lost what do i do i am going to try what you had said earlier
to change the autoexec.ncf file but what do you think hope to here from
you i am so tired
jason2329
Felton Green
File server name STI_DOCS
IPX internal net c5002000
search add c:\server.312
mount sys
load E100B port=FCE0 mem=FEDFD000 int=b slot=16 frame=ethernet_802.3
name=ipx-net1
bind ipx to E100B net=c5002001
load E100B port=FCE0 mem=FEDFD000 int=B slot=16 frame=ethernet_snap
name=ETLK-net1
bind ipx to E100B net=c5002002
load E100B port=FCE0 mem=FEDFD000 int=B slot=16 frame=ethernet_II
name=ip-net1
bind ipx to E100B net=c5002003
mount all
What kind of ethernet card do you have? I would go to the mfr. site and get
the latest lan drivers and put time in the c:\server.312 directory so you
can get on line. Then copy the lan drivers to the sys:system directory.
I would venture a guess that you're behind on your patches too.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming
Brainshare is COMING!
18 - 23 March 2001
http://www.novellbrainshare.com
"jason2329" <jason232...@hotmail.com.invalid> wrote in message
news:01f3fc2c...@usw-ex0107-050.remarq.com...
Dave Lunn
Felton went out to break his hands. Lets see what we can do.
What is your situation right now?
Dave
jason2329
able to load e100b just like in my post any ideas?
jason
Dave Lunn
Dave
jason2329 <jason232...@hotmail.com.invalid> wrote in message
news:1f4c3c26...@usw-ex0107-050.remarq.com...
jason2329
autoexec.ncf ans see what happens wish me luck. Thnaks again i know i
keep saying that but you are great help
Jason
Dave Lunn
OK.
Your post at 3:05 to Felton describes this as an onboard NIC.
The Intel e100b driver goes with the Pro-100 cards which are PCI cards, not
on board devices. Do we need to backtrack here and make sure of what
hardware is present?
Your posting to me just now says that the NIC was present in the server
before the crash and working. If it was present then either/both the
server.312 director on the DOS side and the sys:\system directory should
have the driver present.
When you get to a DOS prompt please look for the driver files tou should
have two ce100b files, a .lan. and a .ldi
If you have the driver files in the c:\server.312 directory we need to know
that.
Dave
jason2329 <jason232...@hotmail.com.invalid> wrote in message
news:1096dc40...@usw-ex0107-050.remarq.com...
> yes it was i tried changing the autoexec.ncf like felton said the only
> thing that changed was it asked for the internal net number witch is
> c5002000 i put that in and it did th whole unable to find load file etc.
> please help you guys are ausome hope to here from you soon
jason2329
if those files are present thanks again
jason2329
what do i do to get them there?
jason
Dave Lunn
be certain that whatever it is you have for an onboard NIC really uses an
Intel e100 driver do you have the docs for the MB?
Dave
jason2329 <jason232...@hotmail.com.invalid> wrote in message
news:01d60bce...@usw-ex0107-050.remarq.com...
jason2329
the autoexec.ncf to c:intell and see if tha works wish me luck
Jason
jason2329
gone i am trying a couple of things i will see what i come up with
Dave Lunn
I would suggest at this time that if you cannot find docs telling you what
is in the box you are going to have to find out somehow.
This may be a much more difficult problem than you would think. Just
dealing with identifying a PCI NIC can be tough, Many have no ID on them at
all, Some have no FCC numbers that are readable.
Dave
jason2329 <jason232...@hotmail.com.invalid> wrote in message
news:0178491c...@usw-ex0107-050.remarq.com...
jason2329
guys have done . if you need something like testing software etc.
e-mail me jaso...@hotmail.com i owe you
Felton Green
Now you need to run the config utility and post the results here WITHOUT the
serial number so we can tweak your box. I'll bet it's way behind on updates
and such.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!