help compaq server w2k big prob

[billb]

heeeeelp about about to run away screaming..

have a compaq proliant ml530 running w2k advanced server

you boot up with net cable in it blue screens a few seconds after log on screen comes up

you boot up without net cable in it works fine until you plug in the cable and it blue screens after a few mins

you boot up in safe mode with net cable in and its fine even with networking


have replaced switch, cable, net card drivers, net card, system board, memory with no luck.

put disks in another server and it still does it so dont think its hardware.

any ideas? what happens when u put a net cable in that could cause it to blue screen????

[malman]

What are the blue screen details? Is it IRQ not equal....?

[billb]

malman said:

What are the blue screen details? Is it IRQ not equal....?

seem to get various different ones that was one of them

[malman]

I can't find the details now but I had one the other day that was getting corrupt packets (from a router) which was causing BSOD. On MSKB it was post sp4 hotfix but only for this specific problem.

Can you block traffic to the switch port then plug it in to see if its software/traffic/service related or hardware. Auto negotiated of fixed rates? Can you move onto another IP so its logically not on the network?

When you changed NIC was the replacement the same model?

Sorry if you've tried these already

[billb]

malman said:

I can't find the details now but I had one the other day that was getting corrupt packets (from a router) which was causing BSOD. On MSKB it was post sp4 hotfix but only for this specific problem. Can you block traffic to the switch port then plug it in to see if its software/traffic/service related or hardware. Auto negotiated of fixed rates? Can you move onto another IP so its logically not on the network? When you changed NIC was the replacement the same model? Sorry if you've tried these already

hotfix sounds interesting do u know which one it was?

has 2 net cards in a 10/100 one thats built in and a gigabit one thats been added. took the disks out and put it in identical server and it did the same thing so its not the cards hardware.

have plugged it into switch port other servers are on which work fine and it still blue screens - its all on auto

will try changing ip

thanks for help

[malman]

Arrggghh can't find it now! Found it straight away the other day. I hate MSKB at times.

Take note of any BSODs then go through the MSKB and see if there is a common thread.

The problem mine showed was in afd.sys with corrupt network packets killing it.

Sorry can't be more help

[timsta]

It's been a while since I've used Compaq Servers, but I seem to remember an issue with auto-negotiation. I think we were using Smart Switch or Cisco Switches.

Something about auto-negotiation not being the same system. Try setting the speed and type of connection on the Network connection properties.

Tim

>> Edited by timsta on Tuesday 10th August 01:08

[billb]

right this is really getting annoying!!

have made the server so its just using the built in 10/100 card only. this has been replaced as its on the system board that was replaced so hardware should be okay.

if you disable it and boot up with net cable in its fine until you enable it and then it blue screens.

if you enable it and boot up without the cable in it works fine until you plug the net cable in and then it blue screens.

you can plug the cable into a switch thats on and not connected to the network and its fine but the sec u put it on our network ( have tried 2 switches ) bam it blue screens.


so what is loading either just after the log on screen ( which is were it blue screens when the cable is in )or within about 20 seconds of being logged on on and putting the cable in? or is it a driver issue - have tried reinstalling driver and going back to an old driver to no avail

have disabled av, remote software


heeeeeeeeeeeeeeeeeeeeeeeeelp

[ATG]

You say when it boots in safe mode, then everything is OK? I'd be finding out what is the precise difference between safe mode and normal. It doesn't sound like that is going to be anything to do with hardware, and I don't suppose its going to be anything to do with drivers either ... both of these will surely be used in the same way regardless of the start-up mode?

[plotloss]

Tried installing Windows on top of itself?

[billb]

plotloss said:

Tried installing Windows on top of itself?

bit scared of doing that as its an apps server that has 101 weird and wonderful programs on it all of which have prob changed the registry etc. would reinstalling windows wipe all this?

yes it boots fine in "safe mode with networking" - anyone know what else happens when not in safe mode?

[plotloss]

Yeah potentially, depending on the state of the registry.

Hmmmn.

If its working in safe mode with networking its using the same drivers as normal mode for the NIC.

It sounds like there is a corrupt module somewhere in windows to me, finding the one though is going to be the bugger.

[apeebles]

I think that Timsta might have hit the nail on the head. I seem to remember a similar problem which was cured by turning off auto-negotitiation on the Cisco switch and setting the speed to 100MB (or 1GB) and also turning on full duplex. Once this was done on the server as well everything worked perfectly.

This may be something you have already done but it is worth a shot.

[timsta]

apeebles said:

I think that Timsta might have hit the nail on the head. I seem to remember a similar problem which was cured by turning off auto-negotitiation on the Cisco switch and setting the speed to 100MB (or 1GB) and also turning on full duplex. Once this was done on the server as well everything worked perfectly. This may be something you have already done but it is worth a shot.

Yep. It was something to do with Cisco and Compaq. You would think that two of the bigest names in the business would test stuff that would likely to be plugged into each other. We changed the settings on the Server, cos the network was a no-no.

It Blue Screens when you switch the Switch on because the server detects the switch connection and auto-negotiates (well, tries and fails to negotiate) the speed, etc.

On the network connection: Properties, Configure, Advanced, one of the settings in there will let you set it to not auto-negootiate.

[billb]

IM SO HAPPY!!! in a cautious way!!

seem to have fixed it after trying everything under the sun. ended up u couldnt delete tcpip from the net card whatever you tried until followed msoft kb article on deleting it via the registry and it seems to have worked!!

so bloody corrupt tcpip was the cause! at a guess could have been service pack 4 and a cdserver client i have on there that did it or it could have just done it on its own. whatever it seems to be working so fingers crossed.


thanks for all the suggestions etc it helps to get some advice

[GregE240]

Good to hear it Bill. Sorry I couldn't help you on this occasion.

Actually, I think PH has a 100% success rate on problems I've asked here...either someone knows the answer or points you in the right direction.

What a bunch of clever people we all are

[malman]

Glad to hear its back up

Neil