thisismatt
asked on
Stop Error after installation
Hi all
I've just installed Windows Server 2003 successfully and completed the first part of configuration as a local domain controller. All went well.
In the box I have two network cards; one of which is on the motherboard and another which is a Netgear WG311T wireless card.
Everything was working fine until I installed the drivers for the card, at which point I got the dreaded BSOD with a stop error with the following codes:
0x0000008e (0xc00000005),0x80556c5f,0
I cannot find out exactly what these are refering to unfortunately.
I'm making the assumption that the wireless card/software is causing a conflict somewhere.
I don't want to revert to a wired connection, as the whole point of going wireless was to prevent any more tripping over cables!!
So, anyone got any ideas? Has anyone got a wireless setup of Server 2003? If so, what wireless card(s) do you use?
Many thanks
Matt
I've just installed Windows Server 2003 successfully and completed the first part of configuration as a local domain controller. All went well.
In the box I have two network cards; one of which is on the motherboard and another which is a Netgear WG311T wireless card.
Everything was working fine until I installed the drivers for the card, at which point I got the dreaded BSOD with a stop error with the following codes:
0x0000008e (0xc00000005),0x80556c5f,0
I cannot find out exactly what these are refering to unfortunately.
I'm making the assumption that the wireless card/software is causing a conflict somewhere.
I don't want to revert to a wired connection, as the whole point of going wireless was to prevent any more tripping over cables!!
So, anyone got any ideas? Has anyone got a wireless setup of Server 2003? If so, what wireless card(s) do you use?
Many thanks
Matt
Open the box back up and remove the new hardware until you install 2003. After all the critical updates, then power down, add the wireless card, go into Bios and disable the onboard NIC card. Boot up and enjoy.
Hi,
Start up using Safe mode, go to the hardware tab and make sure to deïnstall the driver of the NIC. Then, indeed, try what jayca suggest. Update all patches and other stuff. Then, try to install the wireless NIC using the standard Windows 2003 drivers (if you didn't use them) or try using the original ones (anyhowes, other than the ones u used...;)).
I do know that wireless and Server 2003 kinda bite.. I installed it on my laptop using a Linksys card and had to fight it for a day or so to get it to work (sometimes ;))
Start up using Safe mode, go to the hardware tab and make sure to deïnstall the driver of the NIC. Then, indeed, try what jayca suggest. Update all patches and other stuff. Then, try to install the wireless NIC using the standard Windows 2003 drivers (if you didn't use them) or try using the original ones (anyhowes, other than the ones u used...;)).
I do know that wireless and Server 2003 kinda bite.. I installed it on my laptop using a Linksys card and had to fight it for a day or so to get it to work (sometimes ;))
ASKER
jayca and rhandels - thanks for your input here. I'll give it a go over the next few days and see what happens. I guess I need to dig out my cables again!!
So, just to check:
Re-install of Server 2003 (my choice there, just to be sure though!)
Configure on-board NIC
Obtain all MS updates
Install wireless card software (as supplied by Netgear)
Disable the on-board NIC
Enable wireless card
Have I got that right or would you guys suggest any changes?
Matt
So, just to check:
Re-install of Server 2003 (my choice there, just to be sure though!)
Configure on-board NIC
Obtain all MS updates
Install wireless card software (as supplied by Netgear)
Disable the on-board NIC
Enable wireless card
Have I got that right or would you guys suggest any changes?
Matt
Hi,
You don't even need to disable the onboard NIC (if it's not wireless).
You could try to use the Server 2003 drivers for the wireless NIC..
You don't even need to disable the onboard NIC (if it's not wireless).
You could try to use the Server 2003 drivers for the wireless NIC..
ASKER
The server didn't recognise the card while it was in the box, so I assumed that there were no drivers present to run the baby.....am I wrong there?
>>The server didn't recognise the card while it was in the box, so I assumed that there were no drivers present to run the baby.....am I wrong there?<<
No you're not. Then, you will need the Netgear drivers and software (shouldn't be a problem).... Do make sure it is 2003 Server compliant (i could say on the HCL, but there are a lot of hardware vendors that are not on the HCL)
No you're not. Then, you will need the Netgear drivers and software (shouldn't be a problem).... Do make sure it is 2003 Server compliant (i could say on the HCL, but there are a lot of hardware vendors that are not on the HCL)
ASKER
I did look on the Server Catalog earlier on to see if it's listed, but it's not. In that case, how do I know if it's supported or not? That's been my assumption so far - that it isn't supported.
If that is the case, do you know a wireless card that IS supported by Server 2003?!
*pulls more hair out*
If that is the case, do you know a wireless card that IS supported by Server 2003?!
*pulls more hair out*
ASKER
Just done some more research and I could use a wireless bridge to connect the server to the network, without having to use any new hardware IN the box; instead I can plug this bridge into the ethernet connection on the motherbord; thereby removing the problem that Server 2003 has with with the wireless card!
Would that work?
Would that work?
Don't know, could be working, you could try it. But i would say look at the 2003 HCL (Hardware Compatibility List) to see if you can find a wireless NIC that's on the HCL. I would suggest using an Intel or 3Com card, they are normally on the HCL..
Agree
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why don't you sent the Access point up near the server, and use a cable, just for that connection? I have an inherent fear of transferring critical data over a wireless connection. I'd be real careful if I were you...