Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot add new computer to domain

Status
Not open for further replies.

jer18

IS-IT--Management
Feb 5, 2008
96
US
Hey,

It seems my DHCP is failing, there have been a lot of strange things going on. For one, I cannot join a computer to a domain either wireless or wired. Also, for those on the domain, I cannot find printers in the directory. I restarted the servers and dhcp. Any help would be great. Thanks.
 
IT would help if you'd provide some error messages...did you check your server log for errors?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Good evening,

I'd love to help you out with this issue, but I'll need more info. Let's start with your current environment. How many servers, clients, and what platform? Are you running Active Directory?

d|ano
 
I had just checked for errors in the log and I am certain there are none that relate. There two servers but dhcp, dns, active directory, are all on one. There are about 15 clients with both XP and Vista. Yes AD is running. Thanks.
 
You're not helping us help you.

When you try to join a computer to the domain, what error message do you get when it fails?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
All I am able to recommend with the info provide is to check your DHCP scope and DNS records. Be sure you can ping the ADC from all clients on the network. How many users do you have in AD? What account are you using to add computers to the domain? If you have only one god account, create a second and repeat the process. I can't offer more without an error message.Good luck.

d|ano
 
The error message came up during the install of XP. I was notified that it could not find myDomain.org that it was misspelled, unavailable, or otherwise unexisting.

I am unable to ping the AD server via name or IP. But interesting enough I can connect with RDC. Also, I was using the network admin account which had never failed me in the past.

Also on a side note, one computer is stating something about "comprimising security" when trying to open a network drive. Or others will prompt for a user name and password to connect. No matter what valid login is typed, I don't get through. Arg! Thank you much for responses!
 
DNS...check to see what IP the computer your trying to join to the domain is pulling and that you haven't given it a static IP address to a different subnet with the wrong DNS servers plugged in.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Not sure where to look.

I am currently under Forward Lookup Zones and the computer i attempted to connect isnt listed.. How can I tell what IP the computer is pulling?
 
If it were me? I'd go to the client computer and check it, not to the server...since it's not connecting to that server.

You may be in over your head. Have you checked into having a consultant come in and assist you?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
The IP I am assigned is an APIPA of 169.254.176.111 if i try to ipconfig/release I get timed out.
 
At this point, check you network connection. Begin by verifying you can connect to the network with another machine. If you are able to verify the network cable and jack are live and functioning properly, troubleshoot your nic card. Verify that you see lights and that traffic is passing to and from the nic. You should see a green or orange light blinking. Let me know what you discover.

How many switches and router are on your network? How many subnets? What are your subnets? For example, 192.168.1.1 - 192.168.1.254 is common. Do you have machines that have ip address outside of this range (besides the APIPA of 169.254.176.111)?

d|ano
 
There's your problem then, you have not received an IP address from your dhcp server. The XP client has automatically assigned itself an APIPA address.

Could be any number of reasons for this;

DHCP not running on the server
DHCP address pool is full
No active network connection on the client PC

APIPA -
Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein
 
This is the case for connecting multiple computers with working data cables and nic's. Unless I specify an IP address on the network card properties, it will obtain an APIPA of 169.254... When connected with static IP the NIC's activity light will flash and connect.
Our network setup is in the following order:
1.DSL
2.Netgear Firewall
3.Wireless Router(dhcp), Server1(dhcp,dns), Server2, Switch
4.Workstations(from patchpanel from switch)

The router assigns 192.168.1.100 - .254
The switch assigns 10.0.1.1 - .254

No machines are outside the range.

Paul, I double checked the DHCP server and it was running, but maybe not correctly. I also tried to restart it and all seems all right.
 
Jer18, be sure that the netgear firewall is not configured for dhcp.
 
its not. that would be hysterical. :)
 
There two servers but dhcp, dns, active directory, are all on one. "

Check the network card on this "one" server, and tell the results.
 
what happens if you give the XP computer a static ip can it connect to the domain then?

Regards
Max
 
What happens if you turn off the dhcp on the router.
are bothe the router and the server giving ip's in the same range and subnet.

Regards
Max
 
DTracy, hi, the network card is working fine. The server can access the file server and reach out to the internet.

Hi max, yes, only with a static Ip can i reach out to the network drives and internet.

The router was set to dchp Automatic configuration and had the IP 10.0.1.100. I did a dhcp release and renew to see if that would clear any issues. I am unable to renew, oops. I had to set it to static ip and gave it the ..1.100 ip back. Also DCHP was on and now I have turned it off. I'm changing some settings around at the moment.. I think we getting close for this to work
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top