Can't add a PC to the network

I have a simple Windows 2003 Server setup.

I have a hub with an internet connection, a pc & a windows 2003 server on
it. This is a brand new install. I loaded the server with Windows Server
2003. I loaded AD. I put the server on domain.com. I added a
username/password. When I tru to add the usernam/domain name on the pc - new
user, it says that the new account cannot be added because the "Trust
relationship between the workstation and primary domain failed." I have
obviously forgetten a step somewhere - can anyone help me.

To note: When browsing Network places - Server can't see the pc and the pc
can't see the server.

In news:A683028A-FDB6-40F2-A3E2-(E-Mail Removed),
Diane <(E-Mail Removed)> stated, which I commented on below:
> I have a simple Windows 2003 Server setup.
>
> I have a hub with an internet connection, a pc & a windows 2003
> server on it. This is a brand new install. I loaded the server with
> Windows Server 2003. I loaded AD. I put the server on domain.com.
> I added a username/password. When I tru to add the usernam/domain
> name on the pc - new user, it says that the new account cannot be
> added because the "Trust relationship between the workstation and
> primary domain failed." I have obviously forgetten a step somewhere
> - can anyone help me.
>
> To note: When browsing Network places - Server can't see the pc and
> the pc can't see the server.

With AD, it's very important to ONLY use the DC as the DNS address in your
client machines, and the DC itself (point to itself) otherwise *numerous*
things will NOT work. Everytiong looking for an AD service queries DNS for
the service location. If you have the ISP's in there, it's asking the ISP's
DNS, "Where is the domain controller for my domain?", and that guy has no
idea. If the DC shows 127.0.0.1 and some other DNS (like your ISP's) in it's
IP properties, remove both and only show the actual IP of the DC. Configure
a forwarder for efficient internet resolution.

Also, make sure the SRV records show up in the zone. They are the _msdcs,
_udp, _tcp, _sites yellow folders.

Make sure the AD DNS domain name you created is NOT a single label name,
such as "DOMAIN" rather than the required format of 'domain.com'.

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003
(configure forwarding) :
http://support.microsoft.com/?id=323380

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/?id=825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default...b;en-us;291382

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile
Infinite Diversities in Infinite Combinations

"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy.