Link to home
Start Free TrialLog in
Avatar of fasteddie565
fasteddie565Flag for Afghanistan

asked on

SBS 2003 not recognized as a Domain Controller

I have a 2003 small business server that I now just use as file storage unit, but I do use activesync to maintain files between my laptop and the office.

I put a new HD (SSD) in my laptop. I could not image it so I rebuilt the HD. When I try to add the laptop to the domain, The wizard sees the account for the laptop, I enter my user name and info and the final error says no domain controller is found.

I deleted the laptop account from the server and tried to add it via the web browser, same issue

I tried to add it to the domain manually from the laptop, same error

I tried to add it to the domain with the wizard from the laptop, same error.

I rebooted the server and laptop, no joy.  When I look at the server role it says domain controller and it is a member of domain controllers for the domain.ext/users.

No other servers are on the network.
SOLUTION
Avatar of Perarduaadastra
Perarduaadastra
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Larry Struckmeyer MVP
Can/have you run the SBS BPA?  Please do and fix anything it finds.  Also run dcdiag from the tools directory.

What do you see in the event logs of the SBS that may be relevent?
Avatar of fasteddie565

ASKER

I believe that I did reuse the old laptop name. I will change and see if that works,

FF, I will run the diagnostics if the name change does not work.

More later, thanks
Name change did not work, running the BPA and other diagnostics.....
Hello
Please try to use another account - AD administrator or another one, that have necessary rights for creating/changing domain membership. Your personal account maybe doesn't have this right.
Here is the IPconfig /all


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\fast eddie>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : EXECINT02
   Primary Dns Suffix  . . . . . . . : execint.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : execint.local

Ethernet adapter Server Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-18-8B-FD-5C-6E
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.3
   DNS Servers . . . . . . . . . . . : 192.168.1.102
   Primary WINS Server . . . . . . . : 192.168.1.102
The BPA showed errors such as EDNS is enabled, I disabled it as recommended.
Oh, sorry, I meant the output from the laptop that you're trying to join to the domain...

It seems that the server is configured with a single NIC, which is OK, and it points to itself for DNS, which is correct, but is it doing the DHCP?

SBS expects to do the DHCP and DNS for its domain, and all sorts of things go wrong if it doesn't provide those services.
Alex S.

I have been using this server for 5 years and have added many accounts. My UN has the appropriate permissions (I just added a desktop a month ago.)
Are you able to ping the FQDNs of the domain and the server from the laptop?
The server provides dhcp for the wireless portion of the network, but the desk tops are hardwired with an IP.

The DNS shows only the IP addresses, however, I hard wired them into the NIC?
Dave,

I can ping both the domain and the server by DNS name
Try joining the laptop using the wireless connection, as all the IP information will be supplied via DHCP from the server. Also, turn off the Windows firewall, just to eliminate it from the enquiry.
It couldn't hurt to check the Directory Service and File Replication Service event logs on the SBS server for anything that could indicate a problem with AD.
Returning here late, but responding to the post about wireless is very problematic for joining an SBS domain.  Too much info flows back and forth.  Try a wired connection and let us know.  BTW, the SBS is much happier with DHCP addresses being assigned to the stations, or rather I should say the stations are happier.  Once the stations/laptops are joined and all is stable, you shoud find wireless works ok.
Fly,

I normally join them via wired and then go onto to the wireless. I have had to hard wire the server in as the primary DNS as long as I have had this server (About 7 years).

Now all I get is a network error "See your network administrator. It then leaves an account called sbs_netset_up but the PW does not work.
I suggested using the wireless as a test of whether DHCP would resolve the problem, not as a modus operandi...
Per,

I understand, thanks. Tried and failed

The LT is seeing the server as the wizard states it has found an account with the laptop's name and asks whose user rights do I want to assign. When I select the user, it thinks for a bot and then gives me the error message above, leaving that account I mentioned as well.


Now all I get is a network error "See your network administrator. It then leaves an account called sbs_netset_up but the PW does not work.
I know it might sound crazy but try removing the machine from the Domain and change its name.

Reboot

If nothing changed on server check your in your laptop's Network Settings if your settings match the LAN Settings IP range, Mask... etc.

Try to join the computer again.

Good Luck!
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am a bit embarrassed that I did not think of the AV. Thanks to all that helped out.
Would be helpful to others, perhaps, if you gave details... usually this sort of thing is caused by "internet security" garbage, not AV itself.