Re: Logon script not running
- From: Meinolf Weber
- Date: Mon, 10 Dec 2007 15:46:53 +0000 (UTC)
Hello Mike,
Ok, but this configuration cause your problems. Here is an article why NOT multihome DC's from another posting:
Multihomed DCs, DNS, RRAS servers.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Below are the manual steps in more detail, which I had outlined in the above paragraph:
Honestly, multi-homed DCs are not recommended because of the associated issues that can occur, as you've encountered. We usually recommend purchasing an inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you, take out the extra NIC off the DC, but still let the DC handle DHCP (and not the router).
Little background on AD and DNS:
First, just to get this out of the way, if you have your ISP's DNS addresses in your IP configuration (DCs and clients), they need to be REMOVED.
If the ISP's DNS is in there, this will cause additional problems.
Also, AD registers certain records in DNS in the form of SRV records that signify AD's resource and service locations. When there are multiple NICs, each NIC registers. IF a client, or another DC queries DNS for this DC, it may get the wrong record. One factor controlling this is Round Robin. If a DC or client on another subnet that the DC is not configured on queries for it, Round Robin will kick in offering one or the other. If the wrong one gets offered, it may not have a route to it. On the other hand, Subnetmask Priortization will ensure a querying client will get an IP that corresponds to the subnet it's on, which will work. To insure everything works, stick with one NIC.
Since this DC is multi-homed, it requires additional configuration to prevent the public interface addresses from being registered in DNS. This creates a problem for internal clients locating AD to authenticate and find other services and resources such as the Global Catalog, file sharing and the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be logged, authenticating to shares and printers, logging on takes forever, among numerous other issues.
But if you like, there are some registry changes to eliminate the registration of the external NIC. Here's the whole list of manual steps to follow.
But believe me, it's much easier to just get a separate NAT device or multihome a non-DC then having to alter the DC. - Good luck!
1. Insure that all the NICS only point to your internal DNS server(s) only and none others, such as your ISP's DNS servers' IP addresses.
2. In Network & Dialup properties, Advanced Menu item, Advanced Settings, move the internal NIC (the network that AD is on) to the top of the binding order (top of the list).
3. Disable the ability for the outer NIC to register. The procedure, as mentioned, involves identifying the outer NIC's GUID number. This link will show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per NIC too):
http://support.microsoft.com/?id=246804
4. Disable NetBIOS on the outside NIC. That is performed by choosing to disable NetBIOS in IP Properties, Advanced, and you will find that under the "WINS" tab. You may want to look at step #3 in the article to show you how to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface [Registry Entry]:
http://support.microsoft.com/?id=296379
Note: A standard Windows service, called the "Browser service", provides the list of machines, workgroup and domain names that you see in "My Network Places" (or the legacy term "Network Neighborhood"). The Browser service relies on the NetBIOS service. One major requirement of NetBIOS service is a machine can only have one name to one IP address. It's sort of a fingerprint. You can't have two brothers named Darrell. A multihomed machine will cause duplicate name errors on itself because Windows sees itself with the same name in the Browse List (My Network Places), but with different IPs. You can only have one, hence the error generated.
5. Disable the "File and Print Service" and disable the "MS Client Service" on the outer NIC. That is done in NIC properties by unchecking the respective service under the general properties page. If you need these services on the outside NIC (which is unlikely), which allow other machines to connect to your machine for accessing resource on your machine (shared folders, printers, etc.), then you will probably need to keep them enabled.
6. Uncheck "Register this connection" under IP properties, Advanced settings, "DNS" tab.
7. Delete the outer NIC IP address, disable Netlogon registration, and manually create the required records
a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's IP references for the "LdapIpAddress". If this is a GC, you will need to delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS console, under the zone name, you will see the _msdcs folder. Under that, you will see the _gc folder. To the right, you will see the IP address referencing the GC address. That is called the GcIpAddress. Delete the IP addresses referencing the outer NIC.
i. To stop these two records from registering that information, use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in DNShttp://support.microsoft.com/?id=295328
ii. The one section of the article that disables these records is done with this registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress
iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp
b. Then you will need to manually create these two records in DNS with the IP addresses that you need for the DC. To create the
LdapIpAddress, create a new host under the domain, but leave the "hostname" field blank, and provide the internal IP of the DC, which results in a record that looks like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative purposes)
i. You need to also manually create the GcIpAddress as well, if this is a GC. That would be under the _msdcs._gc SRV record under the zone. It is created in the same fashion as the LdapIpAddress mentioned above.
8. In the DNS console, right click the server name, choose properties, then under the "Interfaces" tab, force it only to listen to the internal NIC's IP address, and not the IP address of the outer NIC.
9. Since this is also a DNS server, the IPs from all NICs will register, even if you tell it not to in the NIC properties. See this to show you how to stop that behavior (this procedure is for Windows 2000, but will also work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to Register the Connection's Address:
http://support.microsoft.com/?id=275554
10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if not sure which DNS to forward to until you've got the DNS address of your ISP.
How to set a forwarder? Good question. Depending on your operating system,choose one of the following articles:
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1
323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003 (How to configure a forwarder):
http://support.microsoft.com/d/id?=323380
Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294
<==*** Some additional reading ***==>
More links to read up and understand what is going on:
292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822
Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294
246804 - How to enable or disable DNS updates in Windows 2000 and in Windows Server 2003
http://support.microsoft.com/?id=246804
295328 - Private Network Interfaces on a Domain Controller Are Registered in DNS
[also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent private IP]:
http://support.microsoft.com/?id=295328
306602 - How to Optimize the Location of a DC or GC That Resides Outside of a Client's
Site [Includes info LdapIpAddress and GcIpAddress information and the SRV mnemonic values]:
http://support.microsoft.com/?id=306602
825036 - Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
291382 - Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?id=291382
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface [Registry Entry]:
http://support.microsoft.com/?id=296379
Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx
_________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
Well since both Nics that you see in the IPconfig are in use it is a
little hard to disable one. The one NIC is a private address that goes
between the server and a storage box. As for the 10.1.2.6 well that is
the alternate Domain controller that is in a different office. I could
remove it but if the primary address 10.2.2.2 goes down for some
reason then those people will not be able to get into the network. As
for the removing the 10.1.2.6 on the local computer side well that is
a little hard to remove when all computers are setup using DHCP. We do
not statically map any addresses on the local computers.
"Meinolf Weber" wrote:
Hello Mike,
For DC/DNS:
Disable the not used network adapter. The DNS server 10.1.2.6 is from
a different network, that will cause your problems.
For the Desktop it is the same, remove the 10.1.2.6 from the NIC
settings.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
DNS / Domain controller
Host Name . . . . . . . . . . . . : WDC01
Primary Dns Suffix . . . . . . . : internal.mulvannyg2.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internal.mulvannyg2.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-11-43-DD-8E-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.2.2.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.2.1.1
DNS Servers . . . . . . . . . . . : 10.2.2.2
10.1.2.6
Ethernet adapter DDR410:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2
Physical Address. . . . . . . . . : 00-11-43-DD-8E-1A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Desktop
Host Name . . . . . . . . . . . . : MA1931
Primary Dns Suffix . . . . . . . : internal.mulvannyg2.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internal.mulvannyg2.com
internal.mulvannyg2.com
mulvannyg2.com
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : internal.mulvannyg2.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 M Desktop
Adapter #2
Physical Address. . . . . . . . . : 00-0E-0C-D0-77-8A
DHCP Enabled. . . . . . . . . . . : Yes
IP Address. . . . . . . . . . . . : 10.2.4.50
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.2.1.1
DHCP Server. . . . . . . . . . . . : 10.2.2.2
DNS Servers . . . . . . . . . . . : 10.2.2.2
10.1.2.6
Primary WINS Server . . . . . : 10.2.2.2
Secondary WINS Server . . . : 10.1.2.6
"Meinolf Weber" wrote:
Hello Mike,
Policy problems often have DNS as a reason. Please post an ipconfig
/all from the DNS server and one workstation.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
I am having some random issues where my logon script will not run
when I log on to a PC. I can not duplicate it every time. I will
reboot my PC and the script will run then the next day after
rebooting my pc the script will not run. After a couple reboots
the script will run again. When the script file has not run I have
checked and I do have netowkr connectivity and can ping my DC. I
can even go run the batch file manually and my network drives will
then map. I have gone through and created a special Group policy
to see if adding in "always wait for network would work" and it
did not. I have completely uninstalled my virus software to see if
that was suddenly causing issue and I still have the same problem.
Any one have any ideas? Looking at my DC I do not see any errors
coming back from it and not everyone is having this issue. Just a
few people at random. All of my PC's are running XP sp2 with all
the latest hot fixes.
.
- References:
- Re: Logon script not running
- From: Mike Brester
- Re: Logon script not running
- Prev by Date: Re: Logon script not running
- Next by Date: Re: Logon script not running
- Previous by thread: Re: Logon script not running
- Next by thread: Re: Logon script not running
- Index(es):
Relevant Pages
|
