Tag Info

New answers tagged

-3

Remove all the DNS server entries from your IPv4 network configuration. Then add your dns server IPv4 address as the only one. Also may need to flush dnscache.


0

As for ADFS and ADFS Proxy, no it is not possible to install an ADFS and ADFS Proxy on the same server. (Last time I researched this was 2013, it might have been changed but I highly doubt it) However it is possible to install ADFS on a DC especially because the ADFS server itself does not present significant load. But you still need to properly ...


0

I had the same issue on Windows 2008 R2 with WPAD record. To fit it we add fake DNS record to hosts file like 1.1.1.1 WPAD and after restart the update client it stop using proxy. In some cases the Server needs to be rebooted after WPAD block. Cheers, Andrey


0

it was 50 min applying computer setting...Mcafee was the issue at my side, booted to safe mode, disabled Mcafee, and server booted up fine then, will work with mcafee on issue Hope this will help to someone


0

We have lot of possibilities to create or extend a DC to cloud. firstly, we have EC2 services to host a new AD or extend your AD to cloud. Please refer to the AWS directory services. AWS Directory Service Now you could also launch a windows server with AD service configured over a VPN connection(you can use direct connect or linux server VPN) to the ...


0

Take a look at opsi (opsi.org) for a deployment solution that does not require AD. It is free (opensource, gpl) and works great, but you definitly want some help in setting it up, depending on your inhouse know how with linux and windows. There are some advanced features that cost money,too.


8

How would this be setup connection wise without forcing all traffic through the domain controller? With site to site VPNs. You'd set up your cloud assets as a site, and then establish a site-to-site VPN between your cloud site and each of your physical sites. An alternate option, that Microsoft uses, but is generally ill-advised (unless you really, ...


4

When you boot a domain controller into Directory Services Restore Mode (DSRM,) Active Directory is offline on that DC. That is why you cannot load Active Directory Users and Computers on that DC. Assuming you are not using full disk encryption such as Bitlocker, this simple trick will get you back in the game: Boot the domain controller from alternate ...


2

RFC 4120 has your answer deep on page 74 and 75. It reads: kdc-options This field appears in the KRB_AS_REQ and KRB_TGS_REQ requests to the KDC and indicates the flags that the client wants set on the tickets as well as other information that is to modify the behavior of the KDC. Where appropriate, the name of an option ...


1

You'll need both the Domain Functional Level and the Forest Functional Level to be 2008 R2. To understand the differences, consult this page from Microsoft: http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels%28v=ws.10%29.aspx You'll note that there's no difference between 2008 R2 and 2012 R2 FFL - so that should be ...


0

After you log in as "MFC\user.name" and then log out, does it still show "E5530\user.name"? Also, is there a local user with the same username as the domain user? If so, would you consider changing one of those? so that you may be able to login directly as user.name and it won't change need "MFC\" before it.


3

Scary the situation you're in, but not impossible, and can be solved easily by enabling "SMTP matching", which is a process of transferring the source of authority from your Office 365 to your local active directory. this can be achieved by matching the SMTP address of your Office 365 accounts to the SMTP address of your Active Directory accounts, and using ...


0

Where are the DCs connected - one on each switch, or both on one switch? Where are clients connected? Wondering about how traffic is getting across those switches - trunk/bridge or routed?


0

Thanks for the suggestions. I was able to fix the problem. Basically what I did was to clean the metadata with ntdsutil and seized the roles on the Windows 2003 DC. clean metadata: http://community.spiceworks.com/how_to/show/616-remove-a-failed-domain-controller-from-a-windows-2003-domain seize roles: ...


2

It appears that there's a firewall between the client and server that is blocking the communication required for the client to join the domain. My suggestion would be that if the firewall is relevant only to these two instances that you unblock (allow) all traffic through the firewall between these two instances.


2

It seems that the DNS record for the DC could not have been found. Have you tried adding the DC's IP to the preferred DNS servers under the computers IPv4 settings?


0

I've had this exact problem. What kind of network do you have? You need one that is fully meshed for replication to work properly. If you open up active directory sites and services, you can see DC's are trying to replicate from each other. They will complain if they can only see one main DC, they need to be able to see and replicate from each other.


0

It does not pick a server but deploys the application to all of the servers in the specified group. The documentation should probably state that Deployments will be provided to all servers that belong to a particular group


0

Does the server have more than one network adapter? If it does, disable all but one. On that one active adapter make sure it has a static IPv4 address assigned with the DNS set to 127.0.0.1. In the IPv6 settings of the network adapter remove ::1 from the list of DNS servers. Finally from a elevated command prompt run "ipconfig /registerdns".


1

Please restart Dnscache services. Go to services.msc --> Click on DNS Client and than restart.


1

I personally have done it a lot of times. It's absolutely safe once you use VSS (application aware). The second KB which was recommended by Veeam is worth to be checked.


0

Eventually they all just figured it out, I guess. I took a look a few days later and the relevant DNS entries existed and I'm no longer getting any errors running repadmin.


2

Wheter the network of a domain controller is classified als domain network doesn't depend on the gateway configuration. The behaviour of a false network classification can be caused the NLA (network location awareness) service starts before the domain is available. In this case the public or private network is choosen and not corrected afterwards. How to ...


0

What you are asking: how can I change the Active Directory of the Samba share (from A to B) without modify all the permissions in the filesystem of the samba share server? Isn't possible. The new AD domain will need to be referenced. You'll have to replace the permissions on the existing SAMBA server with permissions for the new domain manually. ...


2

Another method to try to identify those servers might be to run something like Network Monitor on the Domain Controllers and run a capture, filtering for authentication traffic. You could then further filter by the ip addresses of your servers to narrow the displayed results. The trick is going to be determining what authentication traffic is related to your ...


1

One thing you could do is remove the A record and the other DNS Mnemonics. This would result in the usual DNS records for a DC not being registered, and not returned for normal authentication or group policy connections. Then run a packet capture to identify where any traffic may be originating from. How to optimize the location of a domain controller ...


5

Shut down each DC for a couple of days and wait for the screams. Seriously, it's the only way. Whoever/whatever wants to talk to Active Directory should be able to find a domain controller using the proper process. But some application developers are definitely foolish enough to want a statically-defined DC; well, it's their fault, and they should pay for ...



Top 50 recent answers are included