Windows Server 2003 Network problems

[RobinPCG]

I've installed a fresh copy of 2003 Server on a Dell 1425SC server. After a few reboots network connections crashes on start up and I can't access or troubleshoot the network. The only thing that I can see that might be causing this is Windows update. When I run the Windows repair from the CD everything works fine again for a while. I can't find anything like this on google. Has anyone heard of something like this happening before?

 

[justin42279]

It might help if we had a little bit more info.

What do you mean by the network connection crashes? Are you able to ping anything?

What is your network made up of?

Justin

 

[RobinPCG]

I mean the Service Network Connections crashes. I can't see any of my connections in the Network Connections Window.

 

[justin42279]

Have you checked event viewer for any errors related to the network connections service crashing?

 

[RobinPCG]

There are a series of errors relating to not having the network avaiable, but the first one is "SAM failed to start the TCP/IP or IPX/SPX listening thread.

 

[justin42279]

What happens if you try to start the service manually?

 

[RobinPCG]

Nothing, it hangs.

 

[jonhowe]

have you applied any Dell or other manufacturer specific drivers for the server / NIC or is it just using whatever Win2003 detected and installed ?
Jonathan

 

[RobinPCG]

The Dell driver and the 2003 server driver appear to be the same. I tried to install the Dell driver but it wouldn't update.

 

[PoliMalaka]

Are you using two NICs?
Are you using the Broadcom NLB? I found that when i would use that and try to use both nics i would lose the network.

 

[jonhowe]

I'm slightly confused by your description of the problem.

Are you saying that all is OK until you run a windows update ?

Have you applied service pack 1 ?

Is your server connected directly to the Internet or is is behind a hardware firewall ?

I would suggest a trial like this :
find a spare hub/switch
plug in server only
wipe and reinstall win2003
apply service pack one
what is the status at this point ?

 

[Gobster]

Can you confirm the client for microsoft networking is installed and enabled on all NIC's?

 

[RobinPCG]

It isn't a simply connectivity issue, the Network Connections Service crashes. The server has two Intel 1000MT NIC's, but one of them isn't being used. My installation of 2003 Server already has SP1. Network Connections only crashes after I install updates. This isn't a server that is being used for production purposes so I haven't been able to spend a lot of time looking at it. I suppose that I need to figure out which update, if it is indeed a single update, that is causing the problem. It's such a strange problem, I was just hoping that someone might have run across it before.

 

[compuveg]

If it isn't in production, take it offline and run hardware diags on it. It sounds to me like a hardware issue.

I would also make sure that all the plug n play IRQs are good. I've had instances where IRQ 9 was used, causing trouble. (Because PCs only have 8 IRQs, IRQ 2 'cascades' to 9, creating somehow the IRQs 9-15. I don't understand it, but generally speaking it is true)

I had a server that abended just last weekend due to the IRQ 9 being used by the RAID controller. Nothing else was on IRQ 9, but it made a world of difference when we swithced it to IRQ 7. IRQ 9 worked great for the last 2 years, but a patch applied Friday made it a problem.

Do note, that in my situation above, the hardware passed all diags after multiple runs. I just happenned to be looking around BIOS/CMOS after testing and saw the RAID controller on 9 and remembered that being a problem long ago when IRQs were set with jumpers.

Good luck, let us know how it goes.

 

[RobinPCG]

I'm just not familar enough with Server, I'll try some of these suggestoins. I'm a college student that is brought in on the cheap to run their whole small office domain. I only work 15 hours a week and am expected to do everything. *sigh* I love being in IT. Thanks for the help.

 

[compuveg]

That's a great place to be, and how I got started. It feels like that's where I still am because I still don't know anything about the servers I admin. That's the IT game, always learning.

Also, since the machine's not in production, don't hesitate to just wipe the disk and start over.

 

[kulpins]

I am having this same problem. It appeared on a Dell GX260, WS2K3SP1, with all current updates (as of 10/12/2005). The network suddenly stopped. I checked, and the Network Connections Service stopped, and would not run. The error logged was the one that started this thread ("SAM failed to start the TCP/IP...."). I searched for a cause, but I found nothing. I installed a Ghost image of the O/S in it's pristeen state, and after a few reboots, the same thing happened. I then replaced the NIC, and the same thing happened. I then installed the O/S fresh (from an install disk), and did NO updates. After a few reboots, the same thing happened. I've been messing with this for 2 days now, and I'm at a loss. Any thoughts or suggestions would be greatly appreciated!

 

[RobinPCG]

I still have found no solution other than not updating. I'm also having problems with Routing and Remote Access. I want to set up a VPN, but I am denied access to all policy changes through R&RA as Administrator. I am not impressed with Server 2003.

 

[ZipperHeadMan]

remove or disable the second NIC.
I tend to agree, this is a hardware issue.

 

[ZipperHeadMan]

PS...I guess you like NT 4 better? LMAO
Your skills need to be sharpened before you knock the OS.
Have you called Dell? They might have a BIOS update.