Joined to domain issues?

Has anyone else had this issue. I installed Windows 10 9926 as a hyper-v VM. Everything worked on it, the Start button and the cortana search bar. Once I joined it to the domain and rebooted the start menu doesn't work or the search bar next to the start
button. When I click the start button nothing happens, as well as on the search bar. Anybody else experience this. I also have the update installed.

Hi Anthony,
Please note the findings below:
1. I was checking the Lync Client configuration on one of the PC that is not joined to the domain, still on the domain network via site to site VPN connection. I noticed that the Connected Lync Server varies: sipinternal.domain.com, sipexternal.domain.com,
lync.domain.com (Pointing to the Edge Server IP).
2. Edge Server External Settings: Single IP address with the FQDN set to lync.domain.com for all 3 services and the following ports configured. Access Edge Service: 5061, Web Conferencing Edge Service: 444, A/V Edge Service: 443 with NAT enabled public
IPv4 address. I have checked the replication status between the Front End and Edge Server, it is up to date.
3. In regard to the https://lyncdiscover.domain.com, I don't have the lyncdiscover.domain.com published, but it is pointing to the NAT enabled public IPv4 address which is assigned for A/V Edge Services.
4. For the port forwarding, I am using the Cisco Meraki router.
Please advise if there are there is something that I am missing.
Thanks!

Similar Messages

Windows 8.1 Pro join to domain issues....

We bought some Windows 8.1 laptops and purchased the upgrade to the Pro version. When I attempt to join the laptops to the domain, it prompts me for domain credentials, I enter them, and I get an error....
Changing the Primary Domain DNS name of this computer to "mydomain.com" failed.
The name will remain "mydomain.com". The error was:
The specified domain either does not exist or could not be contacted.
Of course, the domain DOES exist and we have plenty of Windows 7 workstations signed into it just fine. I hit OK then login to the laptop using a domain account. At this point, I get an error telling me that no logon servers are available to authenticate.
This is a Windows 2008 domain controlled environment. Everything works fine otherwise for the Windows 7 systems, only these Windows 8.1 systems are having any issues. The new laptops are even showing up in DNS on the domain controller.
Any ideas what I might be missing? Is there something special about joining Windows 8.1 Pro systems to a domain?

OK; took a couple of more days than planned to get back on site. We're continuing to do testing, but here's the IPConfig /ALL that was requested. 10.0.0.1 is the gateway, 10.0.0.10 is the DC. The laptop is "Me-L" and the domain is "mydomain.com".
The below was pulled after getting IP information assigned via DHCP. The laptop is not joined to the domain at the moment and login is a local account.
Windows IP Configuration
Host Name . . . . . . . . . . . . : Me-L
Primary Dns Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com
Wireless LAN adapter Local Area Connection* 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : A0-88-69-46-A4-CF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : A0-88-69-46-A4-D2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : EC-F4-BB-9C-36-56
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.108(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, August 21, 2014 11:29:52 AM
Lease Expires . . . . . . . . . . : Wednesday, August 27, 2014 11:29:50 AM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.10
DNS Servers . . . . . . . . . . . : 10.0.0.10
10.0.0.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wi-Fi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3160
Physical Address. . . . . . . . . : A0-88-69-46-A4-CE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Apply network settings join domain issues

I create a default task sequence in CM 2012 R2. On the apply network settings there is the option to join the domain. If I select to join to the domain, there is an account to set. I set the account and test the account (test button right there) and
the test to ad succeeds.
I then apply and close the task sequence. if you go back into the task sequence, and check the account to join domain, the password is now much longer than the original (only dots shown of course) and if I click test, the test FAILS.
I am not sure if that is the expected behavior or the root of my issue.
My issue is my machines are failing to join the domain. Under Windows\Pather\UnattendGC, I see a log file with the error, failed to join domain, error code 5 (something like that). When I look up that error, I see it means access denied.
Any ideas?

The task sequence will never show the correct length of the password for security reasons, so that's the expected behavior.
Could you share what permissions you've given that account?
These are the permissions that I use:
Scope: This Object and all descendant objects
- Create Computer Objects
- Delete Computer Objects
Scope: Descendant Computer Objects
- Read All Properties
- Write All Properties
- Read Permissions
- Modify Permissions
- Change Password
- Reset Password
- Validated write to DNS host name
- Validated write to services principal name
This will work for every kind of deployment scenario that you may have to use the account in.
Regards,
Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

Windows live mail having problum after joining in domain examples incoming is good but sent or outgoing is not there and also send mails are not exporting at the time of live mail exporting time?

windows live mail having problem after joining in domain examples incoming is good but sent or outgoing is not there and also send mails are not exporting at the time of live mail exporting time?

This is not usually related to AD issues, but it may be more of a DNS issue. I posted a request in your other thread to post an unedited ipconfig /all of the DC and of the client.
This may help use diagnose this issue and your other thread's printer issues.
Thank you,
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Solaris 11 - can't join AD domain

I've upgraded to Solaris 11 from 11 Express and am trying to join the system to an Active Directory domain. I first joined workgroup, then tried to rejoin the domain, at which time I get the following (names changed to protect the anonymous):
myuser@ganesh:~# smbadm join -u "DomainAdmin" lothlorien.domain.com
After joining lothlorien.domain.com the smb service will be restarted automatically.
Would you like to continue? [no]: yes
Enter domain password:
Locating DC in lothlorien.domain.com ... this may take a minute ...
Joining lothlorien.domain.com ... this may take a minute ...
failed to join lothlorien.domain.com: UNSUCCESSFUL
Please refer to the system log for more information.
/var/adm/messages shows this:
Nov 11 00:46:17 ganesh smbd[641]: [ID 270243 daemon.error] smb_ads_update_dsattr: ldap_sasl_interactive_bind_s Local error
Nov 11 00:46:35 ganesh smbd[641]: [ID 702911 daemon.error] smbns_kpasswd: KPASSWD protocol exchange failed (Cannot contact any KDC for requested realm)
Nov 11 00:46:35 ganesh smbd[641]: [ID 702911 daemon.notice] Machine password update failed
Nov 11 00:46:35 ganesh smbd[641]: [ID 702911 daemon.error] unable to join lothlorien.domain.com (UNSUCCESSFUL)
I know for sure the system is locating the DC and trying to register itself - I can see the events in the Windows event log. Having deleted the previous computer account, if I watch the Computers node of the AD Users & Computers MMC snap-in, I can see the Solaris system appear briefly as disabled, then disappear a few seconds later (with corresponding events in the DC's Security event log).
I can't find any documentation specific to S11 (as opposed to SE11) that addresses what might be different (if anything) in the smb join protocols. I know by now that S11 can autogenerate your /etc/krb5/krb5.conf so the fact that I can delete/rename that file and it will reappear with valid information validates the fact that it does locate and connect to the (K)DC and get relevant config info, not to mention that I can type garbage for my domain password and the behavior is different so it can do kerberos authentication.
I think the key error here is the "ldap_sasl_interactive_bind_s Local error" but it's not enough information for me to determine causality. I've already gone through Google searches and implemented changes related to the NTLM levels and so forth, but unlike with SE11 which I did have working, these did not solve the issue.
I'm still trying to go through the S11 documentation including the End of Feature Notices for what's changed but I didn't see anything revelatory in the Interop guide. I know this could also be something that's in my AD/GP configuration on the Windows side (e.g. I've implemented a PKI and strengthened system authentication among certain domain members). Has anyone run into anything similar? Do you have S11 (as opposed to SE11) joined to your domain?

I finally got this figured out. It's a problem with client_lmauth_level on the smb service. the below script snippet configures Solaris 11 to join an AD domain on Windows 2008 R2:
echo *** Installing SMB system
pkg install system/file-system/smb
echo *** Installing SMB service
pkg install service/file-system/smb
echo server $TIMESERVER > /etc/inet/ntp.conf
svcadm enable ntp
echo *** Joining domain: $DOMAIN
svccfg -s smb setprop smb/client_lmauth_level=2
svcadm enable -r smb/server
smbadm join -u $DOMAIN/$DOMAINADMIN
Obviously, you should set the various variables for your local environment and probably a good idea to sync the clock explicitly instead of assuming ntpd will do it for you.
In addition, I had to set the auth level on the Windows 2008 domain:
Start -> Admin Tools -> Local Secuity Policy: Security Settings -> Local Policies -> Security Optiopns:
Network Security: LAN Manager authentication Level = Send LM & NTLM - Use NTLMv2 security session if negotiated

Joining to domain on same computer account name

Hi,
I have a critical server. I need to reinstall it with clean installation an same name. I don't have permissions to delete computer account from AD, but I have permissions to add to domain. If I remove server from domain reinstall it and will join to domain
with same name. Does this can cause any issues? Do I have to delete server computer account before joining to domain?
thank you,

Hi
If you are reinstalling server and do not want to delete the existing computer account, you'll get error "Computer account usually exists already, and security on that account does not allow you to join — usually because the computer was joined
previously by using different computer account credentials."(Assuming you did not joined it to domain in present case). So you must first delete the existing account or get full permissions on the account.
If you receive the error "Failure to create a computer account," it usually means that either the account already exists or that there are insufficient access rights available to the user who is trying to join. Table 10.8 shows the error codes
that come under this category.
Table 10.8 "
Failure to create a computer account " Error Codes
Description
Actual Error
Error Code
Computer account usually exists already, and security on that account does not allow you to join — usually because the computer was joined previously by using different computer account credentials.
ERROR_ACCESS_DENIED
5
The user has joined so many computers that he has exceeded the default per user computer quota (by default, 10).
ERROR_DS_MACHINE_ACCOUNT_QUOTA_EXCEEDED
8557
The specified user already exists.
ERROR_USER_EXISTS
2224
Also pls refer the article for in-depth details :
Join and Authentication Issues
http://technet.microsoft.com/en-us/library/cc961817.aspx
Hope this helps. :)
Thanks

Joining a Domain on my new server

I've just set up my AD domain on Windows Server 2008 R2. I've added users to domains before but right
now I'm completely blanking on what steps I've missed. Basically so far I have ran DCPROMO and set up my FQDN, the computer name is server and lets say the FQDN is myserver.com , i've set up a static address of 192.168.0.25, dns and default gateway are 192.168.0.1
on the server. I've added dhcp roles, my scope is 192.168.0.2-192.168.0.55. Does this seem ok so far? Now the point I need help on, I have a windows 8 laptop and to test the server/domain I wanted to try and join it, what do I need to do? Before I used virtual
box so had a seperate client machine but still have some issues I recall. I tried simply changing my laptop to be a member of the domain and entered the domain name but I get the error about an active directory for "myserver.com" could not be contacted.
What steps am I missing?

I don't want to get into creating a Click-by-Click walk through for all that off the top of my head. I can give details to get you going in the right direction but you need to search out the smaller details on your own,...or use the Help that is already
built into all of these MS products.
Your home Router already determines the IP Range you use. I'm guessing it uses 192.168.0.1 for itself. That is a very common one, but it could be something else. You'll have to check that yourself.
Turn off DHCP on the home router since it won't be needed for that anymore. Once the DC is in place it will take over that job with it's DHCP Service. You can't have two DHCP Services running at the same time on the LAN without making special accommodations,...which
there is no point in getting into that here.
Assuming the home router is using 192.168.0.1 then give the DC something like 192.168.0.10
Once the DC is promoted and the DHCP Service on the DC is up and running,...use the whole range for the Scope (ex. 192.168.0.1 thru 192.168.0.254).
Then set an Exclusion for, say, the first 20 addresses (192.168.0.1 thru 192.168.0.20). This means that DHCP on the DC will begin with 192.168.0.21 as the first address when it starts assigning them to clients.
Within the DHCP Service add the DC's IP# for the DHCP Options pertaining to WINS and DNS. Set these at the Server Level, not the Scope Level because they will always be true even if you had other IP Segments with other clients there (which you won't, but
I'm teaching a principle here).
In DHCP at the Scope Level add the "Router" DHCP Option which will be the IP# of the home router. If you had other network segments (which you won't) then each segment would be associated with a different DHCP Scope and have a different "router"
IP#,...hence why it needs to be a Scope Level option.
WINS needs no setup,...if it is installed and running it will "just work".
At the point where DNS, DHCP, and WINS are running then clients will get the address config from DHCP automatically when they boot up (before a user even logs in) and DNS and WINS will start populating with the Client Details. In some cases DNS may
not populate until the Client actually joins the domain. There are settings within the DNS Service that alter that behavor.
On the DC when you open the tool Active Directory Users and Computers,...you will see Active Directory will start populating Clients as they join the domain and they will initially be listed in the Computers "container" until you manually
move them somewhere else. Users created in Active Directory will initially be listed in the Users "container" until you move them somewhere else.

Workstations not Joining the Domain after OSD

I have a sporadic problem happening in my Environment. OSD Deployments for the most part finish successful , workstation joins the domain with no issues. At certain locations occasionally the workstation does not join the
domain. Have you seen this happen before? are there logs on the DC or DP which might explain why this is happening?

While you are at it grab setupact.log and setuperr.log from two locations, c:\windows\panther and c:\windows\panther\unattendGC. These logs will give more details on why the domain join fails.
Daniel Ratliff | http://www.PotentEngineer.com
Also take a look at C:\Windows\debug\NetSetup.log.
Cheers
Paul | sccmentor.wordpress.com

7410 CIFS/NFS cannot join AD domain

I've been asked to help on this issue but I know little about the 7410 configuration, and the Admin Guide available wasn't much help with some of the errors I've seen.
This is a Sun Storage 7410 Version ak/SUNW,[email protected],1-1.17
CIFS and NFS are enabled, and appear to be configured correctly as far as controller names, IP addresses, etc. DNS is working and nslookup from the CLI does work. Lan Man Compatibility Level is set to 2. Looking in the logs, I noticed that in the log labled system-identity:node, there is a line that says:
aksh fatal error: could not connect to akd; is it both enabled and running?
What does this refer to?
Also, in the top title bar of the 7410 GUI, there is an error which says:
An attempt to import the resource 'ak:/ad/da0f40fc-014e-ca1f-880d-892ff109361c' has failed
Was this error as a result of someone trying to join a domain, or is it some other indicative error? When an administrator attempts to join a domain, the message "no such domain" appears, but the domain does indeed exist.
What else can I look at to find out the source of this problem?
Edit: I should add that we can ping to this 7410 by IP, but not by host name.
much thanks
Edited by: mdinaz on Jul 29, 2009 12:23 PM

I would recomend sticking the latest patch on - there's a fix in there for AD 2008 domains - though not sure if this is your issue. Also, I don't think the box will show in DNS until it is added to the domain (unless manually added to the DNS server).
http://wikis.sun.com/display/FishWorks/Sun+Storage+7000+Series+Software+Updates
hth. Chris

ZTIDomainJoin has attempted to join to domain [Domain.LOCAL] too many times. Count = 4_ZTIDomainJoin_25-6-2013 13:06:20_0 (0x0000)

Hello,
in my invironment the domain-join isn`t working well.
In the log : ZTIDomainJoin has attempted to join to domain [Domain.LOCAL] too many times. Count = 4 ZTIDomainJoin 25-6-2013 13:06:20 0 (0x0000)
What can i do to fix this issue permanent?
Thx

The log you actually want to look at is %SystemRoot%\Debug\NetSetup.log. As Keith said, this file will tell you why a Domain Join is failing and should point you in the right direction to understand what's wrong. There's a
good (but old) primer on debugging the issues here: http://technet.microsoft.com/en-us/library/cc961817.aspx
David Coulter | http://DCtheGeek.blogspot.com |
@DCtheGeek

Should I join the domain with my new server 2008 R2 before I run dcpromo ?

Hi Team,
Should I join the domain with my new server 2008 R2 before I run dcpromo ?
Brand new server, 2008 r2. I want it to eventually be my forest root. Should I go ahead and join it to the domain as just a member server and then do all the ? Should I run adprep before I join
the domain? I'm only asking about member server at this point...before dcpromo.
Most of the posts I have seen relating to installing Additional Domain Controller (ADC) onto a domain, state that the machine they are starting with is NOT a member of the domain. In my case,
the machine I want to make an ADC is already a member of the domain.
Regards,
Rajesh Behara

Hi Rajesh,
Is your issue related to Project, the Microsoft scheduling and planning application? In case it is not, please post your question to the appropriate forum in order to have help from experts.
Here is the
TechNet SQL Server forum.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Could not provision the RemoteApp collection. Error: Could not join the domain. Unable to reach the domain.

Hi
I am trying to set up an Azure RemoteApp Hybrid solution.
I have created RemoteApp net and uploaded a custom image and all that is fine.
When I link my template to my Collection it fails after provisioning for about an hour.
I recive the following message: Could not provision the RemoteApp collection. Error: Could not join the domain. Unable to reach the domain.
The join domin works fine and I have tryed with account with different lvl of access to my AD.
Any suggestion how to solve this?

Hello Eric,
I am landing into the same Problem and i read your guidance on this issue. Let me answer it point by point.
1. Check the VPN state to ensure it is active or connected state:
Sundesh:My Azure RemoteApp Virtual Network after successfull S2S configuration shows as Ready. Is that what you mean by Connected State? Earlier to S2S, it was just under connecting state.
2. Verify your VNET configurations have proper IP address ranges
Sundesh: The VNET address range, the Local address range and DNS has already been verified twice. In fact the same address ranges(with exception to VNET) are working fine on a VENT config on Azure VM instance. Verified.
3. Verify your DNS IP configurations are valid, (often this is the problem)
Sundesh: Yes its done and verified
4. Verify the credentials entered for domain join are valid.
Sundesh: Tested these credentials by joining a regular Azure VM to domain and it works there.
5. Make sure your VPN endpoint that Azure RemoteApp service is connecting to is not blocking traffic.
Sundesh: Can you please let us know the specific port numbers that we need to consider and i can have it checked with the Network team
Thanks
SUndesh

USB drives not accessible until I join a domain

Hi,
I´ve been struggling with this problem for a loong time now.
Simply put, I want to use a usb drive in a laptop running Windows 7, and the device is detected correctly but Windows says that I need to format it. And in My Computer the drive has got a letter but when I doubleclick it it says it´s unaccessible. But if
I join the laptop to my customers AD it suddenly works as it should.
Since I discovered that, I just ignored it since all computers would join the domain, but now I need to install several laptops that´s not going to be ad-joined. So I need help solving this usb problem.
The customers uses laptops(Dall Latitude Exxx models) only and we install these using WDS. I think that all models of laptops have this issue and all usb drives. I haven´t been able to narrow it down to a certain model or anything else.
Everything else works as they should. The usb ports works fine using mouse and keyboard and similar. It´s only usb drives that are the problem.
I know that the hardware isn´t faulty since I can boot up using Linux and everything is fine, plus when I join the domain everything is also fine.
I have tried reinstalling chipset/usb drivers but nothing has helped. Also sfc /scannow doesn´t help.
Using gpedit.msc I set everything in "Users/Administrative/System/Access to removable storage" to inactive but this makes no difference.
I have not had this problem outside this customer.
Does anyone have any ideas? If so, please help!
Regards,
//Andreas..

Hi,
we should figure out what’s the difference between the two situations. I have the following thoughts to narrow down this cause:
Do you have preinstalled any security applications in your image?
Does this issue occur to all USB devices?
After you join the domain, can you log on with a local account to access USB devices?
You can get the security policies via rsop.msc as well.
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

Tecra A9: Cannot join a domain or view websites wirelessly - Vista

I'm having a problem with wireless networking on this new installation of Vista.
I can view & connect to a wireless router no problem but when I try to join a domain or view most web pages it just will not play ball.
I can ping both local and external addresses and some web pages work with no problem at all.
I have tried updating the wireless drivers from the toshiba web site and when that did not make a difference from the intel website but to no avail.
If i plug in a network cable everything works fine.
I have another notebook running XP which connects to the same wireless router and has none of these problems.
Help!
Stu

Seems that there is nothing wrong with your wireless lan device at all. I think there are some settings of Vista, that prevent some internet pages from working, maybe built in firewall or antivirus program. Internet Explorer 7 has built in some security features as well, so you might take a look at this.
Perhaps the first thing you could try is to use another internet browser, like firefox and check firewall settings.

Windows 8.1 will not allow me to join a domain Setting up a new 2012 server, and am trying to join laptops running Windows 8.1 to this new domain. When I go to properties for This Computer, Join a domain wizard is greyed out. Can I join a Windows 8.1 com

Windows 8.1 will not allow me to join a domain
I am trying to join laptops running Windows 8.1 to domain. When I go to properties for This Computer, Join a domain wizard is greyed out. Can I join a Windows 8.1 computer to a domain?

Have you verified that your Windows 8.1 is a Pro or Enterprise edition? The Basic edition cannot join a domain.

Joined to domain issues?

Similar Messages

Maybe you are looking for