Server 2003 Client

darrinlewis441

New Member
Reaction score
0
Location
Council Bluffs, IA
Hello Everyone!
I recently converted my older computer in to a server. I was able to obtain Windows Server 2003 Enterprise edition for a very affordable price though my college. I have my active directory set-up and working. I am having trouble adding the family's Vista PC on my domain. It does have Vista Business installed. I get a DNS error. I will attach the screen shots. I don't understand why because my Windows XP Pro desktop added the domain just fine. My domain is named LEWIS. My family can log in and out just fine on the XP machine.
I want to add the Vista PC to the server because we want to share files, and printers, and I want to be able to "control" the computers.

Thanks in advance,
Darrin
 

Attachments

  • DNS-Error-box.jpg
    DNS-Error-box.jpg
    58.5 KB · Views: 84
  • DNS-Error.jpg
    DNS-Error.jpg
    62.8 KB · Views: 77
Seems as though the DNS server configured for Vista doesn't know how to access the domain. Vista box using external DNS server maybe? Please post the result of 'ipconfig /all' for both the XP and Vista box.
 
Seems as though the DNS server configured for Vista doesn't know how to access the domain. Vista box using external DNS server maybe? Please post the result of 'ipconfig /all' for both the XP and Vista box.


Here is the ipconfig /all for the XP.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\family.LEWIS>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : basement
Primary Dns Suffix . . . . . . . : lewis.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lewis.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont
roller
Physical Address. . . . . . . . . : 00-08-74-BF-36-A9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, October 20, 2009 11:45:46 A
M
Lease Expires . . . . . . . . . . : Wednesday, October 21, 2009 11:45:46
AM

C:\Documents and Settings\family.LEWIS>

Vista's ---

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Family-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-16-76-65-AD-DF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, October 16, 2009 11:42:02 AM
Lease Expires . . . . . . . . . . : Wednesday, October 21, 2009 11:42:03 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{F27FB985-7549-48C7-978C-7AC2D5DE3
E91}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>
 
Last edited:
If I remember correctly, you have to change the DNS server on the client computer to the IP address of the domain controller.

I just tried this and It didn't do the trick. My Server has two ip addresses because I put in two network cards. They are 192.168.1.8 (that is set to auto) and 192.168.1.55 (manual) I didn't know if you needed that or not.
 
Is 192.168.1.1 some sort of router with DNS and DHCP running? Also, from both XP and Vista machines, can you ping the name of the server?

192.168.1.1 is the wired and wireless router in my house it is a Netgear. I can ping the server from Vista. The server is named DELLSERVER. All my computers are connected though this router. I should mention that the server, Vista and the XP computers are wired. According to the router settings it says DHCP is on. This is my only router in my house, and is directly connected to my internet modem. Here is the ping results from Vista.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Family>ping dellserver

Pinging dellserver [192.168.1.8] with 32 bytes of data:
Reply from 192.168.1.8: bytes=32 time=1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128
Reply from 192.168.1.8: bytes=32 time=1ms TTL=128
Reply from 192.168.1.8: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\Family>
 
I googled the error you were getting and according to this article, it seems the issue could be caused by a firewall on the Win 2k3 server. I've never seen that be an issue but I guess its something you can try. If the firewall is even turned on, turn it off and attempt to join the domain again.
 
1) If you're going to have a server behind a firewall/router, it only needs to have 1 NIC. If it is going to be acting as the firewall/router then it needs 2 NICs.
2) If you have DHCP running on your router, turn it off and start it in the server.
3) Turn on your DNS services on the router.
4) Be certain that your server is providing its own address as the DNS server through DHCP.
5) Try again.
 
Assuming the DC is running DNS.

Yea, I assumed because normally I set it up just like TimeCode metioned. I thought it was like "common practice" to do so.

1) If you're going to have a server behind a firewall/router, it only needs to have 1 NIC. If it is going to be acting as the firewall/router then it needs 2 NICs.
2) If you have DHCP running on your router, turn it off and start it in the server.
3) Turn on your DNS services on the router.
4) Be certain that your server is providing its own address as the DNS server through DHCP.
5) Try again.
 
I am by far no server expert, but I have got my hands dirty a bit with domains, active directory, terminal servers, and some other bits.

The way I was taught the domain controller is always setup as the DNS server. I remember I actually had one case where I forgot to do so and it created a mess, very similar to this one.
 
1) If you're going to have a server behind a firewall/router, it only needs to have 1 NIC. If it is going to be acting as the firewall/router then it needs 2 NICs.
2) If you have DHCP running on your router, turn it off and start it in the server.
3) Turn on your DNS services on the router.
4) Be certain that your server is providing its own address as the DNS server through DHCP.
5) Try again.


I am not sure I want to turn DCHP off on my router. If I do that won't it put my server "out in the world?" When my router was down once I had my computer directly connected and I could see the neighbors computer on the network. It was almost like we were all on the same router. DNS is running on the router is set to get automatically from ISP. I will remove the second NIC card and set the first one to automatically obtain an IP from the router.
 
I can get to the point in Vista where I can enter the Administrator password for the server to join the domain and then that is when I get the DNS error. I have tried changing the IP and the DNS and it still does not work. Do I need to buy the update to Server 2008? Would this help? I have several stuff on the server that I want to deploy out to the Vista box.
 
Last edited:
I am not sure I want to turn DCHP off on my router. If I do that won't it put my server "out in the world?" When my router was down once I had my computer directly connected and I could see the neighbors computer on the network. It was almost like we were all on the same router. DNS is running on the router is set to get automatically from ISP. I will remove the second NIC card and set the first one to automatically obtain an IP from the router.

Turning off DHCP on your router simply means that the router would no longer be assigining IP address's automatically. It would not open you to the world. You also cannot set the server to automatically get an IP address from the router if you are going to make it the DNS server. It would need a static IP so that you can specify on the clients computer where the DNS server is.

Honestly, I think your best bet here is to demote the server and then follow this guide for setting up the domain. I pretty much setup domain controllers along this very same lines. This guide has a step by step explanation, and even includes pictures. Give it a try, should only take you 10 minutes to do.

Link
 
It is now Connected! I had to change the DNS.. I know you told me to do this ProTech Support but I must have done something wrong the first time. Anyway Thank you guys for sticking with me and helping me though it! I was getting very frustrated over this ordeal! I am soooo happy now!

Thanks again!
Darrin
 
It is now Connected! I had to change the DNS.. I know you told me to do this ProTech Support but I must have done something wrong the first time. Anyway Thank you guys for sticking with me and helping me though it! I was getting very frustrated over this ordeal! I am soooo happy now!

Thanks again!
Darrin

Glad to hear it, it's a good feeling huh? Server troubleshooting always sucks.

Anyway, still take a look at the guide I posted and save it for future reference. I am sure this won't be your last server project!
 
Back
Top