Joining to the domain problems

Hi I have just bougth a W510. Every time i turn it on it appears a window "Enterprise Worksation Progress Window" saying tha it is attempting to add the computer to the domain in order to rename the computer and join it to the domain, but afterwards the machine failed with error code 1, and it said something about the network cable might be disconnected but internet is working quit well, i really don´t know what is going on, could someone help me?

hey CRAXRUBRA,
is your windows , Win 7 Enterprise or is it another one ? Anyway, i suggest getting in contact with Microsoft with regards to the error that you're getting via http://support.microsoft.com/gp/assistsupport
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

Similar Messages

Server is dis joining from the domain radomely

hi ,
i have a Greate problem that my applications server in windows 2003 os created on DMZ Zone is randomely disjoing the with DC server on the Same Zone ,, if ia made it work group and rejoin the into domain it works for some time and disjoiing again
, can any body suggest me solutions to this porblem as the my application is linked with domain credentials users are bomarding me since morining

Hi,
Based on my experiences, disjoining a computer from domain requires manual actions.
To disjoin a computer, we need to:
Right click on Computer, select
Properties.
Click on Change settings.
Under Computer Name tab, click on
Change.
Then choose Workgroup and input a name for the workgroup.
You may need to find the user who have done this. You can also make sure that this user doesn’t have administrator rights on the server to prevent this behavior.
Here are some similar threads below for you references:
why member server disjoin from a domain
http://social.technet.microsoft.com/Forums/windowsserver/en-US/78940e07-4dfa-448c-bba4-c46eca75f2d2/why-member-server-disjoin-from-a-domain?forum=winservergen
A server was not able to be accessed through domain account and found that the server is in WORKGROUP and not join in the domain.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ce61743c-3fef-468d-a834-69d1b1598123/a-server-was-not-able-to-be-accessed-through-domain-account-and-found-that-the-server-is-in?forum=winservergen
I hope this helps.
Best Regards,
Amy Wang

Join to the Domain network

Dear Sir
I want to join to the DOMAIN network,i have windows 8.1 single language 64 bit
so can i connect to the domain network ?
pls help me AS SOON AS
Your faithfully
siraj khan

Dear Sir
I want to join to the DOMAIN network,i have windows 8.1 single language 64 bit
so can i connect to the domain network ?
pls help me AS SOON AS
Your faithfully
siraj khan

Do CCM's have to be joined to the domain ?

I recently took over a system with a publisher and a subscriber and noticed that they were both not part of our domain. Does anyone know why they might of set this system up this way?
Thanks in advance.

It isn't required for the CallManagers to be in a domain, even if you have the directory integrated with your Active Directory domain. It is supported for them to join your domain. Joining them to a domain has no operational impact, but you should follow procedures carefully when performing upgrades, as some upgrades require you to dis-join the domain temporarily.
You cannot, however, make them domain controllers. This stops you from upgrading them or applying service packs, as doing this requires you to be logged in as local Administrator, which you cannot do on a domain controller.
Take extra care if you integrate with Active Directory and apply group policies to the CallManager server computer accounts. Some items, like password lockout settings, can get you into trouble. You will have no end of trouble repairing your cluster if your SQL service accounts get locked out, and this WILL happen during upgrades.

Laptops joined to the domain

Hey guys,
Currently we don't join laptops to our domain because of a lot of our employees work remote and our password policy. We have a password policy in place that might affect mobile laptop devices users since they are never in the office. How do you go about
managing the policy and for users laptop that don't come into the office however VPN in. What happens if their password is changed on the workstation at work or OWA, but their laptop doesn't recognize the new password. Thoughts? Any feedback would be awesome.

We join almost everything to our domain. (Local accounts are strongly discouraged in my organisation).
In your scenario, do your users not use the laptop at the office often? (they don't use it at the office and then take it home/away)?
Do they have more than one computer, and the laptop stays at home?
This can certainly cause the locally-cached password to become "out of sync" with the domain password for that user account.
In such cases, use the old/previous domain user\password to logon, then connect the VPN, then "lock" the screen, and that requires the current domain user\password to unlock. This causes the cached user\password to be re-cached with the latest
password.
This assumes that your VPN solution retains the VPN connection during the screen-lock phase.
Similar challenges for those users who have multiple devices - eg phones, tablets and multiple computers - each device will have a cache, and each needs to be updated, either manually or via re-sync.
Or do I misunderstand?
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Problems accessing windows share folders with iMac joined to the domain

Hi,
Following the Apple Seminar (http://seminars.apple.com/seminarsonline/addamac/apple/index.html?s=300) I've joined an iMac (10.6.2) to a Windows Domain successfully and I can login with my windows account.
The problem arises when I try to mount a share folder. Mac ask me if I want to access as a guest or as a registered user, and it's really weird since the folder belongs to the windows user. It seems like Mac doesn't use the login account to access the share folders...
Regards,

Hi,
I'm trying to use the Connect to Server > smb://ipaddressoftheserver (smb://192.168.100.1/implementaciones) but it ask me for the authentication again....
It seems there is a problem with Snow Leopard and AD with .local domains. I've trying this solution:
http://www.edugeek.net/forums/mac/43879-snow-leopard-ad-integration-woes.html#po st549033
Regards,

Joining a computer to the domain using the netbios name VS the FQDN

Where I work we must join computers to the domain using the netbios name (ex: mycomp) vs the FQDN mycompany.tx.com or else problems occur and the computer must be rejoined to the domain again with the netbios name- it can be joined to the domain initially, but after about 15 - 30 mins we'll get an error message when trying to logon.
The error message I believe is:
"The system cannot log you on to this domain because the system's computer account in its primary domain is missing or the password on the account is incorrect."
I haven't seen it happen in a while, but if I remember correctly this is the error message we get -I could be wrong though.
It may also have just been a "domain is not available" message.
Some additional info:
The netbios domain name is diffent then the DNS name ie: "mycompany.tx.com" was not made "mycompany" for netbios, but "mycomp" instead.
Our DFL is mixed mode with some 2000 and some 2003 servers
We used to use WINS, but now we do not.
And lastly we usually add a WINS address along with the dns address in each workstation via "advanced TCP/IP settings" (why I do not know) and occationally I will not be able to join a computer to the domain until I add this WINS address. I know what your thinking, and I will say that I am not 100% all of our WINS server were deactivated.
Any info on how to figure this out or troubleshoot this would be greatly apprieciated. Thanks a lot.

Well this happened again.
As a test before I deployed a PC to one of our branches I joined it to the domain via the FQDN: mycompany.tx.com instead of the netbios name: mycomp prior to shipping. It spent a few days in transit and when it arrived a user plugged it in and tried to logon, but recieved this message:
"The system cannot log you on to this domain because the system's computer account in its primary domain is missing or the password on that account is incorrect"
I realize this error message maybe unrelated, but if I recall correctly this is what happened last time.
I pretty sure I was thorough in removing the computer account from the nessesary DCs (it failed and needed to be replaced) before I joined the replacement to the domain with the same name.
Rejoining to the domain via "mycomp" corrected the issue.
Netlogsetup.log:
01/06 15:24:01 -----------------------------------------------------------------
01/06 15:24:01 NetpValidateName: checking to see if 'BR021WS025' is valid as type 1 name
01/06 15:24:01 NetpCheckNetBiosNameNotInUse for 'BR021WS025' [MACHINE] returned 0x0
01/06 15:24:01 NetpValidateName: name 'BR021WS025' is valid for type 1
01/06 15:24:01 -----------------------------------------------------------------
01/06 15:24:01 NetpValidateName: checking to see if 'BR021WS025.mycompany.tx.com' is valid as type 5 name
01/06 15:24:01 NetpValidateName: name 'BR021WS025.mycompany.tx.com' is valid for type 5
01/06 15:24:01 -----------------------------------------------------------------
01/06 15:24:01 NetpValidateName: checking to see if 'FGYJ' is valid as type 2 name
01/06 15:24:01 NetpCheckNetBiosNameNotInUse for 'FGYJ' [ Workgroup as MACHINE] returned 0x0
01/06 15:24:01 NetpValidateName: name 'FGYJ' is valid for type 2
01/06 15:24:01 -----------------------------------------------------------------
01/06 15:24:01 NetpUnJoinDomain: unjoin from 'mycomp' using '(null)' creds, options: 0x4
01/06 15:24:01 OS Version: 5.0
01/06 15:24:01 Build number: 2195
01/06 15:24:01 ServicePack: Service Pack 4
01/06 15:24:01 NetpUnJoinDomain: status of getting computer name: 0x0
01/06 15:24:01 NetpApplyJoinState: actions: 0xb803a
01/06 15:24:01 NetpDsGetDcName: trying to find DC in domain 'mycomp', flags: 0x1020
01/06 15:24:01 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b
01/06 15:24:01 NetpApplyJoinState: initiating a rollback due to earlier errors
01/06 15:24:01 NetpApplyJoinState: actions: 0x40000
01/06 15:24:01 NetpGetLsaPrimaryDomain: status: 0x0
01/06 15:24:01 NetpUnJoinDomain: status: 0x54b
01/06 15:24:01 -----------------------------------------------------------------
01/06 15:24:01 NetpUnJoinDomain: unjoin from 'mycomp' using '(null)' creds, options: 0x0
01/06 15:24:01 OS Version: 5.0
01/06 15:24:01 Build number: 2195
01/06 15:24:01 ServicePack: Service Pack 4
01/06 15:24:01 NetpUnJoinDomain: status of getting computer name: 0x0
01/06 15:24:01 NetpApplyJoinState: actions: 0xb003a
01/06 15:24:02 NetpApplyJoinState: status of stopping and setting start type of Netlogon to 16: 0x0
01/06 15:24:06 NetpApplyJoinState: status of stopping and setting start type of TimeSvc to 16: 0x0
01/06 15:24:06 NetpGetLsaPrimaryDomain: status: 0x0
01/06 15:24:06 NetpLsaOpenSecret: status: 0x0
01/06 15:24:06 NetpLsaOpenSecret: status: 0x0
01/06 15:24:06 NetpSetLsaPrimaryDomain: for 'mycomp' status: 0x0
01/06 15:24:06 NetpApplyJoinState: status of setting LSA pri. domain: 0x0
01/06 15:24:07 NetpApplyJoinState: status of removing from local groups: 0x0
01/06 15:24:07 NetpApplyJoinState: NON FATAL: status of removing DNS registrations: 0x0
01/06 15:24:07 NetpUnJoinDomain: status: 0x0
01/06 15:24:12 -----------------------------------------------------------------
01/06 15:24:12 NetpDoDomainJoin
01/06 15:24:12 NetpMachineValidToJoin: 'BR063WS014'
01/06 15:24:12 NetpGetLsaPrimaryDomain: status: 0x0
01/06 15:24:12 NetpMachineValidToJoin: status: 0x0
01/06 15:24:12 NetpJoinWorkgroup: joining computer 'BR063WS014' to workgroup 'FGYJ'
01/06 15:24:12 NetpValidateName: checking to see if 'FGYJ' is valid as type 2 name
01/06 15:24:12 NetpCheckNetBiosNameNotInUse for 'FGYJ' [ Workgroup as MACHINE] returned 0x0
01/06 15:24:12 NetpValidateName: name 'FGYJ' is valid for type 2
01/06 15:24:13 NetpSetLsaPrimaryDomain: for 'FGYJ' status: 0x0
01/06 15:24:13 NetpJoinWorkgroup: status: 0x0
01/06 15:24:13 NetpDoDomainJoin: status: 0x0
01/07 10:49:50 -----------------------------------------------------------------
01/07 10:49:50 NetpValidateName: checking to see if 'mycompany.tx.com' is valid as type 3 name
01/07 10:49:50 NetpValidateName: 'mycompany.tx.com' is not a valid NetBIOS domain name: 0x7b
01/07 10:49:50 NetpCheckDomainNameIsValid [ Exists ] for 'mycompany.tx.com' returned 0x0
01/07 10:49:50 NetpValidateName: name 'mycompany.tx.com' is valid for type 3
01/07 10:49:59 -----------------------------------------------------------------
01/07 10:49:59 NetpDoDomainJoin
01/07 10:49:59 NetpMachineValidToJoin: 'BR021WS025'
01/07 10:49:59 NetpGetLsaPrimaryDomain: status: 0x0
01/07 10:49:59 NetpMachineValidToJoin: status: 0x0
01/07 10:49:59 NetpJoinDomain
01/07 10:49:59 Machine: BR021WS025
01/07 10:49:59 Domain: mycompany.tx.com
01/07 10:49:59 MachineAccountOU: (NULL)
01/07 10:49:59 Account: mycompany.tx.com\myUserName
01/07 10:49:59 Options: 0x27
01/07 10:49:59 OS Version: 5.0
01/07 10:49:59 Build number: 2195
01/07 10:49:59 ServicePack: Service Pack 4
01/07 10:49:59 NetpValidateName: checking to see if 'mycompany.tx.com' is valid as type 3 name
01/07 10:49:59 NetpValidateName: 'mycompany.tx.com' is not a valid NetBIOS domain name: 0x7b
01/07 10:49:59 NetpCheckDomainNameIsValid [ Exists ] for 'mycompany.tx.com' returned 0x0
01/07 10:49:59 NetpValidateName: name 'mycompany.tx.com' is valid for type 3
01/07 10:49:59 NetpDsGetDcName: trying to find DC in domain 'mycompany.tx.com', flags: 0x1020
01/07 10:50:00 NetpDsGetDcName: found DC '\\br041svr.mycompany.tx.com' in the specified domain
01/07 10:50:00 NetpJoinDomain: status of connecting to dc '\\br041svr.mycompany.tx.com': 0x0
01/07 10:50:00 NetpGetLsaPrimaryDomain: status: 0x0
01/07 10:50:00 NetpLsaOpenSecret: status: 0xc0000034
01/07 10:50:00 NetpGetLsaPrimaryDomain: status: 0x0
01/07 10:50:00 NetpLsaOpenSecret: status: 0xc0000034
01/07 10:50:01 NetpManageMachineAccountWithSid: NetUserAdd on '\\br041svr.mycompany.tx.com' for 'BR021WS025$' failed: 0x8b0
01/07 10:50:01 NetpManageMachineAccountWithSid: status of attempting to set password on '\\br041svr.mycompany.tx.com' for 'BR021WS025$': 0x0
01/07 10:50:01 NetpJoinDomain: status of creating account: 0x0
01/07 10:50:01 NetpJoinDomain: status of setting netlogon cache: 0x0
01/07 10:50:01 NetpGetLsaPrimaryDomain: status: 0x0
01/07 10:50:02 NetpSetLsaPrimaryDomain: for 'mycomp' status: 0x0
01/07 10:50:02 NetpJoinDomain: status of setting LSA pri. domain: 0x0
01/07 10:50:02 NetpJoinDomain: status of managing local groups: 0x0
01/07 10:50:03 NetpJoinDomain: status of setting ComputerNamePhysicalDnsDomain to 'mycompany.tx.com': 0x0
01/07 10:50:04 NetpJoinDomain: status of starting Netlogon: 0x0
01/07 10:50:04 NetpWaitForNetlogonSc: waiting for netlogon secure channel setup...
01/07 10:50:06 NetpWaitForNetlogonSc: status: 0x0, sub-status: 0x0
01/07 10:50:06 NetpJoinDomain: status of disconnecting from '\\br041svr.mycompany.tx.com': 0x0
01/07 10:50:06 NetpDoDomainJoin: status: 0x0
01/11 11:21:08 -----------------------------------------------------------------
01/11 11:21:08 NetpValidateName: checking to see if 'WK' is valid as type 2 name
01/11 11:21:20 NetpCheckNetBiosNameNotInUse for 'WK' [ Workgroup as MACHINE] returned 0x0
01/11 11:21:20 NetpValidateName: name 'WK' is valid for type 2
01/11 11:21:20 -----------------------------------------------------------------
01/11 11:21:20 NetpUnJoinDomain: unjoin from 'mycomp' using '(null)' creds, options: 0x4
01/11 11:21:20 OS Version: 5.0
01/11 11:21:20 Build number: 2195
01/11 11:21:20 ServicePack: Service Pack 4
01/11 11:21:20 NetpUnJoinDomain: status of getting computer name: 0x0
01/11 11:21:20 NetpApplyJoinState: actions: 0xb803a
01/11 11:21:20 NetpDsGetDcName: trying to find DC in domain 'mycomp', flags: 0x1020
01/11 11:21:56 NetpDsGetDcName: failed to find a DC having account 'BR021WS025$': 0x525
01/11 11:21:56 NetpDsGetDcName: found DC '\\BR021SVR' in the specified domain
01/11 11:21:56 NetUseAdd to \\BR021SVR\IPC$ returned 1326
01/11 11:21:56 Trying add to \\BR021SVR\IPC$ using NULL Session
01/11 11:21:56 NetpApplyJoinState: status of connecting to dc '\\BR021SVR': 0x0
01/11 11:21:57 NetpApplyJoinState: status of stopping and setting start type of Netlogon to 16: 0x0
01/11 11:22:01 NetpApplyJoinState: status of stopping and setting start type of TimeSvc to 16: 0x0
01/11 11:22:01 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:22:01 NetpLsaOpenSecret: status: 0x0
01/11 11:22:01 NetpLsaOpenSecret: status: 0x0
01/11 11:22:01 SamLookupNamesInDomain on BR021WS025$ failed with 0xc0000073
01/11 11:22:01 NetpManageMachineAccountWithSid: status of disabling account 'BR021WS025$' on '\\BR021SVR': 0x534
01/11 11:22:01 NetpApplyJoinState: status of disabling account: 0x534
01/11 11:22:01 NetpApplyJoinState: initiating a rollback due to earlier errors
01/11 11:22:01 NetpApplyJoinState: actions: 0x40130
01/11 11:22:01 NetpDsGetDcName: trying to find DC in domain '(null)', flags: 0x1020
01/11 11:22:26 NetpDsGetDcName: failed to find a DC having account 'BR021WS025$': 0x525
01/11 11:22:26 NetpDsGetDcName: found DC '\\br021svr.mycompany.tx.com' in the specified domain
01/11 11:22:26 NetUseAdd to \\br021svr.mycompany.tx.com\IPC$ returned 1326
01/11 11:22:26 Trying add to \\br021svr.mycompany.tx.com\IPC$ using NULL Session
01/11 11:22:26 NetpApplyJoinState: status of connecting to dc '\\br021svr.mycompany.tx.com': 0x0
01/11 11:22:26 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:22:26 NetpLsaOpenSecret: status: 0xc0000034
01/11 11:22:27 NetpSetMachineAccountPassword: NetUserGetInfo on '\\br021svr.mycompany.tx.com' 'BR021WS025$' failed: 0x8ad
01/11 11:22:27 NetpApplyJoinState: status of setting machine password: 0x8ad
01/11 11:22:27 NetpApplyJoinState: status of starting and setting start type of Netlogon to 4: 0x0
01/11 11:22:28 NetpApplyJoinState: status of starting and setting start type of TimeSvc to 4: 0x0
01/11 11:22:28 NetpApplyJoinState: status of disconnecting from '\\br021svr.mycompany.tx.com': 0x0
01/11 11:22:28 NetpApplyJoinState: status of disconnecting from '\\BR021SVR': 0x0
01/11 11:22:28 NetpUnJoinDomain: status: 0x534
01/11 11:22:28 -----------------------------------------------------------------
01/11 11:22:28 NetpUnJoinDomain: unjoin from 'mycomp' using '(null)' creds, options: 0x0
01/11 11:22:28 OS Version: 5.0
01/11 11:22:28 Build number: 2195
01/11 11:22:28 ServicePack: Service Pack 4
01/11 11:22:28 NetpUnJoinDomain: status of getting computer name: 0x0
01/11 11:22:28 NetpApplyJoinState: actions: 0xb003a
01/11 11:22:58 NetpApplyJoinState: status of stopping and setting start type of Netlogon to 16: 0x0
01/11 11:23:01 NetpApplyJoinState: status of stopping and setting start type of TimeSvc to 16: 0x0
01/11 11:23:02 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:23:02 NetpLsaOpenSecret: status: 0x0
01/11 11:23:02 NetpLsaOpenSecret: status: 0x0
01/11 11:23:02 NetpSetLsaPrimaryDomain: for 'mycomp' status: 0x0
01/11 11:23:02 NetpApplyJoinState: status of setting LSA pri. domain: 0x0
01/11 11:23:03 NetpApplyJoinState: status of removing from local groups: 0x0
01/11 11:23:03 NetpApplyJoinState: NON FATAL: status of removing DNS registrations: 0x0
01/11 11:23:03 NetpUnJoinDomain: status: 0x0
01/11 11:23:45 -----------------------------------------------------------------
01/11 11:23:45 NetpDoDomainJoin
01/11 11:23:45 NetpMachineValidToJoin: 'BR021WS025'
01/11 11:23:45 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:23:45 NetpMachineValidToJoin: status: 0x0
01/11 11:23:45 NetpJoinWorkgroup: joining computer 'BR021WS025' to workgroup 'WK'
01/11 11:23:45 NetpValidateName: checking to see if 'WK' is valid as type 2 name
01/11 11:23:57 NetpCheckNetBiosNameNotInUse for 'WK' [ Workgroup as MACHINE] returned 0x0
01/11 11:23:57 NetpValidateName: name 'WK' is valid for type 2
01/11 11:23:58 NetpSetLsaPrimaryDomain: for 'WK' status: 0x0
01/11 11:23:58 NetpJoinWorkgroup: status: 0x0
01/11 11:23:58 NetpDoDomainJoin: status: 0x0
01/11 11:33:08 -----------------------------------------------------------------
01/11 11:33:08 NetpValidateName: checking to see if 'mycomp' is valid as type 3 name
01/11 11:33:17 NetpCheckDomainNameIsValid [ Exists ] for 'mycomp' returned 0x0
01/11 11:33:17 NetpValidateName: name 'mycomp' is valid for type 3
01/11 11:34:23 -----------------------------------------------------------------
01/11 11:34:23 NetpDoDomainJoin
01/11 11:34:23 NetpMachineValidToJoin: 'BR021WS025'
01/11 11:34:23 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:34:23 NetpMachineValidToJoin: status: 0x0
01/11 11:34:23 NetpJoinDomain
01/11 11:34:23 Machine: BR021WS025
01/11 11:34:23 Domain: mycomp
01/11 11:34:23 MachineAccountOU: (NULL)
01/11 11:34:23 Account: mycomp\USER1
01/11 11:34:23 Options: 0x27
01/11 11:34:23 OS Version: 5.0
01/11 11:34:23 Build number: 2195
01/11 11:34:23 ServicePack: Service Pack 4
01/11 11:34:23 NetpValidateName: checking to see if 'mycomp' is valid as type 3 name
01/11 11:34:23 NetpCheckDomainNameIsValid [ Exists ] for 'mycomp' returned 0x0
01/11 11:34:23 NetpValidateName: name 'mycomp' is valid for type 3
01/11 11:34:23 NetpDsGetDcName: trying to find DC in domain 'mycomp', flags: 0x1020
01/11 11:34:35 NetpDsGetDcName: failed to find a DC having account 'BR021WS025$': 0x525
01/11 11:34:35 NetpDsGetDcName: found DC '\\BR021SVR' in the specified domain
01/11 11:34:35 NetpJoinDomain: status of connecting to dc '\\BR021SVR': 0x0
01/11 11:34:35 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:34:35 NetpLsaOpenSecret: status: 0xc0000034
01/11 11:34:35 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:34:35 NetpLsaOpenSecret: status: 0xc0000034
01/11 11:34:36 NetpJoinDomain: status of creating account: 0x0
01/11 11:34:36 NetpJoinDomain: status of setting netlogon cache: 0x0
01/11 11:34:36 NetpGetLsaPrimaryDomain: status: 0x0
01/11 11:34:37 NetpSetLsaPrimaryDomain: for 'mycomp' status: 0x0
01/11 11:34:37 NetpJoinDomain: status of setting LSA pri. domain: 0x0
01/11 11:34:37 NetpJoinDomain: status of managing local groups: 0x0
01/11 11:34:37 NetpJoinDomain: status of setting ComputerNamePhysicalDnsDomain to 'mycompany.tx.com': 0x0
01/11 11:34:38 NetpJoinDomain: status of starting Netlogon: 0x0
01/11 11:34:38 NetpWaitForNetlogonSc: waiting for netlogon secure channel setup...
01/11 11:34:45 NetpWaitForNetlogonSc: status: 0x0, sub-status: 0x0
01/11 11:34:45 NetpJoinDomain: status of disconnecting from '\\BR021SVR': 0x0
01/11 11:34:45 NetpDoDomainJoin: status: 0x0
- I forgot to add when the user experienced this problem I checked for the computer account and found it was not present in the domain on any DCs.

Windows 7 64bit and Joining Windows 2008 domain

just installed Windows 7, 64bit. When I tried to join it to the domain I'm getting "network path not found". I've tried to manually add a host record for the computer in DNS but that doesn't work. I've even set the IP static and then registered
it in DNS. When I do this, I see the host record with the IP (static) but still can't join to the domain. What's the problem and how can I resolve it?

Hi HawaiiKai,
What is your Server operating system version, Windows Server 2003, 2008 (R2) or 2012 (R2)?
You may take a look at the KB article below:
"Network Path Not Found" Error Message When You Try to Add Workstation to Domain
Also, please make sure you have Client for Microsoft Networks
checked on the NIC properties.
Or you may consider to update the NIC driver.
A discussion thread here:
Cannot join domain "the network path was not found"
If issue insists, in case there is any Domain configuration issue, you may also seek help at the forum below:
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverDS
Best regards
Michael Shao
TechNet Community Support

Joining to the Active Diresctory

Dear Guys, I am facing problem in joining to the domain, one of university here in Oman, they order 24 pieces to our company, the OS x Mountain Lion, and they want to join to active directory all of imac. but when i try to bind to AD Windows Server 2008 R2, i got error, like authentication error.
regards
EDWIN (OMAN)

Peck, i used all administartor account but same error, any idea guys,, thank you

Trouble with detect network "Domain network" in the domain member server

HI a have quetstaion about detecking "domain network " in the windows 2012 r2 server . after instaling and adding this member server to domain i look that i cannot connect to this server . After I connect to console a detect site also public site
. After I disable and enable this netwotk site the network is correct domain. How is detect which network is it ? this contacted domain controller ? etc. ???
Thank you for answer
Falcon

Hi
Not fully understood the problem. But if you have a Windows domain and you can't add the new server to the domain or can't connect
to the server after or before joining to the domain. Then it could be no of reason first one to check is firewall.
Turn the firewall on host and source and then try again. Also are you able to ping the new server?
How are you trying to connect to the server via RDP?
If yes then you need to enable the RDP and give yourself permission to remote dial in.
Thanks
Umar

Wireless laptops in the domain disconnect and try to re-authenticate

Hi,
I have a wireless setup that is using WLSM in a 6500 switch which is also acting as WDS.
The problem that am encountering is that wireless laptops that are not in the domain are working
perfectly without any issues,they can roam without dropping the wireless LAN connection while
laptops that are joined in the domain are dropping the wireless connection and get stuck while trying
to re-authenticate.
Your help will be highly appreciated.
Thanks,
Sidi

Sidi,
Just a stab in the dark here, but maybe your group policies are effecting your laptops local firewall and blocking something on the WiFi card which cuases them to get bumped off the WiFi.
Connect those laptops hard wired to the domainand force an update using gpupdate /force, after all is done and logged out with group policy, then try the WiFi connection again.
Hope this helps...

DNS Host pointing to an IP address of a host added to the domain

Hello
I have a server already joined to the domain, I need to migrate a file server, I want this file server host name to point to the actual server that is already joined to the domain. For some reason my company decided to create a host instead of using a DNS
Alias (CNAME),
Look like it is working fine, I can connect to the shares.
ServerA -> File server to migrate
ServerB -> Server to host the ServerA shares
But on some cases looks like authentication is failing for some applications,
Do you know if there is a Kerberos limitation? I am not sure if I should set a spn

Hi,
Could you share the error message with us?
I don’t think DNS CNAME record cause the problem as long as you have configured it properly.
In the meantime, you can do some troubleshoot the issue according to the articles.
Troubleshooting Kerberos Authentication problems – Name resolution issues
http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
Kerberos authentication and troubleshooting delegation issues
http://support.microsoft.com/kb/907272
Hope this helps.

Native Mode for Computers not on the domain (Workgroup)

We recently converted our environment to PKI (HTTPS) and everything has been working great for our domain bound machines. Now in our environment we have a couple machines that are not on the domain, "workgroup computers". Does anyone
have a best practice to getting these devices connected? I have read various things on certain blogs but it seems everyone is doing it different.
I would also like to have the Workgroup cert installed via the task sequence so when the techs are installing things or just having the computer off the domain it is still communicating with SCCM. Then when the computer is joined to the domain it uses
the certs from group policy, and vice versa when a computer is removed from the domain it would revert to the workgroup certs.
Also do you have to create a cert for each workgroup computer? I would like to do it the easiest way possible since we have a seperate group who does the CA Authority certs and would rather not have to bug them for every workgroup machine.

Let's start with the last question, yes every workgroup computer needs its own certificate.
About your initial question, depending on the number of workgroup computers it might indeed be beneficial to automate the certificate request via, for example PowerShell. An example can be found here:
https://jasonhjones.wordpress.com/2014/10/28/powershell-and-certificate-requests/
The complete manual process can be found here (it's written for ConfigMgr 2007, but the process is still very similar except for the client installation parameters):
http://www.petervanderwoude.nl/post/how-to-install-a-configmgr-client-on-a-workgroup-computer-when-the-configmgr-site-is-in-native-mode/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Joining servers in domain

We have few servers that are running oracle EBS and JDEdward application. These servers are not on the domain. What will be the impact on application and database if the servers are joined to the domain? Please advice.

Sami,
We never had any issues in joining Oracle Apps servers to the network domain, and no additional steps were required, so I believe it is the same for the database.
For the database, if you want to setup a user account to startup the services instead of the local user, please refer to:
Note: 401643.1 - How to setup Domain OS User Account Instead of a LocalSystem User, to Start Windows ORACLE Services
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=401643.1
Regards,
Hussein

Can't connect to DFS shares from machines not part of the domain

I'm not sure if this is by design, but we can't connect to DFS shares from machines that are not joined to the domain. We can't even map a drive using credentials of a domain account.
Is that how DFS is supposed to work?

Hi RJO22,
I did some research on this topic, and got a conclusion:
Clients that belong to a workgroup can only access the DFS namespace if the name resolution mechanism that is in place can locally resolve the domain name
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3214a4c-8088-446c-ba4d-643d5baf87cc/how-to-access-dfs-namespace-from-a-standalone-windows-2003-server
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Joining to the domain problems

Similar Messages

Maybe you are looking for