Not sure if this is exactly and DNS issue but am stumped. Cannot view Entire Directory [WiredBox.Net

> First le me apologize if I'm in the wrong NG for this issue. However
> I also posted this in the windows server group and appraently it has
> also stumped the NG'ers as no one has posted a reply in 2 days. I got
> a perculiar issue that appears to be simple solution yet for the life
> of me I can't understand why. Here's my situation.
>
> I'm building 2 test servers and 1 workstation in a test environment
> to do some application installation testing. Both servers are W2K3
> SP1 servers. One is a DC running DNS and of course AD. The other
> server is the application server. Both are on the same internal
> private network 192.168.1.X with static IP's. The DC is RRAS enabled
> for internet access. All appears to be wroking. I can log onto the
> domain and I have internet access on all machines as well as access
> to domain resources such as shares. All servers and workstations can
> see and access each other. I can create shares on all machines and
> have bi lateral access to each. By default at the root of C:
> DOMAINNAME\Domain Admins have full access. Now here is the funny
> part. My only issue is that I need to create local groups on the app
> server and populate them with domain global groups. However after I
> create the local group and go to "add" members I cannot access the
> Entire Directory and see the DOMAIN. Same with when I try to apply
> ppermissions to a local folder on the app server. I do not see the
> Entire Directory and therefore cannot add Domain Groups or Users. All
> I see is the option to populate with local machine members. Any
> ideas?
> Thanks.

> Read inline please.
>
> In news:eP8BY$9lHHA.3952[ at ]TK2MSFTNGP03.phx.gbl,
> SBS W2K3 Admin <noreply[ at ]fakedomain.com> typed:
>> First le me apologize if I'm in the wrong NG for this issue. However
>> I also posted this in the windows server group and appraently it has
>> also stumped the NG'ers as no one has posted a reply in 2 days. I got
>> a perculiar issue that appears to be simple solution yet for the life
>> of me I can't understand why. Here's my situation.
>>
>> I'm building 2 test servers and 1 workstation in a test environment
>> to do some application installation testing. Both servers are W2K3
>> SP1 servers. One is a DC running DNS and of course AD. The other
>> server is the application server. Both are on the same internal
>> private network 192.168.1.X with static IP's. The DC is RRAS enabled
>> for internet access. All appears to be wroking. I can log onto the
>> domain and I have internet access on all machines as well as access
>> to domain resources such as shares. All servers and workstations can
>> see and access each other. I can create shares on all machines and
>> have bi lateral access to each. By default at the root of C:
>> DOMAINNAME\Domain Admins have full access. Now here is the funny
>> part. My only issue is that I need to create local groups on the app
>> server and populate them with domain global groups. However after I
>> create the local group and go to "add" members I cannot access the
>> Entire Directory and see the DOMAIN. Same with when I try to apply
>> ppermissions to a local folder on the app server. I do not see the
>> Entire Directory and therefore cannot add Domain Groups or Users. All
>> I see is the option to populate with local machine members. Any
>> ideas?
>> Thanks.
>
>
> Can you post the ipconfig /all from the member server and DC, and the
> results from
> nslookup gc._msdcs.<ADForestRoot> when ran from the member server?
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> Send IM: http://www.icq.com/people/webmsg.php?to=296095728
> ===================================
> 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 address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> 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
> ===================================
>
>

> C:\Documents and Settings\Administrator>nslookup
> gc._msdcs.sastest.local *** Can't find server name for address
> 192.168.1.2: Non-existent domain Server: UnKnown

> Read inline please.
>
> In news:enjIrh$lHHA.4768[ at ]TK2MSFTNGP05.phx.gbl,
> SBS W2K3 Admin <noreply[ at ]fakedomain.com> typed:
>
> Ok, I see several issues here, I'll go through them one by one.
>
>> C:\Documents and Settings\Administrator>nslookup
>> gc._msdcs.sastest.local *** Can't find server name for address
>> 192.168.1.2: Non-existent domain Server: UnKnown
>
> You can ignore this nslookup message or create a reverse lookup zone for
> your 192.168.1.x subnet.
>
>> Address: 192.168.1.2
>>
>> Name: gc._msdcs.sastest.local
>> Addresses: 192.168.1.2, 192.168.0.1, 67.100.73.190
>
> Here is the problem why the Entire Directory is not available, the only GC
> Address should be the SBS internal NIC IP, you will also find that there
> is
> a (same as parent folder) A record for these three addresses in the Root
> of
> your Domain name, too.
> You will need to completely stop these records from being registered and
> manually adding a host in the root of the domain name (sastest.local) and
> in
> gc._msdcs.sastest.local for the 192.168.1.2 address.
>
> Use regedt32 to add this then create the records noted.
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
> Registry value: DnsAvoidRegisterRecords
>
> Data type: REG_MULTI_SZ
> LdapIpAddress
> GcIpAddress
>
> Also, you need to right click on the DNS server in the DNS Management
> Console, select the Interfaces tab, and make sure it is set to listen only
> on 192.168.1.2
>
> After you do these things you need to bring up a cmd prompt and enter
> these
> commands.
> ipconfig /flushdns & ipconfig /registerdns
> net stop netlogon & net start netlogon
>
> This machine has no default gateway:
>
>> C:\Documents and Settings\Administrator>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : sastestclnt
>> Primary Dns Suffix . . . . . . . : SASTEST.local
> <snip>
>> IP Address. . . . . . . . . . . . : 192.168.1.5
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : <--------------No gateway
>
>
>
> While leaving the NIC disconnected inherently disables the NIC, you need
> to
> right click on the NIC and disable it when not connected.
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : sastestsvr
>> Primary Dns Suffix . . . . . . . : SASTEST.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : SASTEST.local
>>
>> Ethernet adapter Local Area Connection:
> <Snip>
>
>> Ethernet adapter Local Area Connection 2:<------Disable this NIC
>>
>> Media State . . . . . . . . . . . : Media disconnected
>> Description . . . . . . . . . . . : Intel(R) PRO/100+ Management
>> Adapter Physical Address. . . . . . . . . : 00-02-B3-03-1B-44
>
>
> You need to remove the Gateway from the internal NIC on your DC, you
> should
> have only one gateway, and it should point the way to the internet. While
> in
> your Network Connections Control Panel, in the Advanced Menu, select
> Advanced settings, move the internal NIC to the top of the Connections
> pane,
> and make sure File Sharing and Client for MS Networks is selected in the
> Bindings pane on the internal NIC.
>
>> C:\Documents and Settings\Administrator>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : sastestdc
>> Primary Dns Suffix . . . . . . . : SASTEST.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : SASTEST.local
>>
>> Ethernet adapter Wide Area Connection (WAN):
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
>> Connection
>> Physical Address. . . . . . . . . : 00-0E-0C-00-CE-6A
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 67.100.73.190
>> Subnet Mask . . . . . . . . . . . : 255.255.255.248
>> Default Gateway . . . . . . . . . : 67.100.73.185
>> DNS Servers . . . . . . . . . . . : 192.168.1.2
>>
>> Ethernet adapter Local Area Connection (LAN):
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel(R) PRO/100+ Management
>> Adapter Physical Address. . . . . . . . . : 00-D0-B7-75-F7-58
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.2
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.2<------------Remove
>> DNS Servers . . . . . . . . . . . : 192.168.1.2
>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> Send IM: http://www.icq.com/people/webmsg.php?to=296095728
> ===================================
> 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 address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> 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
> ===================================
>
>