I created a new forest called site.lan, single server, with server named
S3KOFFICE. The 2003 DCPROMO auto installed DNS and configured
everything, at least it appears to have. I setup DHCP, like I have a
zillion other times, and clients get the scope and the site.lan zone.

When I join a machine to site.lan it gives and error about DNS not
having a site.lan name. If I enter "site" it joins the domain properly.
Once the machine is in the SITE domain when I look at the network
settings the name is "computername.site.lan".

I can ping computername.site.lan and the server too. I can ping just the
workstation or server names without the site.lan part too.

DCDIAG says that the site.lan is not in the Active Directory, but it
says that the machines name "s3koffice.site.lan" is pingable by address
192.168.2.10......

Any ideas?

--
--
(E-Mail Removed)
(Remove 999 to reply to me)

So you created a new forest with a single root domain named site.lan.

When you did dcpromo you should have entered site.lan as the FQDN and
hopefully not just "site" which you may have when you were asked for the
netbios name. I don't even know if it will take a name without a period when
it aks for the full domain name - I have never tried it.

I would verify that the zone site.lan is indeed in your forward lookup zone
and that _srv records also exist in the zone - _msdcs, _sites, etc. I assume
you had the domain controller pointing to itself as it's preferred dns
server before dcpromo and that the workstations are pointing to it before
joining the domain. Running dcdiag may be helpful also looking for any
failed tests/warning/errors particularly about dns, domain membership, and
dclist. Also see if Event Viewer has any pertinent events that may help
troubleshoot. --- Steve



"Leythos" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I created a new forest called site.lan, single server, with server named
> S3KOFFICE. The 2003 DCPROMO auto installed DNS and configured
> everything, at least it appears to have. I setup DHCP, like I have a
> zillion other times, and clients get the scope and the site.lan zone.
>
> When I join a machine to site.lan it gives and error about DNS not
> having a site.lan name. If I enter "site" it joins the domain properly.
> Once the machine is in the SITE domain when I look at the network
> settings the name is "computername.site.lan".
>
> I can ping computername.site.lan and the server too. I can ping just the
> workstation or server names without the site.lan part too.
>
> DCDIAG says that the site.lan is not in the Active Directory, but it
> says that the machines name "s3koffice.site.lan" is pingable by address
> 192.168.2.10......
>
> Any ideas?
>
> --
> --
> (E-Mail Removed)
> (Remove 999 to reply to me)

In article <_blic.11146$0u6.1988856@attbi_s03>, (E-Mail Removed)
says...
> So you created a new forest with a single root domain named site.lan.
>
> When you did dcpromo you should have entered site.lan as the FQDN and
> hopefully not just "site" which you may have when you were asked for the
> netbios name. I don't even know if it will take a name without a period when
> it aks for the full domain name - I have never tried it.

No, I entered "site.lan" when I created the FQDN. It's when I go to a
workstation and add it to the domain that I have to enter "SITE" as the
domain since it gives an error when I enter "SITE.LAN".

> I would verify that the zone site.lan is indeed in your forward lookup zone
> and that _srv records also exist in the zone - _msdcs, _sites, etc. I assume

Yes, all the DNS configuration information is there, not even log
errors, and it appears to work.

> you had the domain controller pointing to itself as it's preferred dns
> server before dcpromo and that the workstations are pointing to it before
> joining the domain. Running dcdiag may be helpful also looking for any

No workstations were in the domain, none existed until the Server was
configured. The server was setup with a fixed IP of 192.168.2.10/24 and
a default gateway of the router 192.168.2.1 - no DNS entry. DCPROMO
added 127.0.0.1 to the DNS setting in the Network config. Once DHCP was
setup all workstations show a zone of "site.lan" and the DNS server as
192.168.2.10.

All workstations participate in the network as station.site.lan, users
are working, profiles roam, redirected folders work, etc...

The only DNS entry the workstations have is the IP of the server, the
server has forwarders for the ISP's DNS server configured in DNS. All
stations can reach all nodes, the server, and the internet by names
without any problem.

When I open REMOTE DESKTOP on any workstation to the server for remote
administration, it opens and the closes (by itself) as soon as the
server desktop appears - no errors, nothing. If I try a remote desktop
session from the server to the server the same thing happens - on my
other servers if I open a RD session to itself I just get a RD that
shows spawning images of RD (which I expect), not a good test, but it
lets me know that something is wrong with this server.

> failed tests/warning/errors particularly about dns, domain membership, and
> dclist. Also see if Event Viewer has any pertinent events that may help
> troubleshoot. --- Steve

I've setup about 40 single forest/domain 2003 servers in the last 4
months, not one of them has been a problem, this one came with the OS
pre-installed (but not configured) and is the only one that did. All the
others were on blank systems and I installed from scratch.

This one is just kicking my a$$.

If you have any other ideas I would appreciate hearing them.

Thanks,
Mark


>
>
>
> "Leythos" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I created a new forest called site.lan, single server, with server named
> > S3KOFFICE. The 2003 DCPROMO auto installed DNS and configured
> > everything, at least it appears to have. I setup DHCP, like I have a
> > zillion other times, and clients get the scope and the site.lan zone.
> >
> > When I join a machine to site.lan it gives and error about DNS not
> > having a site.lan name. If I enter "site" it joins the domain properly.
> > Once the machine is in the SITE domain when I look at the network
> > settings the name is "computername.site.lan".
> >
> > I can ping computername.site.lan and the server too. I can ping just the
> > workstation or server names without the site.lan part too.
> >
> > DCDIAG says that the site.lan is not in the Active Directory, but it
> > says that the machines name "s3koffice.site.lan" is pingable by address
> > 192.168.2.10......
> >
> > Any ideas?
> >
> > --
> > --
> > (E-Mail Removed)
> > (Remove 999 to reply to me)
>
>
>

--
--
(E-Mail Removed)
(Remove 999 to reply to me)

In news:(E-Mail Removed),
Leythos <(E-Mail Removed)> posted a question
Then Kevin replied below:
>> "Leythos" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> I created a new forest called site.lan, single server, with server
>>> named S3KOFFICE. The 2003 DCPROMO auto installed DNS and configured
>>> everything, at least it appears to have. I setup DHCP, like I have a
>>> zillion other times, and clients get the scope and the site.lan
>>> zone.
>>>
>>> When I join a machine to site.lan it gives and error about DNS not
>>> having a site.lan name. If I enter "site" it joins the domain
>>> properly. Once the machine is in the SITE domain when I look at the
>>> network settings the name is "computername.site.lan".
>>>
>>> I can ping computername.site.lan and the server too. I can ping
>>> just the workstation or server names without the site.lan part too.
>>>
>>> DCDIAG says that the site.lan is not in the Active Directory, but it
>>> says that the machines name "s3koffice.site.lan" is pingable by
>>> address 192.168.2.10......
>>>
>>> Any ideas?

Have you ran netdiag /fix?

Post the results from netdiag /test:dns /v and ipconfig /all from the DC.



--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

In article <(E-Mail Removed)>, (E-Mail Removed)
says...
> In news:(E-Mail Removed),
> Leythos <(E-Mail Removed)> posted a question
> Then Kevin replied below:
> >> "Leythos" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>> I created a new forest called site.lan, single server, with server
> >>> named S3KOFFICE. The 2003 DCPROMO auto installed DNS and configured
> >>> everything, at least it appears to have. I setup DHCP, like I have a
> >>> zillion other times, and clients get the scope and the site.lan
> >>> zone.
> >>>
> >>> When I join a machine to site.lan it gives and error about DNS not
> >>> having a site.lan name. If I enter "site" it joins the domain
> >>> properly. Once the machine is in the SITE domain when I look at the
> >>> network settings the name is "computername.site.lan".
> >>>
> >>> I can ping computername.site.lan and the server too. I can ping
> >>> just the workstation or server names without the site.lan part too.
> >>>
> >>> DCDIAG says that the site.lan is not in the Active Directory, but it
> >>> says that the machines name "s3koffice.site.lan" is pingable by
> >>> address 192.168.2.10......
> >>>
> >>> Any ideas?
>
> Have you ran netdiag /fix?
>
> Post the results from netdiag /test:dns /v and ipconfig /all from the DC.

Here is a result output from the DCDIAG, didn't do a NETDIAG yet.

Any help would be appreciated.

C:\Program Files\Resource Kit>dcdiag /fix
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\S3KADMOFFICE
Starting test: Connectivity
The host 51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan
could n
ot be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan)
couldn't be
resolved, the server name (S3KADMOFFICE.saylor.lan) resolved to
the IP
address (192.168.2.10) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... S3KADMOFFICE failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\S3KADMOFFICE
Skipping all tests, because server S3KADMOFFICE is
not responding to directory service requests
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test
CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test
CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test
CheckSDRefDom
Running partition tests on : saylor
Starting test: CrossRefValidation
......................... saylor passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... saylor passed test CheckSDRefDom
Running enterprise tests on : saylor.lan
Starting test: Intersite
......................... saylor.lan passed test Intersite
Starting test: FsmoCheck
......................... saylor.lan passed test FsmoCheck


--
--
(E-Mail Removed)
(Remove 999 to reply to me)

In news:(E-Mail Removed),
Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine

> Although the Guid DNS name
> (51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan)
> couldn't be
> resolved, the server name (S3KADMOFFICE.saylor.lan) resolved
> to the IP
> address (192.168.2.10) and was pingable. Check that the IP
> address is
> registered correctly with the DNS server.
> ......................... S3KADMOFFICE failed test


Does this GUID entry exist under the _msdcs zone?

51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan

That's what it's looking for.

Curious to see the netdiag results.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================

In article <OpL$(E-Mail Removed)>,
PleaseSubstituteMyActualFirstName&(E-Mail Removed) says...
> In news:(E-Mail Removed),
> Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine
>
> > Although the Guid DNS name
> > (51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan)
> > couldn't be
> > resolved, the server name (S3KADMOFFICE.saylor.lan) resolved
> > to the IP
> > address (192.168.2.10) and was pingable. Check that the IP
> > address is
> > registered correctly with the DNS server.
> > ......................... S3KADMOFFICE failed test
>
>
> Does this GUID entry exist under the _msdcs zone?
>
> 51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan
>
> That's what it's looking for.
>
> Curious to see the netdiag results.

I can't find the netdiag tool.

No the GUID it snot visible that I can see. Since 2003 auto-added DNS
and created the zones I can't imagine why it would leave that out. I
could put the GUID in myself, but I'm not sure that would be wise.

--
--
(E-Mail Removed)
(Remove 999 to reply to me)

In news:(E-Mail Removed),
Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine

>
> I can't find the netdiag tool.
>
> No the GUID it snot visible that I can see. Since 2003 auto-added DNS
> and created the zones I can't imagine why it would leave that out. I
> could put the GUID in myself, but I'm not sure that would be wise.
>
> --

Netdiag is found by installing the Windows Support Tools off the cdrom.

If W2k3 created it, there should be a separate zone called _msdcs. etc.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================

In article <(E-Mail Removed)>,
PleaseSubstituteMyActualFirstName&(E-Mail Removed) says...
> In news:(E-Mail Removed),
> Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine
>
> >
> > I can't find the netdiag tool.
> >
> > No the GUID it snot visible that I can see. Since 2003 auto-added DNS
> > and created the zones I can't imagine why it would leave that out. I
> > could put the GUID in myself, but I'm not sure that would be wise.
> >
> > --
>
> Netdiag is found by installing the Windows Support Tools off the cdrom.
>
> If W2k3 created it, there should be a separate zone called _msdcs. etc.

there is a zone with that name, same as on all my 2003 servers. The
problem indicates it's looking for:

51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan

I've demoted the server three times, even installed 2003 on top of
itself while it was demoted, and the problem continues. The only thing I
have not done is wipe/reinstall.


--
--
(E-Mail Removed)
(Remove 999 to reply to me)

In news:(E-Mail Removed),
Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine
> In article <(E-Mail Removed)>,
> PleaseSubstituteMyActualFirstName&(E-Mail Removed) says...
>> In news:(E-Mail Removed),
>> Leythos <(E-Mail Removed)> posted their thoughts, then I offered mine
>>
>>>
>>> I can't find the netdiag tool.
>>>
>>> No the GUID it snot visible that I can see. Since 2003 auto-added
>>> DNS and created the zones I can't imagine why it would leave that
>>> out. I could put the GUID in myself, but I'm not sure that would be
>>> wise.
>>>
>>> --
>>
>> Netdiag is found by installing the Windows Support Tools off the
>> cdrom.
>>
>> If W2k3 created it, there should be a separate zone called _msdcs.
>> etc.
>
> there is a zone with that name, same as on all my 2003 servers. The
> problem indicates it's looking for:
>
> 51ecea82-113e-4139-905b-323c1c1ca3bc._msdcs.saylor.lan
>
> I've demoted the server three times, even installed 2003 on top of
> itself while it was demoted, and the problem continues. The only
> thing I have not done is wipe/reinstall.
>
>
> --


See if this helps to re-create it:

817470 - HOW TO Reconfigure an _msdcs Subdomain to a Forest-wide DNS
Application Directory Partition When You Upgrade from Win:
http://support.microsoft.com/?id=817470



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================