Link to home
Start Free TrialLog in
Avatar of pat_the_bat
pat_the_bat

asked on

Microsoft Server 2003- can't ping domain controller

I've just installed server 2003. I am trying to add a computer to the domain. I went through the steps of adding a user and adding a computer on the server. On the client machine- I right click on my computer, properties, computer name, then I click on change (to change computer name or join a domain.) where it says member of, I entered my domain name.... newserver.local. Then it gives me error message  A domain Controller for the domain Newserver.local could not be contacted.

So before I moved forward I pinged both machines to make sure there was no network issue. Client is able to ping server successfully. Server cannot ping the client. From the admin screen of the router I can see both nodes recognized and both have ip addresses. Server is able to access the www.

I'm stuck. Can someone please help!!!
ASKER CERTIFIED SOLUTION
Avatar of Henrik Johansson
Henrik Johansson
Flag of Sweden 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 pat_the_bat
pat_the_bat

ASKER

Turned off firewall. That made it so my client machine could join the domain. Then when I go to the Windows logon screen and I choose to login to the domain instead of the local computer, I get "Logon Message     The system cannot log you on now because the domain is not available"
I am guessing there is something wrong with dns settings but unfortunately I am too much of a rookie to understand what it is. Appreciate some more direction.

Also, what is the ettiquette here? The answer henjoh09 gave me did in fact solve the problem I posted, so I feel like I should accept as solution so he/she gets awarded those points, but I wanted to get more direction in the context of this correspondence. Should I make this a new post so that a new set of points would be awarded for the new problem that this solution uncovered? Please advise.
If primary question has been answered/solved, the question should be closed to keep the thread clean from spinoff questions. Better to ask a new question, but you can link the questions together by using 'related question' feature after first question has been closed.

As I posted above, you nead to check the DNS settings with ipconfig/all command on the client that you don't use any external DNS servers listed that can't resolve the internal namespace. Configure client through either local TCP/IP properties or centralized DHCP options (can also be done with GPO) what DNS servers shall be used.
I set dns server as 192.168.1.2, which is the address of the server. Left alternate dns blank. Still get the logon message system cannot log you on now because the domain is not available.

When I set the dns server to 192.168.1.2 it allowed me to change the computer name/workgroup to join the domain, so it resolves that issue, but it does not resolve the issue of the windows logon message saying the domain is not available.

Also, when I am logged on to the client as the local machine, I cannot access any internet pages unless I change the dns server back to 192.168.1.1 (the router) which I am assuming is normal. Thought I would add to post in case that is relevant though.