Re: Group Policy doesn't apply
Hi,
This is a single server you mention that is having this problem so I
would not even think about restoring the sysvol.
Well the two NICs could deem a problem but on the NIC connected to the
domain, make sure it is pointed to a DNS authoritative to your domain
as primary DNS.
Question here is why it is not registering it's DNS records on it's
own. Is the DHCP client service running on this machine?
Could it be that this server being unable to register it's records, it
is unable to read records that it needs to read?
If this still fails, I would disjoin and rejoin this machine to the
domain.
Good luck
Harj Singh
Power Your Active Directory Investment
www.specopssoft.com
On Jan 23, 3:40 pm, Lafayette techie
<Lafayettetec...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I would prefer not to restore the Sysvol as no other servers or computers are
experiencing any problems...I just dis-joined and rejoined but still
receiving the errors. When I run GPRESULT, I get lots of LookupAccountSid
failed with 1789 error
.
Relevant Pages
- Re: Problem with internet connection
... Depending on the hardware/NIC you maybe can use a teaming software to combine both physical NICs to a virtual, which then can be used for automatic failover or loadbalanced. ... Multihoming a server, using more then one ip address, can result in problems you don't wan't. ... Multihomed DCs, DNS, RRAS servers. ... there are some registry changes to eliminate the registration of the external NIC. ... (microsoft.public.windows.server.networking) - Re: Urgent! New router and big disaster
... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... (microsoft.public.windows.server.sbs) - Re: issue with DC replication
... DNS server to ... As Jorge stated and explained why, multiple NICs on a DC is not recommended ... internet gateway, it is recommended to purchase an inexpensive, or cable/DLS ... there are some registry changes to eliminate the ... (microsoft.public.windows.server.active_directory) - Re: Machines not being registered in DNS anymore
... using two nics on a dc is only a problem when both nics are on the ... But if on different subnets, and one is NOT reachable by clients, yet the registration exists in DNS and will more than likely be given to a client in a query response, then YES it WILL be problematic. ... If you have an ISP's (or some other outside DNS server or even using your router as a DNS server) DNS addresses in your IP configuration, they need to be REMOVED and ONLY use the internal DNS server. ... there are some registry changes to eliminate the registration of the external NIC or simply use the internal networking routing to allow access. ... (microsoft.public.windows.server.dns) - Re: Some xp clients very slow to boot
... this connection addresses in DNS". ... You can stop DNS registering by telling it to only listen to the internal interface, however to control netlogon requires registry alterations. ... If the both NICs are internal, I would suggest to pick a subnet, team the NICs and allow your internal routers handle the traffic between subnets - Good luck! ... The one section of the article that disables these records is done with this registry entry: ... (microsoft.public.windows.server.sbs) |
|