unable to add computers to a server 2003 sbs domain

Hi all,

I have surfed the forums here, and checked around. I have found similar problems, and attempted to fix it from what I have read with very, very little luck so far.

My company recently purchased a Dell Power Edge 840 running server 2003 sbs. I am working on migrating to a domain, and did a few tests with two computers in the office a few weeks ago (one was my company laptop, the other is a contacting computer that is a community machine.)

I was able to get both of these computers on the domain using active directory. I added them into active directory after configuring the users for the domain. I was able to get both computers into the domain with no problem, and I can still sign into the domain and access the server with both of those computers.

However, now I am unable to add anymore computers to the domain. When I try to I get an error message.

"Active Directory Domain controller for the domain %domain name% could not be contacted

Ensure the domain name is typed correctly (this I have done I know it is right)

If the name is correct click details for troubleshooting info "

When I do this I find the error code "0x0000232b (Rcode_Name_Error) "

I looked it up and there is some strange DNS error occurring that was not happening when I initially started adding computers to the domain. My domain servers are hosted externally by my ISP. I am absolutely at a loss here, and I ended up looking into a Microsoft document that says to use something called the "configure your server Wizard." The best I can tell is that it doesn't exist in server 2003 sbs, and I have found some other forums that say the same thing, however I am still not sure.

I have tried switching the dns to 192.168.1.5 (on of the nic cards in the server.) It works fine for the server, but if I try to point one of the client computers to that DNS address I am unable to get anything, even local access. I switch it back to Obtain automatically, and I am able to get around the network, and out to the web, but still unable to put that computer into the work group.

I could really use some help here if anyone know what may be going on. I have used server 2003 before, but I have never had to configure a domain from the ground up completely by myself, and I just cannot seem to get passed this snag.

Thanks,
Jake

 

I made it one step further

I have made it one step further, I looks like the duel nic cards in the unit was causing the the client machines to not be able to connect to the domain, it probably couldn't identify which one to use.

However, now that I at least get a log in to authenticate a computer to the domain I get this error.

"The following error occurred attempting to join "domain name ":

An attempt to resolve the DNS name of a DC in the domain being joining has failed please has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. "


I have tried what I think is everything this could be. MY ISP domain (although I doubt this would be configured to resolve local domans.)

I have tried my router, which is what everything else looks at, and what I would think could be capable of resolving the local domain since it is a local piece of hardware dictating DNS as well as DHCP for the company.

Lastly, I have tried the server itself 192.168.1.5 This also doesn't work, which makes some sense, but was the last thing I had to try. I am still stuck, and when I set the client computer to obtain DNS info automatically that also does not work.

What am I doing wrong here? Any help would be greatly appreciated.

Thanks again,
Jake

 

I think you are making life hard for yourself by dual-hosting SBS. The simplest way to use SBS is with one NIC and let a decent firewall/router look after gateway security.

However, if you are using two NICs the first thing to check is that you are using different subnets on either side of the server. If the internal NIC is using 192.168.1.5 then the other NIC needs to be using a different subnet. A 10.0.0.0 address would make a lot of sense.

With the two NICs using different IP address and being on different subnets, you then need to make sure that the internal PCs have their DNS pointing at the IP address of the NIC closest to them.

 

Thanks for the help

Thanks for the Help ReggieB. I don't really know why I hadn't tried that before. Since looking back on it, the things you suggested make absolutely perfect sense.

I just set them up on different subnets, and since then everything has worked perfectly. Glad to know that people get back to me here. I will most definitely be using this forum in the future when I have any questions.

Thanks again,
Jake D.

 

Glad to have been of help and look forward to seeing more posts from you.