Join to Windows domain, what is benefits ?

Hi there,
I know it's strange question but can you answer it?
If I make my Mac joined a Windows domain what is benefits I get as a system administrator? Is Windows server policy deployed on Mac (Password policy and so on)?
Also if a network user (from Windows server) log in to Mac except home folder what I get?
Thanks for help

If I make my Mac joined a Windows domain what is benefits I get as a system administrator? Is Windows server policy deployed on Mac (Password policy and so on)?
You're right - if you authenticate against the Windows domain, then all the Windows policies are in effect - expiration, password restrictions, auditing, etc.
Also if a network user (from Windows server) log in to Mac except home folder what I get?
I'm not sure what you mean by this.

Similar Messages

What benefits are there to joining a Windows domain?

My company has one mac user with a Macbook Air, we have a Windows 2008 r2 domain.
I'm wondering if it is worth joining him to the domain, what benefits are there for a mac user?
We use Exchange 2007 and change our passwords every 90 days.
One concern is when the user is out of the office the cached password can become out of sync with the domain passowrd.
This is an anoyance and can be confusing.
Any advice would be much appriciated.
Thanks.

Greetings.
I am a 1 of 2 Mac users in a company that otherwise is using Windoz. I do not join the domain though, because I really see no reason to. I can get to the printers, to the web, to the Exchange and to the SharePoint. Though mostly I need SVN and cloud services anyway.
Thus no real reason. Unless there is some specific stuff that is setup on the network that is only available to windows machines authenticated with a certificate and joined to the windows domain, like for instance a split tunnel VPN or something along those lines, there is really no need to be "on the domain" connected to the LAN works just fine if not better.
HOWEVER
There is that annoying bit about the passwords.
Some sysadmins like to setup password expiration, thus forcing us mortals to rotate three (almost identical) passwords every three months. In this case you just need to setup a reminder on your calendar that prompts you a week in advance to change your password.
How to change your password? You have options:
OPTION 1
Now. If your Mac has OS pre Lion (no higher then 10.6) then you have old samba installed by default and that comes with "smbpasswd" command. To change the password just open the mighty mac terminal and type:
smbpasswd -r YOUR_WINDOWS_DOMAIN_CONTROLLER_IP -U username
Then the output will be something like this:
Old SMB password: ********
New SMB password: *********
Retype new SMB password: *********
Password changed for user username
Of cause replace the YOUR_WINDOWS_DOMAIN_CONTROLLER_IP with the IP of your domain controller. Do not know your domain controller IP? run Google "net lookup master" command. I think older macs have it. (not sure)
if you are running Lion, you do not have smbpasswd command. I think Apple either wrote their implimentation of samba or just use some stripped down wersion of it, not sure. It has to do with some dreary and borring licensing thing.
You can either install samba yourself form sources... Thus if you are brave and adventurous here is a walk through http://forums.sonos.com/showthread.php?t=24022 or you can use optopn two:
OPTION 2
If your company has not gone to the cloud hosting and still use the old-school home grown Exchange hosted in the broom closet, you might have a web version of the M$ Exchange running. The URLs usually something like: https://owa.yourcompanyname.com. If you have that then the sysadmins may have the password change feature enabled there. Login to your web interface for Outlook (OWA), In the top right corner choose the "Change Password" feature and use it.
If this is not an option because either your sysadmin is not running OWA or the password change feature is not enabled you have still have options.
OPTION 3:
If you are working for a company that loves Windows and their products you might have an M$ Office installed on your Mac. Thus you might have Remote Desktop Connection (RDC) utility. If not you can download it here: http://www.microsoft.com/mac/remote-desktop-client. Then remote desktop to a machine in your office and you will get to it's login screen where you can change the windows domain password. (This requires a machine to which you can remote desktop)
OPTION 4:
Walk up to any Windowz box that no one is using, CTRL + ALT + DEL one time and this will give you the login screen, you can change password form there.
OPTION 5:
Ask your sysadmin to setup your password to never expire, or add the policy for your user so that you can change it in OWA (see option 2)

Joining a Windows domain failing

I am trying to set up a Windows domain on a fresh install of Leopard Server updated to 10.5.1. The domain seems to run, but when I attempt to join the domain with a client running XP Professional, authentication using an administrator account seems to succeed but checking the computer record seems to fail.
Here's the log output from an attempt:
\[2007/11/19 17:18:01, 2, pid=1142\] /SourceCache/samba/samba-187/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [X] -> [X] -> [X] succeeded
\[2007/11/19 17:18:02, 2, pid=1142\] /SourceCache/samba/samba-187/samba/source/rpcserver/srv_samr_nt.c:_samr_lookupdomain(2988)
Returning domain sid for domain [DOMAIN] -> S-1-5-21-991786210-996032087-2166944342
\[2007/11/19 17:18:02, 0, pid=1142\] /SourceCache/samba/samba-187/samba/source/passdb/passdb.c:lookupglobal_samname(596)
User COMPUTER$ with invalid SID S-0-0 in passdb
\[2007/11/19 17:18:02, 0, pid=1142\] /SourceCache/samba/samba-187/samba/source/passdb/pdbinterface.c:pdb_default_createuser(389)
Could not get RID of fresh user
I do have a computer record set up with COMPUTER$ in the directory using Workgroup Manager. Windows just errors out saying that it's an internal error as a result. Any thoughts as to what could be keeping the Windows client from joining?

I am seeing the same error as well. Sometimes the computer account gets created, but the join fails. Wondering if the code complaining about the fork has anything to do with it.
[2007/11/30 16:36:35, 2, pid=25395] /SourceCache/samba/samba-187/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/auth/odsam.dylib' loaded
[2007/11/30 16:36:35, 2, pid=25395] /SourceCache/samba/samba-187/samba/source/smbd/sesssetup.c:setupnew_vcsession(1260)
setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.
[2007/11/30 16:36:35, 2, pid=25395] /SourceCache/samba/samba-187/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [X] -> [X] -> [X] succeeded
[2007/11/30 16:36:35, 2, pid=25395] /SourceCache/samba/samba-187/samba/source/rpcserver/srv_samr_nt.c:_samr_lookupdomain(2988)
Returning domain sid for domain MyDOMAIN -> S-1-5-21-2303871110-3578217151-2514236707
[2007/11/30 16:36:35, 0, pid=25395] /SourceCache/samba/samba-187/samba/source/passdb/passdb.c:lookupglobal_samname(596)
User TEST$ with invalid SID S-0-0 in passdb
[2007/11/30 16:36:35, 0, pid=25395] /SourceCache/samba/samba-187/samba/source/passdb/pdbinterface.c:pdb_default_createuser(389)
Could not get RID of fresh user

Joining mac to windows domain what are the best practice?

Hi,
I work in a MNC environment and we have been using Windows based system 95% of our servers are on windows and as of now 100% of our users are on windows. Now we are looking forward to give our management some Mac's. I wanted to know what would be the best practice to be followed in order to add Mac's to our existing domain's and use our AD. At the same time we have windows based file servers which are added to the user using windows script's on to the user profile.
Thanks & Regards,
Aj_Mac

1) Use section name instead of Title View to name your report. This way sections can be collapsed and user can still see report name.
2) Enable alternate coloring in tables and pivots for easy readablity and set table and pivot widths to 100% (for reports in dashboards) to reduce white space and achieve a more "professional look."
3) Use column selectors and view selectors to reduce the width of reports and reduce the amount of columns user sees to a "practical minimum."

Is it possible to join a Windows server domain?

Hi, We have a mixtures of Windows and Mac clients at school. We have recently had installed a Windows Server 2003. The windows all work well - but other than as a file server can I expect more from the macs? Is it possible to join the windows domain - and log in as different users so that different network drives are mounted at log in? Thanks in advance!

Hi, We have a mixtures of Windows and Mac clients at
school. We have recently had installed a Windows
Server 2003. The windows all work well - but other
than as a file server can I expect more from the
macs? Is it possible to join the windows domain - and
log in as different users so that different network
drives are mounted at log in? Thanks in advance!
Yes. The server does not have to be running Services for Macintosh.
If the server is running Active Directory, you'll have to work with the windows admin people to create the AD account.
Otherwise, you'll just hae access to the shares.
On the Mac, I think the AD options are under Directory Services.
To map drives at login, the easiest way is to write an Applescript, save it as an application, and add it as a login item.
I can't recall the exacy syntax, but for each drive, the script should look something like this:
Tell Application "finder"
try
mount "smb:\\windows.server.ip.address\sharename"
end try
You will get a user id/pw/domain prompt for each share.
For e-mail, assuming they use Exchange, you'll need exchange server 2000 SP 2 or higher with OWA, IMAP, and LDAP active on the mail server to be able to access mail through Entourage or Apple mail.
Otherwise, you'll be limited to Outlook Web Access.
Printing: Standard IP,LPR, or appletalk printer setup.

Android, Ipad authentication under windows domain environment

I’m really confused about the best practice to set up these devices in a 802.1x and Windows Domain network using ISE.
I had seen the Ipad download the ISE certificate the very first time the device is connected to the SSID. In Android device (Galaxy phone) I don’t see the device download certificate.
Testing with the Android device I was able to install the root CA certificate (a not easy procedure), then when the SSID is configured in the device I have the option to choice the root CA certificate.
Now if I don’t include the certificate in the SSID configuration, the device is able to connect with an Identity and Password only. If I include the certificate in the SSID configuration, the device ask for the certificate storage password if the option for use secure credentials is not enabled before.
How can I validate through the ISE the android device is using the certificate? Is it possible to set a rule in the ISE denying access if the device does not validate the certificate? I think EAP necesarity use certificates, but the Android device does not show anything.
I had read about provisioning and profiling the Android devices. I think the Network Setup Assistant available through Google Play is an easy procedure to install the root CA certificate. Am I Right?
The customer said it appears the certificate is being used to encrypt the username and password not for do the authentication itself. Reading about EAP functionality I believe it is right, I understand the EAP-MSCHAP actually creates a tunnel to passthrough the username and password. Right?
As the Ipad and Android devices are not in the windows domain, what should be expected when the password is expired? Customer Policy indicates users must change domain passwords every four months. In a Windows PC users receive warnings some days before the expiration but it appears nothing happen in non-domain devices. A co-worker told me the easy way is that when this happen the user should remove the SSID in the device and create it again. The customer does not like this behavior, so what should be a best practice work around?
I hope you can help me to clarify my doubts.
Regards.
Daniel Escalante

Client Provisioning for Android you can refer thease guides:
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Borderless_Networks/Unified_Access/BYOD_Design_Guide/BYOD_ISE.html#wp1024291
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/113606-byod-flexconnect-dg-000.html#anc10

Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

Every few days we see two dialogs with the following messages:
Dialog 1, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
Dialog 2, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
down in 8 day(s) 23 hour(s) 0 minute(s).
The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
adapter properties.
I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
not an option for this scenario.
I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
DNS server configured.
I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

Thanks for your response Vivian.
I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
never displayed these messages.
The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
There are only 2 user accounts configured on this server. The local admin account and another local admin user.
The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
server will shut itself down again in 3 days.
The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
on its new network and this is what is triggering the messages?
Am I clutching at straws here?

Joining a Mac OS X server to a Windows Domain

Hi all, new to the forums here and fairly new to a Mac environment. I'm looking for some guidance and assistance with how to join a Mac Server to an existing Windows domain. My questions are what kinds of options do I have for setting up a server that will be part of the Windows domain and also hosting multiple Mac clients. I looked briefly at the server options like stand alone, member server, domain server, etc. I'm having trouble distinguishing what we want the server to be defined as. I'm also wondering what are the steps I'll need to take in order to join the system to the Windows domain. Any help in this matter would be greatly appreciated!
-Terry
Mac OS X (10.4)

You use the Directory Access app found in the /Applications/Utilities folder to join the computer to the domain. Once there you can see what options you have.
You also may want to browse http://www.macwindows.com and/or post further questions you have in the Windows Compatibility forum:
http://discussions.apple.com/forum.jspa?forumID=687

What changes occur to my machine after I would join the company domain?

HI folks. I've been considering joining my mac to the company windows domain but I'm not sure what the outcome might be. Before I do that, I want to know what is going to change, be better, be worse, etc. Will it streamline connecting to server shares? Will my local profile still be available if I want to revert back? Not sure exactly what might happen so I want to know before doing so. Thanks.

http://www.techrepublic.com/article/10-things-you-should-know-about-connecting-m acintosh-os-x-systems-to-windows-networks/6127492
I also suggest to post your request in
https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_lio n_server
or
https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_ser ver_v10.6_snow_leopard

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.

Windows Domain - Joining of Ubuntu Systems

Dear Team,
Now i would like to joing my ubuntu systems in the domain, and also to apply the group policy to give access for wifi connectivity.
Server : 2008 R2, client : ubuntu 12.04 (wifi network).
Regards, Ravi Kumar

Hi,
Thanks for your post.
You could add ubuntu machine to windows domain, please refer to the following article:
How to join a Ubuntu machine to a Windows domain
http://www.linux.com/learn/tutorials/336477:how-to-join-a-ubuntu-machine-to-a-windows-domain
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Joining a Windows 7 machine to a domain

Dear all,
I have been told and also experienced, that if a windows7 machine is joined to a domain (Server 2008 R2), there can be trouble, if the time on the joining machine differs more then 5 Minutes to the Server, that the machine is joined but many things in the
background go wrong as for example GPO which are not pushed and maybe even more.
The strange thing is, you are able to login to the domain and to work with the client.
Is there a way, that after a machine has been joined, I can check, that the joining completed correctly ?
Unfortunaltey, this is a new field to me...
Thank you very much for your help and greetings from Switzerland :)
Mike

it is a fact that kerberos authentication will fail if there is too much of a time skew. In many cases, but not all, the computer will failback to NTLM authentication, which explains that some functions work correctly.
By default, joining the domain will reconfigure the time service so it will sync time with the domaincontrollers. If you experience time synchronisation issues, you should take a look primarily on the domain controllers. the dc holding the PDC emulator FSMO
should sync with an external source and all dc's should sync with that "pdc".
Note time service needs connectivity on NTP port (udp/tcp123) to the dc's in it's site to be able to sync time.
http://technet.microsoft.com/en-us/library/cc773013(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/bb727060.aspx
http://blogs.technet.com/b/nepapfe/archive/2013/03/01/it-s-simple-time-configuration-in-active-directory.aspx
i think it is a good idea to make sure time is ok before you join, because if the time skew is too large (>15hrs by default),
Windows time will fail to sync. One way would be to make sure clients can connect to time.windows.com, the default time service configured for clients. Also make sure the pdc has not too much skew compared to time.windows.com.
MCP/MCSA/MCTS/MCITP

Error in join to SMB domain from windows pc

hi,
I have a problem on mac os x server leopard 10.5. I have configured only DNS, Open Directory and SMB as PDC, In SMB service I have configured a windows domain. I have create a SharePoint for Profile folder.
I have create a test user "user1" and set home. In File Sharing I have set automount as AFP but this is not necessary for windows connection, as believe....
let's see the problem...
I go on win machine and set windows domain, enter user1 and password and I can join to my domain.
Reboot machine and logon screen appear.
MYDOMAIN is the domain in SMB service, winmachine is the name of win pc used for test.
now I enter username and password and some error appear in log of SMB service:
2008/12/01 16:27:00, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [user1] -> [user1] -> [user1] succeeded
[2008/12/01 16:27:01, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/rpcserver/srv_samr_nt.c:_samr_lookupdomain(2988)
Returning domain sid for domain MYDOMAIN -> (some code here)
[2008/12/01 16:27:01, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [user1] -> [user1] -> [user1] succeeded
[2008/12/01 16:27:01, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service profiles initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:17, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [user1] -> [user1] -> [user1] succeeded
[2008/12/01 16:27:17, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service profiles initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:17, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service netlogon initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:18, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284)
winmachine (192.168.0.120) closed connection to service profiles
[2008/12/01 16:27:18, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user [user1] -> [user1] -> [user1] succeeded
[2008/12/01 16:27:18, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service user1 initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:18, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS/system. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS/system. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=Yes (numopen=2)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=0) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=Yes (numopen=1)
[2008/12/01 16:27:19, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service user1 initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=0) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=No (numopen=1)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=0) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=No (numopen=1)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WIND read=Yes write=Yes (numopen=2)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WIND (numopen=1) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=0) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=Yes (numopen=1)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/inifile.upd read=Yes write=Yes (numopen=2)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/inifile.upd (numopen=1) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=0) NTSTATUSOK
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/win.ini read=Yes write=No (numopen=1)
[2008/12/01 16:27:19, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_file(391)
user1 opened file WINDOWS/inifile.upd read=Yes write=No (numopen=2)
[2008/12/01 16:27:29, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/win.ini (numopen=1) NTSTATUSOK
[2008/12/01 16:27:29, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:closenormalfile(399)
user1 closed file WINDOWS/inifile.upd (numopen=0) NTSTATUSOK
[2008/12/01 16:27:29, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284)
winmachine (192.168.0.120) closed connection to service profiles
[2008/12/01 16:27:29, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284)
winmachine (192.168.0.120) closed connection to service netlogon
[2008/12/01 16:27:29, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284)
winmachine (192.168.0.120) closed connection to service user1
[2008/12/01 16:27:41, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:makeconnectionsnum(1087)
winmachine (192.168.0.120) connect to service user1 initially as user user1 (uid=1025, gid=20) (pid 514)
[2008/12/01 16:27:42, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:42, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS/system. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:42, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:27:42, 2, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/open.c:open_directory(2105)
open_directory: unable to create WINDOWS/system. Error was NTSTATUS_OBJECT_NAMECOLLISION
[2008/12/01 16:28:03, 1, pid=514] /SourceCache/samba/samba-187.8/samba/source/smbd/service.c:close_cnum(1284)
winmachine (192.168.0.120) closed connection to service user1
this is an error or warning message?
someone can help me?
thank's a lot
fil

Yes, you can.
You will need to configure the virtual network switch as either internal or external.
Then, you'll need to specify the IP address of the virtual Domain Controller as a DNS Server on the Windows 8.1 device.

GS60 Ghost Pro 3k - Joining Windows DOMAIN

Just got my new GS60-2PE laptop, reformatted and reinstalled Windows 8.1, and joined to the domain. Things are working great, except every time I am outside the office it completely craps out - nothing works, windows system32 services are not starting, etc... Sometimes I can reboot and get everything to (appear to) work fine, but at least 50% of the time nothing works. I am working closely with our domain admin to troubleshoot this issue, but this is the only machine on our network that is having these problems. Hopefully someone out there might know why this MSI laptop is having problems being joined to the domain?
I am getting the following error in the Application event logs:
Event ID 1000:
Faulting application name: svchost.exe_RasMan
Faulting module name: rastapi.DLL_unloaded
Much of the time when I boot up, after I login it will be a black desktop and error message on the screen saying C;\Windows\system32\config\systemprofile\Desktop is unavailable.... When this happens I can't do anything, opening the Start menu it is empty, can only restart and have a 50/50 chance that everything loads correctly.
Also, I am sometimes getting errors saying "The stub received bad data" when I try to open any program, e.g. Task Manager. Try it again, and the program opens fine.
I have reformatted and reinstalled windows twice, the second time with our domain admin involved, we are not doing anything wrong. With this machine, these problems are consistent...
Any ideas???

errors your getting it probably no access to domain server where your laptop account is located so then it crashes and throws error once you leave location with laptop :/ so make sure the domain network isnt local type since some buisness have it as local means it only access able within their internet/wifi connections sinc it will use local ip to communicate, while when your outside and not att office or so it will fail since it's not able to communicate with server that account is on.

Px12-350r unable to re-join domain - what to do now?

Hello everyone!
I hope you can give me some advice because at the moment I am in a really stupid situation, being probably locked out of my Iomega px12-350r.
Here's what happened:
* The device has been successfully joined to my Microsoft AD domain and has been running with this config for at least a year.
* I expanded the storage array 2 days ago, adding 2 disks. Everything went fine and when the expansion completed, the new total disk space was displayed correctly in the admin web interface.
* After that, I rebooted the device. After the reboot, I could not log in to the device any more using my domain account. This account has had admin rights on the NAS and I have logged into the NAS using this account before.
* I did not change anything in the domain infrastructure.
* I know that the device cannot join the domain anymore because I activated email notifications and it keeps sending me "Unable to join domain".
I already tried:
* Login using the usual local accounts: Does not seem to work once the device is joined to a domain.
* Login via SSH. Does not work, probably for the same reason as above.
I did NOT try yet:
* The user manual mentions resetting the admin password by pushing the reset button on the back. But will this only reset config (I would be ok with that) or will it erase the data on the drives as well?
I am from Germany. Despite having purchased a 24x7 service plan, German support hotline will only redirect me to the American hotline who claim to do only desktop NAS, no px12's. I am kind of in the middle of nowhere now. ;-)
Thanks for your help!
Best Regards,
Florian
Solved!
Go to Solution.

Hi qaware,
Just to clarify, are you talking about logging into the device's web interface or logging into your active directory client?
I would first recommend rebooting everything and restarting your client in case there are more than one sessions open.
What credentials are you using to log into SSH? User should be "root" and password is "soho + admin password". Make sure you are not using any special characters.
You could do a reset from the back of the device. This is not data destructive, but it will reset user and network settings so you will have to set the device up again, rejoin the domain and import the AD users and groups.
Are there any other admin users you could try logging in under?
Have questions and need answers?
Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
LenovoEMC Support & Downloads
LenovoEMC North America Support Contact Page

Join to Windows domain, what is benefits ?

Similar Messages

Maybe you are looking for