NW 5.0 server hang, possible flood?
  Home FAQ Contact Sign in
novell.support.netware.5x.abends-hangs only
 
Advanced search
POPULAR GROUPS

more...

novell.support ... 5x.abends-hangs Profile…
 Up
NW 5.0 server hang, possible flood?         


Author: jtrogdon
Date: Dec 1, 2006 07:03

I have a Netware 5.0 with all the last known service packs. I has two NICs,
one for the main network and one for its CaminoSoft Standby Server. The
server has been hanging with about 26-30 utilization and dropping from the
network. The NIC connecting to the CaminoSoft Standby is still
communicating with the server. I can see the packet receive buffers keep
increasing. I have the maximum set at 10000 but I usually restart the
server before it gets too high, which is the only way to resolve this
hanging problem.

My suspicions are that my server is being flooded. The main network
protocol is still using IPX but I do have TCP/IP bind to the NIC so I can
run Backup Exec 9.0 which for some reason requires this. When the server
hangs there are no abends and no error messages. I looked at the LAN/WAN
adapters in Monitor and did notice this: Receive discarded, noavailable
buffers 105 (and increasing).
Show full article (64.34Kb)
1 Comment
Re: NW 5.0 server hang, possible flood?         


Author: Andrew C Taubman
Date: Dec 3, 2006 14:37

SYS is a bit low on free blocks, I'd purge it. May as well purge DATA also.

I'm not sure what's going on with your lan setup. In autoexec you run a
file C:LoadLan.ncf and then load and bind to a ce100b card; except the
only lan driver you have loaded in ce1000. Maybe you can clarify what
happens here.

Whatever is happening there, make sure the lan driver(s) is set to
autonegotiate for both speed and duplex (not hard set to 100FD or
anything else), and the switch/router port it's plugged into is set the
same.

Next time you get the high util, look in

Monitor - kernel - threads, and
NRM (portal) - profile/debug - Profile CPU execution by NLM

to see what is causing the high util.

Next time it hangs, try to get into the debugger with
shift-shift-alt-esc - this often works even if no other keys do. If
nothing happens you almost certainly have a hardware fault.
Show full article (1.42Kb)
no comments

RELATED THREADS
SubjectArticles qty Group
Re: Problem with Terminal server /Licence servermicrosoft.public.windows.terminal_services ·