One NetWare 4.11 file server, one NT4sp6a workstation. Server only runs IPX/SPX, workstation runs Netware Client and has TCP/IP installed to connect to web. I recently replaced the NT box, but kept the old hard drive. I had to reinstall TCP/IP to get the nic working. Everything fine for the past few weeks. Since all is ok, I decide to give it our nightly script to run. This script itself is definately ok. It's been running for months on a different (yet similar) pc. It takes about 30 minutes to complete. When I come in the mornings my netware connection is hosed, AND I can't ping this workstation from anywhere. I try rebooting and it hangs at the NT .bmp screen trying to shut down. I thought it might be the TCP/IP, but why does the IPX/SPX not work either. And why would it not shut down on it's own? Also the problem workstation shows no signs of trouble during the day; logs are also clean. Looking at my script to see where it was stopped shows a different section every morning. IP is static, no DHCP, DNS is ok, no WINS, NetBios is ok, connectivity all other times is fine. ANY THOUGHTS?

Netbios, wins have nothing to do with netware so you can eliminate that from the problem group. I am assuming you have ipx/spx on the workstation and you have set that to be the primary protocol. Your first clue was that you HAD to install tcp/ip to get the nic working. Next clue is the connection is hosed as well as ip on the workstation. Sure sounds like a bad nic to me! Malfunctioning hardware behaves as you describe. Nt4 is not acpi compliant so I am not sure why you think it will just shutdown. There was a trick to get a acpi to work on NT if you could run the acpi compliant HAL. That took running winnt32 and choosing that HAL. Didn't work on all systems though. Normally the shutdown command would just reboot the system.

wanderer, thanks for the response! I too was leaning towards hardware but wonder why it works flawlessly during the day. ?@# I will uninstall the netware client, swap out the nic, reinstall latest netware client, reinstall tcp/ip, and update nic driver. I know this is bad pin pointing, but I need this script to run on it's own again asap.

Well guess what.... that wasn't it either. I put back his old NT box and scrapped that project until my Dell guy gets me a good deal on an Optiplex.