Gah.. can't join domain! DNS problem

The server has Intel Xeon CPU E5606 @ 2.13 GHz, 8 GB RAM. Windows Server 2012 R2 DataCenter x64
The workstation has Intel Core i7 4820K CPU @ 3.70 GHz 16 GB RAM. Windows 8.1 Professional x64

Rob Dunn wrote:Your primary DNS server address on the client...it's IPv6. I wonder if this is your problem.
I haven't had much (*ahem* any) experience with IPv6 in a domain environment. With that said, see this link:
https://windorks.wordpress.com/2014/09/17/the-day-ipv6-broke-my-dc/You may have to configure the IPv6 properties to use the loopback address ( ::1 ) on the DC.
You're awesome! That was it. **Grumbling to self about what a waste of time!!!**I ended up going to the link that someone on that page you gave me referred to.. that link is to some Microsoft troubleshooting tools. I tried to do "Put IP4 before IP6" fix, but that didn't do anything. So I just went ahead with the Disable IP6 one.https://support.microsoft.com/en-us/kb/929852/en-usand now it's joined!

Similar Messages

Windows machines can't join domain after 10.5.4 upgrade

Howdy folks,
I have a ticket open with Apple on this but am posting here in hopes that someone might have an idea for me.
I upgraded our Mac OS X Server 10.5.3 to 10.5.4 on Sunday, and this morning several users reported that their PCs running Windows XP SP2 were unable to login to the Windows domain hosted on this machine. It's the primary domain controller for the Windows users.
One thing to note is that I had to reinstall the server completely because the 10.5.4 patcher crashed, creating all kinds of mayhem. I did a fresh install of OS X Server 10.5 and immediately applied the 10.5.4 combo updater to it. I had to restore the Open Directory from an archival copy, and the SMB was created fresh. Not sure why but the SMB services weren't preserved by the Server settings export command in Server Admin.
I thought unbinding the PC from the Windows domain and then rebinding it with a new name would help, but I've been completely unable to add older computers to the domain, even after removing the old computer records first.
I've got a reproducible failure mode for this problem on a Windows XP virtual machine running on VMware Fusion on my Mac. Here's the method I've been using to create the failure:
1. Change Windows XP System name to something new that doesn't already have a computer record on the Mac OS X Server and reboot.
2. After the reboot, run "NewSID" program on Windows to globally change my Windows machine's SID to a new, random value, and reboot again.
3. Attempt to use the Network ID wizard in the Windows Control Panel to re-add the machine to the domain under a new name so there's no conflict with any old computer records floating around in Open Directory. After it prompts me to enter the username, password and domain name for a user who's authorized to add machines to the domain, I get a dialog box that displays this error:
"Your computer could not be joined to the domain because the following error has occurred:
An internal error occurred."
Not too informative.
Here are the error messages I see in /var/log/samba/log.smbd (searching for the new computer name in the search field):
netbios connect: name1=BIGMAC name2=JEFFVM6
netbios connect: local=bigmac remote=jeffvm6, name type = 0
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'JEFFVM6$'
odssam_getgrnam gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Groups record for 'JEFFVM6$'!
opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Computers record for account 'JEFFVM6$'
kDSStdAuthNewUser was successful for account "jeffvm6$"
At that point it's impossible to join the computer to the domain no matter what. The most puzzling thing is that SOME of our users were able to login without any problems whatever. The ones that were either physically off or somewhere else when the 10.5.4 upgrade was applied are the only PCs that seem to be having problems.
Any help at all is appreciated. I suspect this is some kind of a SID conflict because the SMB server had to be recreated from scratch, but have no idea how to fix the client, the server, or both to make the computer account creation process work.

The problem is fixed.
The issue boils down to an argument between the Open Directory server on bigmac (the OS X Server machine) and the SMB server on bigmac. The crucial information I needed to solve this problem was located here: http://www.radiotope.com/node/61
The Open Directory database had to be restored from a backup following this weekend's problematic upgrade, and it had a different value for the SID for the Windows domain than the one used by the SMB server software itself. Even stranger was that the Open Directory database actually had the wrong domain name! The It was listed as "BIGMAC" in Open Directory, even though it was set to the correct Windows domain name in the SMB server.
The solution was to demote the SMB server from a Primary Domain Controller to a Standalone Machine, and then repromote it. Although I changed no values in the settings, and did not modify the plist containing the SID in the Open Directory via the Inspector in Workgroup Admin, after the SMB PDC was repromoted, the SIDs and the domain names in Open Directory and the SMB config agreed with each othe. Now new machines can join the domain and users can login just as they did before. No client-side modifications are necessary.
Hope this is helpful to someone else. It was quite the hair-pulling experience for a while there.
Jeff Kirk

XP Pro SP2 PC can't join domain

I had a crash and restart with an XServe that was acting as OD Master and PDC for several users. Now the trust relationship has been disrupted and I can't get the PC's to rejoin the domain. When I try, the XP box gives a message that "the user name could not be found" and the NETSETUP log on the PC shows the following:
11/16 11:04:52 NetpDoDomainJoin
11/16 11:04:52 NetpMachineValidToJoin: 'TULKAS'
11/16 11:04:52 NetpGetLsaPrimaryDomain: status: 0x0
11/16 11:04:52 NetpMachineValidToJoin: status: 0x0
11/16 11:04:52 NetpJoinDomain
11/16 11:04:52 Machine: TULKAS
11/16 11:04:52 Domain: bbcmpls
11/16 11:04:52 MachineAccountOU: (NULL)
11/16 11:04:52 Account: bbcmpls\diradmin
11/16 11:04:52 Options: 0x27
11/16 11:04:52 OS Version: 5.1
11/16 11:04:52 Build number: 2600
11/16 11:04:52 ServicePack: Service Pack 2
11/16 11:04:52 NetpValidateName: checking to see if 'bbcmpls' is valid as type 3 name
11/16 11:04:52 NetpCheckDomainNameIsValid [ Exists ] for 'bbcmpls' returned 0x0
11/16 11:04:52 NetpValidateName: name 'bbcmpls' is valid for type 3
11/16 11:04:52 NetpDsGetDcName: trying to find DC in domain 'bbcmpls', flags: 0x1020
11/16 11:04:52 NetpDsGetDcName: found DC '\\GONDOR' in the specified domain
11/16 11:04:53 NetpJoinDomain: status of connecting to dc '\\GONDOR': 0x0
11/16 11:04:53 NetpGetLsaPrimaryDomain: status: 0x0
11/16 11:04:53 NetpGetNt4RefusePasswordChangeStatus: trying to read from '\\GONDOR'
11/16 11:04:53 NetpGetNt4RefusePasswordChangeStatus: failed but ignored the failure: 0xc000000f
11/16 11:04:53 NetpLsaOpenSecret: status: 0xc0000034
11/16 11:04:53 NetpGetLsaPrimaryDomain: status: 0x0
11/16 11:04:53 NetpLsaOpenSecret: status: 0xc0000034
11/16 11:04:55 NetpManageMachineAccountWithSid: NetUserAdd on '\\GONDOR' for 'TULKAS$' failed: 0x8ad
11/16 11:04:55 NetpJoinDomain: status of creating account: 0x8ad
11/16 11:04:55 NetpJoinDomain: initiaing a rollback due to earlier errors
11/16 11:04:55 NetpLsaOpenSecret: status: 0x0
11/16 11:04:55 NetpJoinDomain: rollback: status of deleting secret: 0x0
11/16 11:04:55 NetpJoinDomain: status of disconnecting from '\\GONDOR': 0x0
11/16 11:04:55 NetpDoDomainJoin: status: 0x8ad
So it's seeing the server as the PDC of the domain, but the NetUserAdd is failing. What should my next move be?
Thanks in advance,
Andy

I had a crash and restart with an XServe that was
acting as OD Master and PDC for several users. Now
the trust relationship has been disrupted and I can't
get the PC's to rejoin the domain. When I try, the
XP box gives a message that "the user name could not
be found" and the NETSETUP log on the PC shows the
following:
is the computer still listed in WGM under windows computers ?

DNS Problems with WRT54G

2 Nights ago we had storms in the area; next morning wife calls me at work and says that internet connection does not work. Get home and take a look at it. I can connect to router wired or wirelessly, was able to look at the configurations, etc. but when I try to access internet pages I get an error indicating DNS problems.
I have cycled power on cable modem (also Linksys but don't remember model number at the moment) and router. Still had the same problem wired and wirelessly.
I reset the router to factory defaults, connected to it both wired and wirelessly and still had the DNS rpoblems.
I reconfigured the router with my original security settings, connected to it wired and wirelessly and still had the DNS problems.
I connected directly to the cable modem and had no problems accessing internet at all.
Is there any way that I can force the router into updating DNS information? Or possibly reset DNS information?
I have run out of things that I know to try. I hope someone can help.

Usually a DNS problem is caused because the router is not connecting to the Internet properly.
Since you have a cable modem, you can usually leave the WRT54G set to its factory default settings, except that you might need to "Clone the MAC address" of the computer that works when connected to your modem.
Hope this helps.
If you need more help, please do the following:
1) state your ISP
2) state the make and exact model number of your modem (not the WRT54G).
3) Connect your computer, by ethernet cable, directly to your modem (not the WRT54G). Verify that you have a properly working Internet connection, then do the following test:
Go to "Start" > All Programs > Accessories > Command Prompt.
A black DOS box will appear. Type in "ipconfig /all" (with no quotes), then hit the Enter key. Post all of the results, except if your "IP address" does not start with 192, then post only the first 3 digits of it, along with the rest of the info. To copy the info to your post, highlight (select) the info, then use the copy (Ctrl-c) and paste (Ctrl-v) keys.
Message Edited by toomanydonuts on 05-16-2008 07:13 AM

Build and Capture - How to install software updates without joining domain

Due to security policy, can't join domain before the patch installation.
I want to know the detail steps. I only set SMSMP when install Configuration Manager, but in the end, NO updates are installed.
Do I miss some steps? what are the detail steps?

HI Jorgen
Sorry for my poor English!
You mean I should create two new collections, one is X86,
another is X64.
Add the "Unknow Computer"
object,
that I want to build and capture, into the two collections
Deploy the patches to the two collections
Do I correct?

Can't join clients to domain in Server 2012 R2 Datacenter

I have done the searching. I have installed 2012 Datacenter 64bit. No problem. I installed the Ad Ds role and elevated it to a domain controller. I installed DHCP and DNS roles. I now want to join a client computer to this new
domain in the server. (it's the only domain). However, nothing I try works. I get the message:
"An Active Directory Domain Controller (AD DC) for the domain "DGR.MINE" could not be contacted."
Ensure that the domain name is typed correctly.
If the name is correct, click Details for troubleshooting information"
Details:
The error was: "This operation returned because th teimout period expired." (error code 0x000005B4 ERROR_TIMEOUT)
The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses; 192.168.1.200
Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.
In my 2012 Server the DNS address is set to 192.168.1.200
In my client computer the DNS address is set to 192.168.1.200
The server and the client are both connected to a simple switch, so I'm using straight through Ethernet cables. I've tried crossover for client to server connections also, but no luck there either.
This should be a simple process. Can someone with patience give me a step-by-step on setting my server to a domain controller, DNS server, assigning the DNS address, and what else I need to do to allow a client to connect? Then can I get the
same wonderful help in connecting the client to the server? I wouldn't ask for such detail, but I'm needing to check to see where I messed up, if indeed I can find where.
Thanks very much.

Make sure that the machine you are trying to join to your new domain has access to the domain (can ping the IP address of the domain controller) and has set itself to point to the IP address of the domain controller
as its DNS server.
Hi, Tim
I can ping my domain controller, but not quite sure about how to set itself to point to the IP address of the domain controller as its DNS server. where do I do it? Thanks in advance.
my sql keep dropping out the domain for some reason, I cant see any domain user account and the location is not entire directory anymore on my sql server even the domain name appears there. so I decide to take it off domain officially and rejoin later, but
failed to rejoin and gives me an error msg just like that.
Regards
Linda

Windows 8.1 Pro has error while joining domain, while windows 7 pro has no problem to join in the same network

I am having the same issue as posted in http://social.technet.microsoft.com/Forums/windows/en-US/6ea57e5f-6e9d-49bd-9dd7-832ea84c0276/windows-81-pro-will-not-join-domain?forum=w8itpronetworking
There are a few other people have the same issues. However there was no real solution provided although the post was marked as answered. I am posting it here again and hopefully I can get some help to solve this issue.
We got two new PCs, one with windows 7 and the other with windows 8.1 Pro. In the same network with domain, the windows 7 pc has no problem at all to join the domain. However the windows 8.1 Pro won't join the domain. On the windows 8.1 Pro computer,
I can ping the other computers in the network. The error message says:
An Active Directory Domain Controller (AD DC) for the domain "cmi" could not be contacted. ...
In my case, the domain name is "CMI". I am sure the DNS setting is correct. What did I do wrong? Any help is greatly appreciated. Thanks.

I tried the solution in that article.
In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters folder, there is no
NeutralizeNT4Emulator. So I followed the instructions and created one, and set the value to 1. Then I restarted the computer and tried to join the domain again. I got the same error. Below is more from the netsetup log file:
06/04/2014 21:36:37:256 -----------------------------------------------------------------
06/04/2014 21:36:37:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 1 name
06/04/2014 21:36:40:256 NetpCheckNetBiosNameNotInUse for 'XPS8700' [MACHINE] returned 0x0
06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 1
06/04/2014 21:36:40:256 -----------------------------------------------------------------
06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 5 name
06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 5
06/04/2014 21:36:40:256 -----------------------------------------------------------------
06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'cmi' is valid as type 3 name
06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid for cmi returned 0x54b, last error is 0x0
06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid [ Exists ] for 'cmi' returned 0x54b
----------------below is the error message from the pop up window
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
The domain name "cmi" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "cmi":
The query was for the SRV record for _ldap._tcp.dc._msdcs.cmi
The following domain controllers were identified by the query:
cmi-dc2.cmi
cmi-dc1.cmi
However no domain controllers could be contacted.
Thanks.

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

WinXP computers can't join the domain

Hi, I'm setting up my first Xserve and I'm having troubles making WinXP machines join the domain.
With OS X and Win98 clients I have no problems with the tests accounts I have created, but with with WinXP machines I get the error that they can't Join the domain becouse Access is Denied. I don't think is a configuration error on the server's services or the WinXP boxes becouse I can join the domain and access the account for diradmin OK from the WinXP boxes, so it may be an account configuration problem.
Also the accounts have network home folders, don't know if this might also cause a problem, I did try with no home assigned and still got the same error.
Any help would be appreciated

Fixed the problem myself....
Creted a new account and dindn't move anything on it, nothing managed and nothing changed on the account windows tab.
Joined the domain with the diradmin account, and after the reboot used the new test user, logged in fine and home folder was mounted as a Network drive perfectly.
Hope this helps someone in the future

Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."

Hi,
Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."
DC:windows Server 2008 R2
Domain functional level:Windows Server 2003
When Winxp join domain, have no this error message.
I checked http://support.microsoft.com/kb/2018583?wa=wsignin1.0 does't work.
There have 3 suggestion in this article:
1.The "Disable NetBIOS over TCP/IP" checkbox has been disabled in the IPv4 properties of the computer being joined.
Doesnt's work.
2.Connectivity over UDP port 137 is blocked between client and the helper DC servicing the join operation in the target domain.
On my DC, I run netstat -an, reslut as below:
UDP 192.168.20.3:137 *:*
3.The TCP/IPv4 protocol has been disabled so that the client being joined or the DC in the destination domain targeted by the LDAP BIND is running TCP/IPv6 only.
We are not using IPV6.
This server recently updated from Windows Server 2003 to Windows Server 2008 R2. Before upgrade, when Win7 and Win2008 join this domain, also have the same error message.
Please help to check this issue.
Thank you very much.
BR
Guo YingHui

Hi Guo Ying,
I have faced this critical error which makes over-writes the host names in the domain when you join.
For example: Already you had a host name called as PC.domain.com in the domain.com Domain.
When you try to add the another host name called as PC in the domain.com Domain, it doesn't give you the duplicate name error on the network it does over-write the existing host name called as PC.domain.com & it will add the new host name into the domain.
Host name which got over-written will get removed from the domain. I faced this issue in my project. My DPM host name got removed from the Domain & new host name got joined into the domain which halted my backups for one day.
Final Resolution is as follows:
You need to start the dns console on the DC & drop down the domain name.
Select the _msdcs when you click on _msdcs it will show the Name Server's list on the right hand side.
You need to add the Domain Naming Master under the _msdcs or add all the domain controllers which you had.
After you add the Name server's try joining the PC OR Laptop to the domain which is successfully joins it.
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

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.

Hello, I have a problem with my Yahoo Messenger, I can't join in chatroom. It's prompting like "yahoo error, you've been refused to access"..please help me..thanks

Hello, I have a problem with my Yahoo Messenger, I can't join in chatroom. It's prompting like "yahoo error, you've been refused to access"..please help me..thanks

post in a yahoo messenger forum. These forums are for apple products and software.

HT201364 MacBook Pro has DNS problems. Need to Download new OS, but can't.

I need to download on another computer since my I can't download from my MacBook, but I only have one old desktop with not enough space or a Windows laptop. I want to download it onto a thumb drive on one of those machines. How can I do that?

It would make a lot more sense to fix the "DNS problems," whatever they are, but if for some reason you can't do that, and you also can't free up about 5 GB of space on your other Mac (which doesn't have "DNS problems"?), then you'll have to install OS X on an external drive, boot from it, and then download the Mavericks installer. You can't download it directly to a secondary volume.

Lion & Mountain Lion won't join domain

Hi,
We have a Windows Server 2008 R2 network, with OS X 10.8 Server and various Macs running 10.6, 10.7 and 10.8.
However, we are having problems joining OS X Lion and Mountain Lion machines to the domain, while Snow Leopard Macs work fine.
With Lion & ML, when we try and bind to the Windows Server domain, the following error is returned:
"The authentication server could not be contacted (5200)"
And
"The authentication server could not be contacted" (without the error code)
We have tried joining the domain using the IP address of the server, with no luck. The Macs can ping the domain controller and such. The domain controller also handles DNS, which is properly set in the DNS settings on the Macs.
Our domain name is similiar to this: orgname-idcode
All Servers, Macs are patched with the latest updates. We just can't understand why Snow Leopard works while the others fail.
Any idea?
Thanks.

Hi ChrisU,
It sounds like it may be DNS related. Although this article is older and references 10.5, I would make sure the reverse lookups are in place per this article:
Mac OS X v10.5: Verifying DNS consistency for Active Directory binding
http://support.apple.com/kb/ht3394
Also, this article will enable debugging logs for the Mac side of things, both AD and OD:
Mac OS X Server v10.5, 10.6: Enabling Directory Service debug logging
http://support.apple.com/kb/ht3186
I hope this helps!
- Ari

Cannot join domain "the network path was not found"

Hi there.
As I wanted to install new Microsoft Lync Server, I tried to prepare a virtual machine for this. For some reason I used a virtual machine that I tested for some another services, therefore it had some changes on it.
As you know before installing Lync Server your client must be join a domain and when I tried to joined it I faced with this error "The following error occurred attempting
to join the domain “ysatech”; the network path was not found "
Before my search, I thought it was DNS problem. I checked DNS but nothing was wrong.
I searched for it and I read some forums answers and I resolved it:
As I said my client server had some changes, the problem was in the NIC but not about DNS or WINS. The "Client for Microsoft Networks" of
NIC of my domain network was not checked and it must be checked.

Check the dns setting on client and ensure the setting as below.
1. Each workstation/member server should point to local DNS server as primary DNS and other remote DNS servers as secondary.
2. Do not set public DNS server in TCP/IP setting of client/member server.
3. If multiple NIC are configured disable the unrequired NIC.Check the NIC binding order too.
This issue may occur if the TCP/IP NetBIOS Helper Service is not running on the client computer.
http://www.chicagotech.net/pathnotfound.htm
Network Path Not Found" Error Message When You Try to Add Workstation to Domain:http://support.microsoft.com/kb/285182
I will also recommend to enable the Client for Microsoft Networks.If still issue persist post the ipconfig /all details of client computer.
Best Regards,
Sandesh Dubey.
MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator |
My Blog
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Gah.. can't join domain! DNS problem

Similar Messages

Maybe you are looking for