Question Locked

DHCP server on SBS2003 stops Need assist

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

sbs 2003
On reboot DHCP works fine. scopes are set so on and so forth.
1 NIC system
after a short bit (20-30 min) DHCP stops and cannot be restarted (error is DCHP had nothing to do blah blah blah)

also get error TCPSVCS memory cannot read error.
Once this happens cannot remotely connect to server.
Reboot and all works fine for the 20-30 min

Also Windows Firewall wont run.
Previously was a 2 NIC setup with ICS but since have changed.

10 replies

by csheppard

Go to Start > Run > services.msc

For your firewall, go down to Windows Firewall and make sure its set to Automatic and then Start.

For your DHCP, go down to DHCP Server and make sure its set to Automatic and then Start

Also, while in the DHCP properties, click on the Recovery tab and for first second and subsequent failures, you want it set to Restart the Service.

by ddoyle

let's take the DCHP as it's the most important.
it's Auto. and restart on failure is and has been set.
If i manually start the service it trys to start then shuts back down.
I think it has something to do with the tcpsvcs error coming back
not sure though.

by bart777

I've seen this problem before.
Most likely there is another DHCP server somewhere on the newtowk. You need to find the culprit. Unfortunately the only way to do it is to wait until another failure. Unless of course you know which device it is. SBS will not play with other DHCP servers.
In my case there was a small print server device that was passing DHCP and causing havoc on the network.

Good luck

by cg it

did you run the CIECW wizard again? have to run the CIECW wizard for any and all changes to the way SBS handles traffic. example: If you change out a NIC, you have to rerun it. Change addresses, have to rerun it. change router IP address have to run it. Change DHCP scope, have to run it.

make sure any dependencies for DHCP are also in the auto state and are running.

Note: Windows Firewall does not run and can't be turned on with the 1 NIC configuration. This is by design. Reason: If the firewall is on, clients on the lan can't reach the server. Remember, SBS is designed to be configured by the wizards so that the server can be configured & up and running by someone with minimal tech knowlege. If you try to manually configure SBS like you do a Windows Standard Server, that tends to break things.

by ddoyle

Change from 2 Nic to 1 Nic was done about a year ago. All nessecary DCHP changes were made, the Connection I-Net wiz was ran and so on.
In the last month or so started noticing that remote connection was not possible 20-30 min after server reboot.
Reboot fixed the problem, or so i thought.
Started delving deeper and noticed DHCP service had stopped.
I know by security logs we are getting some thing like 20k incoming account hack attempts a day.
At one point i know something or someone got in because all Admin accounts were deleted. Primary admin account was untouched.
I did a restore and got back all that info. but am left with the same issue of DHCP starting up fine at reboot and then some time after just no longer working.. cannot even restart it.
IE my reason for trying to work out some firewall.

by ddoyle

Yeah, had that problem last year when we took it down to 1 nic. Router had DCHP running. that's been disabled for some time now though.
I honestly think the system has been under an attack of some sort and i cannot figure out where the stopage is coming from.

by cg it

sounds omminous...

I've had a problem similar to this but not quite the same crop up on SBS box. The only way I fixed it was to rerun the SBS setup.

I've also fixed a funky DHCP on a SBS box by unauthorizing the existing scope, create a new scope using the same addressing, then authorize it. The problem with this is that you'll get errors in the event log that DHCP can't be backed up.

by ddoyle

Ok, from reboot.....
Starts up with TCPSVCS error
At desktop gives 1-2 more TCPSVCS errors
Check services and DHCP is NOT running
Remote log in from web works fine.
Run Inet connection wiz and says that DHCP is not running..
Run DHCP and nothing shows up, Pull up authorized DHCP and it wont connect to it says no running.. so cannot remove and reset up scope.

After some time.. Remote log in from web no longer works. says connection does not support..

Web Outlook works fine thru all of it.

I know there is no other DHCP because today i had to set up all the workstations with Static IP

Seems at no time does DNS service go down either.

If i rerun setup on the SBS, what will i lose? Users? mail?

by cg it

but if that also fails I suggest you go here and ask a question on the forum for Small Business Server. The Microsoft techs for small business usually will reply with what they know [these are the MS SBS developer/programmer guys] .

http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.sbs&mid=b5a48b5c-6ac6-48f6-932d-4359da33f490&sloc=en-us

Rerunning Setup you get to choose what you want to do. you can reinstall portions of SBS or do maintenance or do nothing to the component. This works well if your intranet web site messes up which I've had happen on more than couple of SBS installs. you just reinstall that component.

pop in the first SBS CD and you'll see that you get to choose what to do.

you don't want to reinstall.. better to reinstall with an older backup...

oh and I'd check who's got remote access rights and make sure only those who are supposed to are listed.

This discussion is closed to new replies.