Vista - Vista Cannot Connect to Server 2003 Domain

I'm currently trying to connect my laptop which has Vista Business 32-bit to my Poweredge T105 which is running Server 2003 RC2. I get this error when running Network ID:

"Your computer could not be joined to the domain because the following
error occured:
An attempt to resolve the DNS name of a DC in the domain being joined has
failed. Please verify this client is configured to reach a DNS server that
can resolve DNS names in the target domain."

The domain name I'm using is a live domain and worked fine when I connected my XP desktop to it. Not sure why it won't connect. Although it is on a different network (name) it can see the shared folder on the server.

Any ideas?

"Breakingcustom" <Breakingcustom.379l21@xxxxxx-mx.forums.net> wrote in message
news:Breakingcustom.379l21@xxxxxx-mx.forums.net...
That is usually caused by exactly what the error message says, a problem
with DNS. Can you post the results of IPCONFIG /ALL from the Vista computer
and the domain controller? This will tell us if it's a DNS problem. It could
also be a firewall problem.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/

Right now the router is the DHCP server. All I have enabled as roles on Server 2003 is Domain Controller, File Server, and Application Server. Firewall is disabled in 2003. Like I said the domain name is actually a registered domain that I own. Would it be better if I did something different?

This is from the server with 03 RC2:

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : breakingcustom.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : breakingcustom.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1D-09-30-08-35
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
Lease Obtained. . . . . . . . . . : Thursday, April 03, 2008 6:12:08 AM
Lease Expires . . . . . . . . . . : Friday, April 04, 2008 6:12:08 AM

This is from the Vista machine:

Windows IP Configuration

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

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
nection
Physical Address. . . . . . . . . : 00-1C-BF-8F-6D-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8101E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1E-68-18-BD-A8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2caa:248:d397:1719%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, April 02, 2008 7:37:53 PM
Lease Expires . . . . . . . . . . : Friday, April 04, 2008 7:37:52 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
Primary WINS Server . . . . . . . : 192.168.1.104
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{892DDE9C-E846-4427-B922-30A210BFC
A2F}
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 . . . . . . . . . . . : isatap.{DCBB2F25-81B4-43D2-A454-A8255BB40
9D9}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 14:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:20b7:1fcf:3f57:fe98(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::20b7:1fcf:3f57:fe98%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

You probably don't want to use your public domain name for your internal
network. For active directory to work properly the domain controller should
be the DNS server. If the internal domain name is the same as your external
public domain there are some special things you have to do for internal
clients to access your external web site. Normally you would use something
like breakingcustom.lan for your internal domain name. The internal DNS
server resolves the internal network and should be set to forward external
requests to your ISP's DNS servers.

Right now you are using your ISP's DNS servers for the client PC. This is
why you get that error. Your ISP's DBS servers have no idea where your DC
is. In an active directory domain the clients should only be using an active
directory integrated DNS server. Explaining how to set up active directory
is beyond the scope of a newsgroup. It sounds like it would be easier at
this point to start again from scratch. With a single domain controller in a
small network it is easiest if the domain controller is the only DNS server,
the DHCP server, and the WINS server. Turn off DHCP on the router.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/



"Breakingcustom" <Breakingcustom.37avl1@xxxxxx-mx.forums.net> wrote in message
news:Breakingcustom.37avl1@xxxxxx-mx.forums.net...

Ok, DHCP is disabled on the router. I removed the role of DC and re-added. The domain name is now breakingcustom.lan.

I also instead DHCP server and WINS server. In the DHCP server I had to scope run from 192.168.1.100 to 150. Followed the wizard and resolve my Server IP for DNS and WINS. Also told it the IP that was my router.

When I go to IP config it shows 127.0.0.1 instead of my ISP DNS. I just added the DNS server role and had it forward to the DNS servers for my ISP. Now the internet works on the server computer.

I'm having trouble though getting the laptop to connect still. When I go through the Network ID wizard and I put in BREAKINGCUSTOM.LAN as my domain it says "An Active Directory Domain Controller for the domain BREAKINGCUSTOM.LAN could not be contacted.

I even put the 127.0.0.1 as my DNS server and still nothing.

"Breakingcustom" <Breakingcustom.37crn0@xxxxxx-mx.forums.net> wrote in message
news:Breakingcustom.37crn0@xxxxxx-mx.forums.net...
You missed the results of ipconfig /all

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/

Here is everything from each computer:

Windows XP (able to connect to the domain), also in the TCP/IP settings everything is set at Automatically obtain address.

Windows IP Configuration

Host Name . . . . . . . . . . . . : conlan-pc
Primary Dns Suffix . . . . . . . : breakingcustom.lan
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : breakingcustom.lan

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-15-F2-05-AB-3C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
Lease Obtained. . . . . . . . . . : Friday, April 04, 2008 7:23:42 AM
Lease Expires . . . . . . . . . . : Saturday, April 05, 2008 7:23:42 AM

Vista (not able to connect) although if I put in 192.168.1.102 and for DNS 127.0.0.1 and a DNS IP for my ISP it will connect to the internet. If not, it won't.

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

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
nection
Physical Address. . . . . . . . . : 00-1C-BF-8F-6D-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8101E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1E-68-18-BD-A8
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2caa:248:d397:1719%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
204.127.203.135
216.148.225.135
Primary WINS Server . . . . . . . : 192.168.1.104
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{892DDE9C-E846-4427-B922-30A210BFC
A2F}
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 . . . . . . . . . . . : isatap.{DCBB2F25-81B4-43D2-A454-A8255BB40
9D9}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 14:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:2cfa:3b0c:3f57:fe99(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::2cfa:3b0c:3f57:fe99%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Server 2003 RC2

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SERVER>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : breakingcustom.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : breakingcustom.lan

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1D-09-30-08-35
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1

It looks like you are still using the router for DHCP. Turn off DHCP on the
router. Turn it on on the server. Set the server to use it's own IP address
rather than 127.0.0.1 for DNS. Set the DHCP options so that clients use the
server for DNS and WINS and the router as the gateway. XP will use NETBIOS
to find domain resources but it is very inefficient. Vista will not do this.
Setting up DNS properly is the key to running active directory. The XP
computer will work much better with DNS working properly.

I highly recommend you do some reading on setting up active directory.

http://www.petri.co.il/how_to_instal...ndows_2003.htm

http://www.microsoft.com/technet/pro...p/default.mspx



--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/

DHCP is disabled on the router. So I can use 192.168.1.104 as the DNS server or just make up something?

"Breakingcustom" <Breakingcustom.37dm77@xxxxxx-mx.forums.net> wrote in message
news:Breakingcustom.37dm77@xxxxxx-mx.forums.net...
The XP computer is using the router for DHCP.

DHCP SERVER . . . . . . . . . . . : 192.168.1.1

All of the computers on the network, including the XP computer and the
domain controller itself, need to be using the domain controller
(192.168.1.104) for DNS resolution.


--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/