Every 3 days or so, it reboots itself during normal running, throwing out
all the users.
I have been fortunate enough to be looking at the svr console when this has
happened - it goes straight from a healthy-looking console to the POST
routine as if the reset button had just been pressed - no BSOD, and no
entries in the Event Logs apart from 'The server shutdown at <TIME> was
unexpected".
The server is a Dual P3 Xeon 500MHz Dell PowerEdge 6300 with 2Gb RAM.
The only perhipherals are the inbuilt RAID/SCSI setup and an Intel
EtherExpress 100 NIC.
The only applications running on it are MS Office 97 pro, a 32-bit terminal
emulation package for access to a UNIX box and HP JetAdmin for access to
network printers (all are HP w/JetDirect). It also runs an agent for our
ArcServeIT 6.5 backup system.
The TS is a member server in an NT Domain (the PDC is on NT4 SP5).
It supports ~30 users at present, and has never showed more than 25%
processor utilisation.
The server hardware and power supply have been checked and are OK.
There are no 3rd party drivers installed on this machine, for printers or
otherwise. All driver files came from the TS CD-ROM.
No users have authority to shut down the server, so this cannot be the
problem.
So what can it be?
Anyone have any ideas?
Nick Farina
> Every 3 days or so, it reboots itself during normal running, throwing out
> all the users.
We have started to experience the same problem.
> The server is a Dual P3 Xeon 500MHz Dell PowerEdge 6300 with 2Gb RAM.
> The only perhipherals are the inbuilt RAID/SCSI setup and an Intel
> EtherExpress 100 NIC.
Quad P3 Xeon 500MhZ Dell PowerEdge somethingorother with 2Gb of Ram.
Same RAID and NIC too. A spooky co-incidence?
> The server hardware and power supply have been checked and are OK.
Running on a UPS so can pretty much rule out power spikes/drains.
Perhaps its a problem with this model of Dell PowerEdge?
--
Andrew Carpenter
Computing Technician
Cirencester College
andrew.c...@cirencester.ac.uk
ICQ : 20885021
NO users connected (new setup), just sits there happily then when we
next look, there is the logon screen! Just like hitting reset.
Melak
As the system rebooted when we lost connectivity, we think it could be a
problem with Autonegotiate. Our system should have negotiated 100Mb/Full
successfully, but the drivers supplied don't give an easy way of finding
out.
Are you sure you don't get an event in the eventlog? We get a ".. the
previous shutdown at xx:xx on xx:xx:1999 was unexpected."
Also, I believe HP printer drivers have been a source of much grief (BSOD
stop 0x50 errors, etc)
regards,
Stuart.
Melak <me...@bigfoot.com> wrote in message
news:0q=nN=jp76rPgsTvL...@4ax.com...
> Also, I believe HP printer drivers have been a source of much grief (BSOD
> stop 0x50 errors, etc)
Argh! Don't talk to me about HP printer drivers! That's the only make of
printer we are using! Had to resort to using the DeskJet 660 driver to power
any of the colour DeskJets.. can't get any of the others to work!
We experience Blue Screen of Death (windows nt style) quite often too. I don't
wanna tell my boss we have to scrap all the HP's. We just bought another 18 new
ones.
Which ones are known to cause issues? Is there a list of them anywhere?
Nick.
Andrew Carpenter wrote in message ...
> What are you telling me? That even Terminal Server's built-in printer
> drivers cause problems.
>
> Which ones are known to cause issues? Is there a list of them anywhere?
>
> Nick.
I've lost track of exactly which drivers we're using now, either built in or
downloaded. Trouble is, HP have just gone so overboard with their drivers.
Even just installing the driver without the toolbox for the latest DeskJet 610c
model, every time someone prints it bought up a EULA on the server and refused
to do anything until OK was clicked. Even then, all the printer did after that
was to prime the cartridges, then nothing. I have found that the 660c driver
works well for all colour deskjet's.
I don't know if they are the cause of our troubles, I hope not.
>We experienced this phenomenon today when one of our etherswitch modules was
>reset. Our system is a Dell PE6300/4xZeon 500/4Gb RAM, PERC SCSI
>controller, Intel EEPro100.
>
>As the system rebooted when we lost connectivity, we think it could be a
>problem with Autonegotiate. Our system should have negotiated 100Mb/Full
>successfully, but the drivers supplied don't give an easy way of finding
>out.
>
>Are you sure you don't get an event in the eventlog? We get a ".. the
>previous shutdown at xx:xx on xx:xx:1999 was unexpected."
SORRY, I do get that message. What I meant was that there was nothing
helpfull in the log. <g>.
>
>Also, I believe HP printer drivers have been a source of much grief (BSOD
>stop 0x50 errors, etc)
I do have the drivers for the HP 4050TN printer installed. I'll check
for newer versions.
Take care,
Melak.
we figured out, that a certain printer driver would cause the mistake. after
removing the epson printer driver (model sq, of course not an original
tse-driver), the system worked fine without any reboot.
hp1120c works fine
dino
eber...@4net.ch
Nick wrote:
> We haave a problem with our Terminal Server 4.0 SP4 / Metaframe 1.8 server.
>
> Every 3 days or so, it reboots itself during normal running, throwing out
> all the users.
>
> I have been fortunate enough to be looking at the svr console when this has
> happened - it goes straight from a healthy-looking console to the POST
> routine as if the reset button had just been pressed - no BSOD, and no
> entries in the Event Logs apart from 'The server shutdown at <TIME> was
> unexpected".
>
> The server is a Dual P3 Xeon 500MHz Dell PowerEdge 6300 with 2Gb RAM.
> The only perhipherals are the inbuilt RAID/SCSI setup and an Intel
> EtherExpress 100 NIC.
>
> The only applications running on it are MS Office 97 pro, a 32-bit terminal
> emulation package for access to a UNIX box and HP JetAdmin for access to
> network printers (all are HP w/JetDirect). It also runs an agent for our
> ArcServeIT 6.5 backup system.
>
> The TS is a member server in an NT Domain (the PDC is on NT4 SP5).
>
> It supports ~30 users at present, and has never showed more than 25%
> processor utilisation.
>
> The server hardware and power supply have been checked and are OK.
>
Q191666
Q221509 (this one explains a lot) !
My Compaq 6500 did the same.
Are you mapping local printers through NT or 95 - this might be the problem.
Bobsta
Stuart Preston <s.pr...@NOSPAM.ucl.ac.uk> wrote in message
news:7sb7qi$5j6$1...@uns-a.ucl.ac.uk...
> We experienced this phenomenon today when one of our etherswitch modules
was
> reset. Our system is a Dell PE6300/4xZeon 500/4Gb RAM, PERC SCSI
> controller, Intel EEPro100.
>
> As the system rebooted when we lost connectivity, we think it could be a
> problem with Autonegotiate. Our system should have negotiated 100Mb/Full
> successfully, but the drivers supplied don't give an easy way of finding
> out.
>
> Are you sure you don't get an event in the eventlog? We get a ".. the
> previous shutdown at xx:xx on xx:xx:1999 was unexpected."
>
> Also, I believe HP printer drivers have been a source of much grief (BSOD
> stop 0x50 errors, etc)
>
> regards,
> Stuart.
>
> Melak <me...@bigfoot.com> wrote in message
> news:0q=nN=jp76rPgsTvL...@4ax.com...
> > I have the same problem but I'm running on an IBM Netfinity 5500,
> > 512GB RAM, 1 Xenon 500
> >
> > NO users connected (new setup), just sits there happily then when we
> > next look, there is the logon screen! Just like hitting reset.
> >
> > Melak
> >
> > On Mon, 20 Sep 1999 01:07:48 +0100, "Andrew Carpenter"
> > <ne...@gloucestershire.freeserve.co.uk> wrote:
> >
> > >
> > >Nick wrote in message news:#g3Wz2qA$GA.197@cppssbbsa03...
> > >
> > >> Every 3 days or so, it reboots itself during normal running, throwing
> out
> > >> all the users.
> > >
> > >We have started to experience the same problem.
> > >
> > >> The server is a Dual P3 Xeon 500MHz Dell PowerEdge 6300 with 2Gb RAM.
> > >> The only perhipherals are the inbuilt RAID/SCSI setup and an Intel
> > >> EtherExpress 100 NIC.
> > >
> > >Quad P3 Xeon 500MhZ Dell PowerEdge somethingorother with 2Gb of Ram.
> > >Same RAID and NIC too. A spooky co-incidence?
> > >
> > >> The server hardware and power supply have been checked and are OK.
> > >
There is a known problem with Cirrus video adapters
and terminal server. Our Compaq did the same. We
changed the video driver to standard VGA and it
has not happened since.
JF du Plessis
-----Original Message-----
From: Nick [mailto:nick....@virgin.net]
Posted At: 19 September 1999 04:53
Posted To: misc
Conversation: Server reboots itself at random - no BSOD, no entry in
Event Log
Subject: Server reboots itself at random - no BSOD, no entry in Event
Log
We haave a problem with our Terminal Server 4.0 SP4 / Metaframe 1.8
server.
Every 3 days or so, it reboots itself during normal running, throwing
out
all the users.
I have been fortunate enough to be looking at the svr console when this
has
happened - it goes straight from a healthy-looking console to the POST
routine as if the reset button had just been pressed - no BSOD, and no
entries in the Event Logs apart from 'The server shutdown at <TIME> was
unexpected".
The server is a Dual P3 Xeon 500MHz Dell PowerEdge 6300 with 2Gb RAM.
The only perhipherals are the inbuilt RAID/SCSI setup and an Intel
EtherExpress 100 NIC.
The only applications running on it are MS Office 97 pro, a 32-bit
terminal
emulation package for access to a UNIX box and HP JetAdmin for access to
network printers (all are HP w/JetDirect). It also runs an agent for
our
ArcServeIT 6.5 backup system.
The TS is a member server in an NT Domain (the PDC is on NT4 SP5).
It supports ~30 users at present, and has never showed more than 25%
processor utilisation.
The server hardware and power supply have been checked and are OK.
There are no 3rd party drivers installed on this machine, for printers