Can not Log into Windows 2003 server
I am new in Server area but have quite few years experience in stand alone computer, like Win2000, Win Xp. I just setup a windows 2003 server. Also, install DNS, DHCP and Active Directory. Domain Name is " Kima.local ". I am trying to log in this Domain from a station and failed. The steps I tried are
(1). In System Properties I click "Change"
(2). In Computer Name Changes, I choose this is Member of a Domain and type my Domain name and click OK
(3). A new screen comes out to ask for a User Nmae and Password to get the permission to join a Domain.
(4). I type the user name and password which I already setup in the server.
(5). It took about 20 seconds to check then the "Computer Name Changes" windows shows " No Responding". About 2 minutes later, an error message comes out say " The Specified Server can not Perform the requested Operation"
Anybody can give me a clue?
Thanks.
(1). In System Properties I click "Change"
(2). In Computer Name Changes, I choose this is Member of a Domain and type my Domain name and click OK
(3). A new screen comes out to ask for a User Nmae and Password to get the permission to join a Domain.
(4). I type the user name and password which I already setup in the server.
(5). It took about 20 seconds to check then the "Computer Name Changes" windows shows " No Responding". About 2 minutes later, an error message comes out say " The Specified Server can not Perform the requested Operation"
Anybody can give me a clue?
Thanks.
jimbecher
You might have a couple things going on but lets start with one. When you try to join the workstation to the domain and it comes back and asks you for a username and password with rights to join the doman don't use the user you set up. Use Administrator (of the dom) and what ever password goes with that. First step is joining the computer to the domain. Reboot then you can log in as the users you set up on the domain.
you may want to run netdiag and dcdiag utilities on your 2003 server to make sure everything is in order
How are these system connected to each other?
What is the DNS of the XP/Vista system that you are trying to join to the domain?
What is the Servers DNS? (the server network adapter?)
Do you have any errors in the event log of the server itself?
Of the CLient istself?
YOu will need to type this for the username and password (when the box promopts you)
KIMA\administrator (assuiming KIMA is the domain name)
then your domain admin password
Robert
What is the DNS of the XP/Vista system that you are trying to join to the domain?
What is the Servers DNS? (the server network adapter?)
Do you have any errors in the event log of the server itself?
Of the CLient istself?
YOu will need to type this for the username and password (when the box promopts you)
KIMA\administrator (assuiming KIMA is the domain name)
then your domain admin password
Robert
Believe it or not, the administrator's user name and password doesn't always need to be used to join the domain. Up to 10 computers can be joined to an AD domain using a user account. I have NO IDEA WHY M$ allowed this.
The error you are seeing stems from the inability to either connect to the domain controller via DNS or Netbios. So, the best way to detect this issue is to go to the command prompt and provide us with an IPconfig /all of the client and an IPconfig /all of the server. Netdiag and DCdiag should show most errors of the configuration of the server. But, for someone novice in deciphering these errors it might be a bit difficult to pinpoint the issue. It's really best to see the issue first hand.
Most likely the preferred DNS server list was not correct under the DHCP scope options and your clients are going to the outside world for DNS resolution. Nowhere on the domain should you set an outside DNS server as your preferred DNS server except under the forwarders tab of DNS. You want all your clients and servers to point to your internal DNS server, and let the internal DNS server point to an outside server.
Also, you should make sure your ROUTER is not providing DHCP. The reason for this is the router will also try to provide DNS. The router does not store special DNS records, called SRV records (short for SeRVice records), that point the way to your authentication server (AD server).
I have an article I wrote on DNS that will help you pinpoint the DNS issues: (here it is)
http://beta.experts-exchange.com/articles/Networking/Protocols/DNS/DNS-TROUBLESHOOTING-MADE-EASY.html
The error you are seeing stems from the inability to either connect to the domain controller via DNS or Netbios. So, the best way to detect this issue is to go to the command prompt and provide us with an IPconfig /all of the client and an IPconfig /all of the server. Netdiag and DCdiag should show most errors of the configuration of the server. But, for someone novice in deciphering these errors it might be a bit difficult to pinpoint the issue. It's really best to see the issue first hand.
Most likely the preferred DNS server list was not correct under the DHCP scope options and your clients are going to the outside world for DNS resolution. Nowhere on the domain should you set an outside DNS server as your preferred DNS server except under the forwarders tab of DNS. You want all your clients and servers to point to your internal DNS server, and let the internal DNS server point to an outside server.
Also, you should make sure your ROUTER is not providing DHCP. The reason for this is the router will also try to provide DNS. The router does not store special DNS records, called SRV records (short for SeRVice records), that point the way to your authentication server (AD server).
I have an article I wrote on DNS that will help you pinpoint the DNS issues: (here it is)
http://beta.experts-exchange.com/articles/Networking/Protocols/DNS/DNS-TROUBLESHOOTING-MADE-EASY.html
ASKER
Hi ChiefIT:
I tried. still not work. I think I better explain my hardware setup to give you a better picture. I have a server directly connect to Netgear WiFi router. A client PC connect to this WiFi router by wireless. For my server, I uninstall DHCP role. So I am using Netgear router as a DHCP provider. Right now I only have DNS and Active Direct installed. You are right about DNS and I am confusing the role of DNS, Active Directly. I think my client did not point to internal DNS but ISP DNS. So, How could I setup the client to point to internal DNS and still can browse Internet. Also, How could I just copy the IPconfig /all from my client and server computer to you. Sorry, I am an entryT lever of Server system, Please bear with me. Thanks
I tried. still not work. I think I better explain my hardware setup to give you a better picture. I have a server directly connect to Netgear WiFi router. A client PC connect to this WiFi router by wireless. For my server, I uninstall DHCP role. So I am using Netgear router as a DHCP provider. Right now I only have DNS and Active Direct installed. You are right about DNS and I am confusing the role of DNS, Active Directly. I think my client did not point to internal DNS but ISP DNS. So, How could I setup the client to point to internal DNS and still can browse Internet. Also, How could I just copy the IPconfig /all from my client and server computer to you. Sorry, I am an entryT lever of Server system, Please bear with me. Thanks
That is a definite problem. The server needs to be the DNS that the workstations are pointed to otherwise they won't be able to find the domian. As long as you are taking the time to do this you should do it properly. The server should ne the DNS, DHCP and WINS. Shut the DHCP off on the wireless router. Should be absolutely nothing but the gateway. All of the workstations should get their IP addresses from the server and the DNS and WINS on the workstations should point to the server. All the gateway addresses (server and workstations) should be the IP address of the router. The DNS address on the server should point to itself. When you set up the DNS on the server use forwarders to point to your ISP's DNS servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.