We have been having periodic abends when attempting WOL, it does attempt
to do WOL across our routers (2 locations with T1 between them) which
are not set to broadcast those packets. (routers were installed and
maintained by 3rd party as part of our VOIP package)

I know I am behind abit on the service packs, but I did install the
latest TCP/IP patches (tcpip661e) which reportedly would solve the
issue. Prior abends would just be a simple abend, all other processes
would continue normally - server would stay up. After restarting for
the patches to get applied, the abend now caused a server restart.

Do I also need to apply the NW 6.5sp5 to resolve this? will setting the
routers to allowing these packets solve it?

We have 200 workstations that it attempts to wake up. somewhat less
than 1/2 are across the WAN.

here is the beginning of the latest abend log: (I can post it completely
if needed)
************************************************** *******
Novell Netware, V6.5 Support Pack 3 - CPR Release
PVER: 6.50.03

Server DEMETER halted Thursday, February 23, 2006 3:49:32.711 am
Abend 1 on P00: Server-5.70.03: Double Fault Processor Exception (Error
code 00000000)

CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 0068 SS = 0068
EAX = 814C4013 EBX = 814C4215 ECX = 00000013 EDX = 00000013
ESI = 814C4214 EDI = 814C3FB9 EBP = 00000000 ESP = 814C3FB8
EIP = 0034DC8D FLAGS = 00010002
0034DC8D 880424 MOV [ESP]=?, AL
EIP in SERVER.NLM at code start +001493CDh

The violation occurred while processing the following instruction:
0034DC8D 880424 MOV [ESP], AL
0034DC90 8AC1 MOV AL, CL
0034DC92 C1E902 SHR ECX, 02
0034DC97 2403 AND AL, 03
0034DC99 8AC8 MOV CL, AL
0034DC9D 89E0 MOV EAX, ESP
0034DC9F 50 PUSH EAX
0034DCA0 E82B5D0100 CALL SERVER.NLM|CryptSymbolStruct

Running process: Interrupt service routine (nested count 2)
Interrupted process: Java_549 WUOL Service Thread-T1 Process
Thread Owned by NLM: JAVA.NLM
Stack pointer: 816F9238
OS Stack limit: 816CA060
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack dump exceeded the valid memory limit

Additional Information:
The hardware detected a problem while executing an interrupt
service routine. The code being executed is owned by SERVER.NLM. It
may be the source of the problem or there may have been a memory corruption.
************************************************** *******

Michael Alexander
Network Administrator
Milwaukee Valve