Setup for unexposed-to-internet domain.

Hello ..!

On my network, I have three Windows 2003 Server and one Windows 2000 Server
which runs different services (MS SQL, Lotus Notes, Sybase SQL, etc)... I am
using no domain for them... they are just part of a workgroup.

Now, I would like to create a Domain, convert one of my W2003 Servers to be
a PDC for such Domain, and get the other three Win Servers into the new
Domain.

While I'm giving access to my users to the internet, I'm doing so using a
separate router and firewall solution... that means no Server is involved on
delivering Internet Services to any one... and I would like to keep that as
it is.

I have no Services been given to anyone outside the company, so I will not
have any name for my Win Servers published to the Internet, and no one of
those Servers will have a public IP address.

How can I setup that? I did some things, but I found several 'warning'
system events on my event log... I list them at the end.

Thank you for your help.

================================================
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11165
Date: 8/1/2006
Time: 8:40:42 AM
User: N/A
Computer: SLWMXWIN4
Description:
The system failed to register host (A) resource records (RRs) for network
adapter
with settings:

Adapter Name : {4ECB1A7A-4D4D-4D58-B413-EEEADB24685A}
Host Name : slwmxwin4
Primary Domain Suffix : Domain.SlwMx
DNS server list :
192.168.1.25
Sent update to server : <?>
IP Address(es) :
192.168.4.5

The reason the system could not register these RRs was because the DNS
server contacted refused the update request. The reasons for this might be
(a) you are not allowed to update the specified DNS domain name, or (b)
because the DNS server authoritative for this name does not support the DNS
dynamic update protocol.

To register the DNS host (A) resource records using the specific DNS domain
name and IP addresses for this adapter, contact your DNS server or network
systems administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..
================================================
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/1/2006
Time: 8:45:23 AM
User: N/A
Computer: SLWMXWIN4
Description:
Dynamic registration or deletion of one or more DNS records associated with
DNS domain 'Domain.SlwMx.' failed. These records are used by other
computers to locate this server as a domain controller (if the specified
domain is an Active Directory domain) or as an LDAP server (if the specified
domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate registration
or deletion of the DNS records by running 'nltest.exe /dsregdns' from the
command prompt or by restarting Net Logon service. Nltest.exe is available
in the Microsoft Windows Server Resource Kit CD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..
================================================
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/1/2006
Time: 8:45:40 AM
User: N/A
Computer: SLWMXWIN4
Description:
Dynamic registration or deletion of one or more DNS records associated with
DNS domain 'DomainDnsZones.Domain.SlwMx.' failed. These records are used by
other computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server (if the
specified domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate registration
or deletion of the DNS records by running 'nltest.exe /dsregdns' from the
command prompt or by restarting Net Logon service. Nltest.exe is available
in the Microsoft Windows Server Resource Kit CD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..
================================================
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/1/2006
Time: 8:45:41 AM
User: N/A
Computer: SLWMXWIN4
Description:
Dynamic registration or deletion of one or more DNS records associated with
DNS domain 'ForestDnsZones.Domain.SlwMx.' failed. These records are used by
other computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server (if the
specified domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate registration
or deletion of the DNS records by running 'nltest.exe /dsregdns' from the
command prompt or by restarting Net Logon service. Nltest.exe is available
in the Microsoft Windows Server Resource Kit CD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..
================================================
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/1/2006
Time: 8:45:41 AM
User: N/A
Computer: SLWMXWIN4
Description:
Dynamic registration or deletion of one or more DNS records associated with
DNS domain 'TAPI3Directory.Domain.SlwMx.' failed. These records are used by
other computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server (if the
specified domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate registration
or deletion of the DNS records by running 'nltest.exe /dsregdns' from the
command prompt or by restarting Net Logon service. Nltest.exe is available
in the Microsoft Windows Server Resource Kit CD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..





.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)