Why is one machine killing other machine DEAD?

[morningtrader]

I got this strange problem fixed but I'd sure like to understand why it happened, so I can prevent a reoccurrence.

Network set up 192.168.0.1, 192.168.0.2, etc. SOMETHING reset the Ethernet TCP for the 192.168.0.1 machine back to "obtain an IP automatically". Didn't know it and using the 192.168.0.2 machine, I was able to pull up files from #1 for a day or two. Then, at some point, pulling up even a .txt file caused the #1 to crash AND (here's the funny part) the BIOS screen would just sit there and not load. The power on/off stopped working completely. The only way to reboot was to pull the cord out and reattach it.

When I figured out the IP had changed, reinstalled TCP and the Ethernet driver, renumbered the network and its working again.

So I have two questions so I don't see this again:
1. Can a demonic program or the system itself change the IP settings without me doing it?
2. Why did it also affect the boot from ROM and power supply, which shouldn't have anything to do with OS issues?

Should add this last tidbit, which might be related. The #1 is win98se, #2 is win2k (administrator). I intentionally have never set access for the #1 machine back to #2 (by setting a user profile on win2k). This has been a nice way to control access since #1 is the server for my Net connection.

Thanks guys.....

😕

------------------
Alan

 

[morningtrader]

1 mercybump

 

[spidey07]

possibly try general hardware forum

only thing i can think of is somekind of hardware conflict. try a different PCI slot maybe?

 

[me19562]

i am with spidey, maybe a hardware conflict or even a faulty NIC

 

[bot2600]

the only time i saw something like this was when I was assigning 2 ips to one nic, each ip being on a different network. the one ip was for internal network, the other ip was to cablemodem, all machine including cable modem were hooked to hub, but only the one ip on the nic actually talked to the cable modem, the other ip was for proxy for the internal network. this is not how it is supposed to be set up, I should have been using 2 nics, just didnt know that at the time. this setup worked ok for awhile, then one day, if one particular machine would try to surf the net, the proxy machine would reboot and lock up just like that. ended up adding another nic and solved the problem. doesnt sound like that is your problem, but I just felt like rambling about my stupidity...

Bot

 

[morningtrader]

Maybe I'm on the wrong track and this is OS related. It happened again this evening, but I've isolated it to only occurring when I'm accessing .txt files through Explorer. My notepad freezes, the remote crashes and then the wierdest thing happens. The remote starts to boot and the notepad pops open the requested file (on the "good" machine) during the (remote) splash screen! Bizarre. Ran a log. Maybe, just maybe its a demonic font being called. Look at the corrupted (?) file failing to load.

Sorry if this turns out to be in the wrong section. BTW anyway to figure what font that gooblygook is?

Alan

LoadStart = c:\windows\fonts\smalle.fon
LoadSuccess = c:\windows\fonts\smalle.fon
LoadStart = g¶&egrave;reb.ttf <--------------------------------------------------------------------------------------
LoadFail = g¶&egrave;reb.ttf Failure code is 0002

LoadStart = ABSN__DB.TTF
LoadFail = ABSN__DB.TTF Failure code is 0002

LoadStart = AGCLN_DB.TTF
LoadFail = AGCLN_DB.TTF Failure code is 0002

LoadStart = AGCLI_DB.TTF
LoadFail = AGCLI_DB.TTF Failure code is 0002

LoadStart = AGCMN_DB.TTF
LoadFail = AGCMN_DB.TTF Failure code is 0002

LoadStart = AGCN__DB.TTF
LoadFail = AGCN__DB.TTF Failure code is 0002

LoadStart = AMN___DB.TTF
LoadFail = AMN___DB.TTF Failure code is 0002

LoadStart = CALN__DB.TTF
LoadFail = CALN__DB.TTF Failure code is 0002

LoadStart = CLRB__DB.TTF
LoadFail = CLRB__DB.TTF Failure code is 0002

LoadStart = CLRN__DB.TTF
LoadFail = CLRN__DB.TTF Failure code is 0002

LoadStart = CLRBN_DB.TTF
LoadFail = CLRBN_DB.TTF Failure code is 0002

LoadStart = EXCN__DB.TTF
LoadFail = EXCN__DB.TTF Failure code is 0002

LoadStart = EXCI__DB.TTF
LoadFail = EXCI__DB.TTF Failure code is 0002

LoadStart = HEN___DB.TTF
LoadFail = HEN___DB.TTF Failure code is 0002

LoadStart = HEB___DB.TTF
LoadFail = HEB___DB.TTF Failure code is 0002

LoadStart = HEI___DB.TTF
LoadFail = HEI___DB.TTF Failure code is 0002

LoadSuccess = user.exe