Discussion Locked

LDAP Connection

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

Hi

My Win2k File server running Small Business Server 2k suffered two power failures this weekend and both DNS and DHCP servers (running on this machine) have stopped working.

Rebooting has not helped. The first reboot produced STOP: 0x000000IE (0xC000005, 0x804172A9...) Address 804172A9 then the machine rebooted after the memory dump so I could not get the rest of the error, but the application was ntoskernel.exe Rebooting into Safe Mode with network support takes a long time but I can at least get into the machine.

If I try to change the security on any object I get a Network path not found error when trying to add a user's account to security on a share.

I ran DCDIAG but get an error: 'LDAP connection failed with error 1231'

Does anyone know what this means?

I cannot manupulate DNS or DHCP at all. Should I try to uninstall, then reinstall these through Add/Remove Programs\Windows Components?

Any help with this will be appreciated.

5 replies

by curacao_dejavu

Hi,

You should have any error messages in the eventviewer of some services that are not starting.
From there we can proceed.You could reinstall the services and then the w2ksp4.

try this see if it help too.
The "TCP/IP NetBIOS Helper" Service is not started on the client computer. Launch services.msc and set the "TCP/IP NetBIOS Helper" Service's startup type to Automatic and start it.

Leopold

by blackcurrant

Thanks for answering. The solution was to uninstall both DNS and DHCP via Add/Remove programs, reboot the computer, then reinstall DNS only. The DNS server reinstalled and automatically configured itself, and now works fine (the network is based around a single AD domain). Because my network only has 24 machines, we decided to apply static IP addresses to all the machines (which allowed connection to the server which was not being allowed when DNS failed), and therefore, not to reinstall DHCP.

by mark

I know this sounds pretty basic, but I had this happen once and a CHKDSK with surface scan fixed the problem.

by blackcurrant

Thanks for answering. The solution was to uninstall both DNS and DHCP via Add/Remove programs, reboot the computer, then reinstall DNS only. The DNS server reinstalled and automatically configured itself, and now works fine (the network is based around a single AD domain). Because my network only has 24 machines, we decided to apply static IP addresses to all the machines (which allowed connection to the server which was not being allowed when DNS failed), and therefore, not to reinstall DHCP.

This discussion is closed to new replies.