We bought an IBM Server, cpu 3,2ghz,3 HDD Raid 5, in october 2005. We have 55 workstations in our Netware Lan, using novell client v83 or v92, and OS win98 or Win Xp. It worked well for 1 month, then some problems occured. In January 23, and 27 the server restarted and some sheduled application could not be resolved. The messages appeared in Sys#log.err are the next : (I shall not send all the sys$log.err file only some parts of it) Monday, 2006-01-23 9:37 LAN Traffic on server OTL was in a BAD State Current Value - 0 Peak Value - 23273 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Monday, 2006-01-23 9:37 LAN Traffic on server OTL has returned to the GOOD State Current Value - 1 Peak Value - 23273 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Tuesday, 2006-01-24 10:58 Failed Logins Per Hour on server OTL was in a SUSPECT State Current Value - 5 Peak Value - 5 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = -1 threshold = More than 12 Failed Logins <HR NOSHADE ALIGN=RIGHT> Tuesday, 2006-01-24 11:37 Failed Logins Per Hour on server OTL has returned to the GOOD State Current Value - 3 Peak Value - 5 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = -1 threshold = More than 12 Failed Logins <HR NOSHADE ALIGN=RIGHT> Tuesday, 2006-01-24 11:44 Failed Logins Per Hour on server OTL was in a SUSPECT State Current Value - 4 Peak Value - 5 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = -1 threshold = More than 12 Failed Logins <HR NOSHADE ALIGN=RIGHT> Tuesday, 2006-01-24 11:58 Failed Logins Per Hour on server OTL has returned to the GOOD State Current Value - 2 Peak Value - 5 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = -1 threshold = More than 12 Failed Logins <HR NOSHADE ALIGN=RIGHT> Tuesday, 2006-01-24 12:24 Failed Logins Per Hour on server OTL was in a SUSPECT State . . . . . . . . Friday, 2006-01-27 8:14 LAN Traffic on server OTL has returned to the GOOD State Current Value - 1 Peak Value - 23617 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Friday, 2006-01-27 8:30 LAN Traffic on server OTL was in a BAD State Current Value - 0 Peak Value - 23617 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Friday, 2006-01-27 8:30 LAN Traffic on server OTL has returned to the GOOD State Current Value - 1 Peak Value - 23617 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Friday, 2006-01-27 8:36 LAN Traffic on server OTL was in a BAD State Current Value - 0 Peak Value - 23617 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 <HR NOSHADE ALIGN=RIGHT> Friday, 2006-01-27 8:36 LAN Traffic on server OTL has returned to the GOOD State Current Value - 1 Peak Value - 23617 Max Value - N/A Current SUSPECT trigger delay = -1 and Critical trigger delay = 60 We have to built in Lan cards in the server. What could be the problem ? How can we resolve to stop restarting server ? Please give us some advice. Thanks Veres Janos OTL RA Oradea, Romania