Win 2003 Domain Issue

Hi,

We have a DC with AD. We have native domain(SATS-AU)
chatswood.satsapac.com(192.168.1.150), name of DC is sats-
server. This was installed on the network first and
currently serves all XP clients with internet access etc
with no issues. We use NAT on our network to get our on
the net. IP of the router is (192.168.1.2)Our company is
changing its name from SATS to MVSS.

We purchased a new server and configured it as a DC and
created a new domain(MVSS) mvss.com(192.168.1.11)(root)
with AD. The name of the server is mvss-server. We need
all clients to be added to this domain. We plugged it into
the network and it got its IP automatically(192.168.1.11).
Its DNS server is (192.168.1.150) which is sats-server,
the other DC. I want to start adding the client computers
to this domain but am having trouble.

From the XP client(192.168.1.17) I can ping
(192.168.1.150) and add it to the existing domain(SATS-AU)
with no dramas.

From 192.168.1.11(mvss-server) I can ping the client
192.168.1.17(client)
From 192.168.1.11(mvss-server) I can ping sats-server
192.168.1.150(sats-server)

However from 192.168.1.17(client) I cannot ping
192.168.1.11 and cannot add the computer to the domain. I
got the error saying the client could not locate mvss-
server when trying to add it to the domain. I created a
new computer in AD and a domain user account.

The error reads could not loacate mvss.com root domain. Is
this because I need to add a DNS entry (SRV) record on
sats-server? OR Does mvss-server need to be configured as
its own DNS server? Do I manually need to authorise the
mvss-server?

The mvss-server seems to be blocking all incoming
communications and there is no firewall setup on the
server yet.

Any help would be appreciated.

Steve Sutic

First ..Get the Firewall up! You don't need viri or trojan issues while
trying out a new server. Second: The issue does appear to be DNS related
taking into consideration the network configuration you described. In order
to join an AD Domain the workstation will need to use the servers DNS
address (you can join without it, but it's painful).
Eric

"Steve Sutic" <(E-Mail Removed)> wrote in message
news:df7201c3bb7c$a4398e00$(E-Mail Removed)...
> Hi,
>
> We have a DC with AD. We have native domain(SATS-AU)
> chatswood.satsapac.com(192.168.1.150), name of DC is sats-
> server. This was installed on the network first and
> currently serves all XP clients with internet access etc
> with no issues. We use NAT on our network to get our on
> the net. IP of the router is (192.168.1.2)Our company is
> changing its name from SATS to MVSS.
>
> We purchased a new server and configured it as a DC and
> created a new domain(MVSS) mvss.com(192.168.1.11)(root)
> with AD. The name of the server is mvss-server. We need
> all clients to be added to this domain. We plugged it into
> the network and it got its IP automatically(192.168.1.11).
> Its DNS server is (192.168.1.150) which is sats-server,
> the other DC. I want to start adding the client computers
> to this domain but am having trouble.
>
> From the XP client(192.168.1.17) I can ping
> (192.168.1.150) and add it to the existing domain(SATS-AU)
> with no dramas.
>
> From 192.168.1.11(mvss-server) I can ping the client
> 192.168.1.17(client)
> From 192.168.1.11(mvss-server) I can ping sats-server
> 192.168.1.150(sats-server)
>
> However from 192.168.1.17(client) I cannot ping
> 192.168.1.11 and cannot add the computer to the domain. I
> got the error saying the client could not locate mvss-
> server when trying to add it to the domain. I created a
> new computer in AD and a domain user account.
>
> The error reads could not loacate mvss.com root domain. Is
> this because I need to add a DNS entry (SRV) record on
> sats-server? OR Does mvss-server need to be configured as
> its own DNS server? Do I manually need to authorise the
> mvss-server?
>
> The mvss-server seems to be blocking all incoming
> communications and there is no firewall setup on the
> server yet.
>
> Any help would be appreciated.
>
> Steve Sutic
>