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.

Similar Messages

How to join to virtual domain from windows 8.1 host ??

Hi there
does it possible to join to virtual domain from windows 8.1 host or not ??
I installed windows 8.1 on my system as host windows and then enable windows 8.1 hyper-v and installed windows server 2012 r2 and installed active directory domain service
now I want to join to this domain from my windows 8.1 but I can't . I create a user in active directory users and comupers and do it's DNS but can't complete .
give me this Error that may be the domain name is not correct or the user name or password is incorrect
please help me how can I join to virtual domain from windows 8.1 host in my pc ??
thanks
Regards :
Raha
whit the best regard : Raha

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.

Error while publishing Lightswitch application remotely from Windows 7 PC to Windows 2003 Server having IIS 6.0

I am trying to publish a LightSwitch 2012 application as Web Application from Windows 7 PC to Windows 2003 IIS server, .Net Framework 4.0
The publish Summary as follows
Application Name - User Test
Application Version - 1.0.6.0
Application Type : Browser
Application Server : IIS Server
Authentication : Windows Authentication
Database : Do not publish
Error details while publishing with the option "IIS server has lightswitch deployment prerequisites installed".
============================================================================
102 Web deployment task failed. (15/04/2014 16:24:51) An error occurred when the request was processed on the remote computer.)
(15/04/2014 16:24:51) An error occurred when the request was processed on the remote computer. The entry type 'unknown' was not expected at this time. The serialization stream may be corrupted.
When published without the option "IIS server has lightswitch deployment prerequisites installed".
the applications publishes successfully, But when the application is accessed from Browser it says authentication error.
I have searched a number of blogs with the same issue, but none have answered.
Any help will be highly appreciated.

I am once again facing the same issue when trying to publish remotely. But I have done nothing to the server after successful publishing as suggested below,
Not sure why the issue persists again (Could this be a firewall issue?) . Your help will be much appreciated.
[5952] MsDepSvc.exe Error: 0 :
[5952] Tracing deployment agent exception. Request ID '964acec1-797b-47c2-a4b6-3c872fc9b7ed'. Request Timestamp: '05/12/2014 09:45:31'. Error Details:
[5952] Microsoft.Web.Deployment.DeploymentException: The entry type 'Unknown' was not expected at this time. The serialization stream may be corrupted.
[5952] at Microsoft.Web.Deployment.PackageDeserializer.ReadChildren(Int32 parentId, Boolean bufferIfNeeded)
[5952] at Microsoft.Web.Deployment.SerializationProvider.<GetChildProviders>d__0.MoveNext()
[5952] at Microsoft.Web.Deployment.DeploymentObject.<GetChildrenWithoutAz>d__9.MoveNext()
[5952] at Microsoft.Web.Deployment.DeploymentObject.<GetChildren>d__0.MoveNext()
[5952] at Microsoft.Web.Deployment.DeploymentSyncEnumerable.<Create>d__0.MoveNext()
[5952] at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
[5952] at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenOrder(DeploymentObject dest, DeploymentObject source)
[5952] at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObject dest, DeploymentObject source)
[5952] at Microsoft.Web.Deployment.DeploymentSyncContext.ProcessSync(DeploymentObject destinationObject, DeploymentObject sourceObject)
[5952] at Microsoft.Web.Deployment.DeploymentObject.SyncToInternal(DeploymentObject destObject, DeploymentSyncOptions syncOptions, PayloadTable payloadTable, ContentRootTable contentRootTable)
[5952] at Microsoft.Web.Deployment.DeploymentAgent.HandleSync(DeploymentAgentWorkerRequest workerRequest)
[5952] at Microsoft.Web.Deployment.DeploymentAgent.HandleRequestWorker(DeploymentAgentAsyncData asyncData)
[5952] at Microsoft.Web.Deployment.DeploymentAgent.HandleRequest(DeploymentAgentAsyncData asyncData)
Finally, I Could able to resolve the issue. I have identified the below information for a successfull deployment
1. Light switch 2012 application can be published only with Web Deploy 1.1 (which will create Web Deployment Agent Service) in Windows Services list. I had an issue with multiple Web Deploy versions (Web Deploy 2.0, 3.0) which caused to fail the publishing
from Light Switch Development environment. Un-installed all the versions and installed only Web Deploy 1.1 and then published successfully
2. You should use Remote Publish from Light Switch 2012 Development PC as there is no option in IIS 6.0 to import the Package in IIS 6.0 with the packages files similar to the option available in IIS 7.0 and later.
3. You should be able to publish from Light Switch 2012 environment with the option "IIS server has lightswitch deployment prerequisites installed" checked. The application will publish with the option unchecked but it will not work.

Satellite U200-115 - CD Rom error - can't activate the drive from windows

Hi everyone,
I'm having some problems with my DVD rewriter drive on my Satellite U200-115.
It works very intermittently and whenever I power up the machine, the first notice I get is 'cd-rom error' even though there is no disc in the drive.
I can't activate the drive from windows either (icon in system tray).
There is the odd occassion when the drive does work in windows but this is so infrequent that I can't remember the last time (I think it was back in Nov 08).
I want to restore the system as I am getting a lot of windows file icons instead of the proper icons for images e.g. pdf, doc, etc. but am worried that the drive wont read the disc or will stop working during the recovery process.
Any ideas would be gratefully received.
Best WIshes
Nick

If its a software issue the drive will not stop working during the recovery procedure.
Do you get a CD-ROM error in Windows?
You could try to boot from a Linux boot disk. If this work it would be a software problem and not a hardware problem.
Maybe this article from the Microsoft Knowledge Base can help you:
http://support.microsoft.com/kb/314060

Unable to save document - Read Only or Open by another user error occurs when PDF is opened from Windows Explorer

Adobe Pro XI - using Windows 7 Pro OS
When a PDF document is opened from Windows Explorer, and pages are added, deleted, notations made, any type of changes, it cannot be saved until Windows Explorer is fully closed. If you try to save the document, you receive the following error - "The document could not be saved. The file may be read-only, or another user may have it opened. Please save the document with a different name or in a differnt folder. " I have confirmed the document is not read only, it is not open by another user, and it is not open multiple times. Once you fully close Windows Explorer, and try to save the document, it saves without a problem.
Are there settings in either Adobe Pro XI or Windows that will allow you to save documents without closing Windows Explorer first?
Thank you for any assistance you can provide. This error is a frustration since I open all my documents through Windows Explorer.

[discussion moved to Creating, Editing & Exporting PDFs forum]

Can only connect to smb share from Windows as "nobody"

I'm trying to share some folders on my Mac using samba. When I connect from Windows, I do not get asked for a username and password, and I get connected as a guest user (nobody). What do I do to get connected as a real user? I've tried playing with /etc/smb.conf, but I'm not sure what to change.

when you enable smb in haring system preferences on your mac, did you check the box to enable smb on a specific account?
if you did, when you initiate smb from windows try entering
smb://[email protected]
instead of
smb://mac.ip.address

Error 807/800 - using PPTP VPN from Windows 7/XP t...

Hi,
I wonder if someone could help me? I've had this issue for about 3 months now and I’m completely at a loss now. I’m trying to connect remotely to a Windows 2003 server via Windows VPN (PPTP) from home. This had been working fine for months (Draytek 2830n purchased in Feb 2011), there has been no configuration changes beforehand to cause the problem.
Problem
From Windows 7 PC – I receive Error 807 – “The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity”
From a Windows XP PC – I receive Error 800 - Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection”
Steps Taken
I have carried out the following steps to trying and resolve the issue:-
Setup port 1723 on router(s)
Swapped out router for a completely different model
Upgraded firmware on Drayek 2830N
Tried various laptops and desktop PCs running Windows XP and Windows 7
Switched off local windows firewalls and Norton Anti-virus software
Opted out of BT Web Address Help service
Rebuilt the Windows 2003 Server and setup remote access again.
Tested the desktops and laptops that didn’t work at home from various locations (work, friends houses) and they work fine from another location (so this rules out the Windows 2003
The only thing that I can’t swap out is my BT line to the Exchange. Any ideas or suggestions would be extremely helpful. I’m thinking it must be a problem with my ADSL connection, perhaps the traffic is being blocked (for some reason) as I’ve explored all other avenues. I’m out of contract with BT now (although I don’t want to move ISP) I might end up having to if it solves the problem.
Many thanks for looking.
Steve

posted in error as you've already looked at BT web address help. Sorry
-+-No longer a forum member-+-

Cannot access SMB shares from Windows boxes in AD domain

Hey folks
I've needed to tackel this for sometime, but Santa is bringing me a dual core G5 and the urgency just increased.
I have an Active Directory domain and all of my macs are successfully joined and get Kerberos tickets upon login. I can access any shares I need from OS X -> windows but NOT the other way around.
I did finally noticed that only local user accounts seem to appear in the accounts list in the sharing pref pane. So I have figured out that I can access any users folder with that one account- OUCH! What I need is access control based on the user.
For instance if I want to share ~jdoe and jdoe is a mobile account and an AD user then if I am logged into windows as [email protected] then I should be able to access the share on the mac. Conversly I should not be able to access ~jdoe with the mac's local admin account and pass.
Do I need to change my smb.conf to reflect AD and if so, where/what?
Also, do I need to map UIDs to anything? And, is that a security risk?
Thanks!
-N

Hi SpaceBass, have you looked into sharepoints or into Netinfo manager. I have been playing around with sharepoints and it does let me enter non local users into the sharing prefs- albeit manually. Only thing is , depending on the number of macs you have, it could be a long and tedious job entering it all by hand. Netinfo may have an easier way, I'll do some more digging and post back.
Cheers.

SMB access from windows

Hello,
I clean installed Lion on my MBP 2010 and Mac Mini Server 2010. I also installed Lion Server on the Mac Mini. I have the Server configured to share my drives like it was with SL Server. I made the same users and usergroup in Server.app.
I can access everything just fine over AFP with the MBP. But I have a problem with Windows 7. When I search for computers in the network it sees the server but when I double click it, it takes a while to load but eventually I get an error message saying that I have no access and that I should check the network path. I don't get a message box asking for credentials.
But when I type this directly in the adress bar: \\192.168.0.1xx (IP adress server Mac in local network) I get a message box asking for credentials. I'm perfectly able to access everything as it should this way. But why can't I access the server using it's name? If i type \\SERVER (name for Mac server) I get the same error message. I tried SMB sharing with the MacBook Pro with the same result. I tested this on 3 different Windows PC's and one was a fresh install of Windows 7 but they all gave the same result.
I really don't know how to make this work normal again. I'm probably not seeing something stupid. I know i can make a connection to a share in windows so that it access the share on boot but I really would like it normal again.
Kind regards

I've been doing some more trouble shooting at this - I have not made progress but thought I'd at least share what I've tried:
I am using Lion Server 10.7.4 and I am able to share folders with the Windows 7 desktop without an issue - it's only the windows 7 backup that seems to have a problem with using the lion network share as a destination.
I thought it might be the version of SAMBA so I tried to replace the SMBX with smbup as another thread had suggested. With Lion server I wasn't able to get it to share anything at all and once I removed it (using their uninstall tool), my netbios name would no longer broadcast. I coudn't figure out how to reverse the problem so I re-loaded the OS from scratch and started over
I also read in another thread that some folks who had issues signing in had to use the domain of their server in the username line so I thought I'd give that a try as well. The domain name is shown in the advanced tab of your network control panel under netbios name and the format to use simply DOMAIN\username - it's important to note you don't need a pair of slashes before you put your domain name as you would normally use in the server address field. Mapping network drives with the username written with the domain preceding works but so does just your username. I tried it within the windows 7 backup and it still gives an error on the first attempt then goes through on the second and ultimately the backup fails.
Any other ideas?

Connecting domain from Windows 8.1 pro to Windows server 2008

Hello,
We try to login to our domain controller from a windows 8.1 pro laptop. The login is going good it looks like, but the user is nog getting the shares that the user expects to get. This is working with a windows 7 pro laptop but on a windows 8.1 pro laptop
this is not working. What should we do to resolve this ?
Also printers are not assigned to users although they are set in the DC.
Regards,
Thejo de Boer

Hi Thejo de Boer,
According to your description ,I would like to confirm if the issue only occurred on this windows 8.1.
Firstly, please check
the file access permission.
Then, please check the event viewer to see if some error log appeared when the issue occurred.
Regards,
Kelvin hsu
TechNet Community Support

Connecting to Mac bound to a Windows domain from Windows

I have a 2010 MBP running OSX 10.6.7 which is "bound to the [my company name] domain" (that's how our corporate IT department describes it; not sure if this is technically accurate). We have a mixed Mac/Windows environment but are predominantly Windows based (I log onto my Mac using my Windows user id/password).
I'm trying to access shared files on this machine from a Windows 7 machine on the same domain.
Before I had my Mac bound to the Windows domain, I was able to access my shared files by following the instructions in OSX help (I enabled a shared folder, added my Windows username and password as a local admin on my Mac, turned on SMB access for that user, and all was good).
Now that my Mac is bound to the domain, I can access the directories associated with the local user account I have on my Mac by connecting from my Windows machine as a different user and then entering the account name and password associated with my local user on the Mac.
I can't access the directories associated with my Windows account.
I tried adding a local user (sharing only) to my Mac with the same userid/password as my Windows account, but this prevented me from logging into my corporate network from my Mac, so I deleted this local user.
Any assistance greatly appreciated.
thanks.

Partial success: after some experimentation with my local IT guru, I'm now able to access my home directory (which is tied to a network account, not a local one), but I can't access it using my Windows user ID/password.
Here's what we worked:
Confirm sharing is enabled for desired folder, SMB sharing is turned on, my local user account has access to this folder (in the users section of the file sharing dialog), and this local user account is enabled for Windows sharing. [This is no different from what we had previously done]
Get Info on the same desired folder and give read/write access to the folder (help doesn't mention anything about this step; I'm assuming that in normal use - where you're using a local account instead of a Centrify network account - you don't need to do this because you have access to these folders by default. In my case, since I'm sharing a folder in the directory associated with my network account instead of the directory associated with my local account, these permissions are not enabled by default.
Log onto my Mac from a Windows machine using my Mac's local username/password. [Again, this is no different that what I was doing previously, but because of step 2, I can now access the folder associated with my network user]
I'd prefer to just stick with a single user id/password, but this at least lets me access my files.

Can't mount 10.6.8 Server SMB share from Windows

Actually, I can mount it...I just can't read or write it.
So I'm running Snow Leopard Server on this Intel-based Mac Mini. I have a group of users who want to be able to have a common area to store files. "Easy", I think. "Just create a folder, give it the appropriate permissions for the group, and make it a share point in the SMB configuration."
So I do all this-- through the Server Admin UI, BTW.
I create the folder. I give the specified group read and write access; everybody else gets nothing.
I make the folder a share point and ensure that SMB sharing it turned on.
Then I try to mount it from my Windows machines. I create a new network place, but I'm never asked for a user name and password. So the network place is created fine, but any attempt to open it or drag something to it fails because I'm not logged into the server.
So the question is:
Why isn't my server asking users to authenticate?
And:
How can I make it start doing this?

Hehe... Servers are tricky things for sure.
It sounds like you're expecting to have users log in from outside your network, but that you're testing from within? Is this the case?
If your users are trying to log in from outside the local network of the server, then you'll need to ensure that the correct port forwarding is set up on your firewall.
Next thing I'd try... Simplify your share to ensure that the problem isn't with your group set up. Eliminate all the ACL's associated with it.
Add one sole user to the ACL, give it read and write, and try to log in using that credential.
Ensure that the POSIX Permissions are set to default. (administrator should be the owner, staff should be group, read and writable only by the owner, everyone else gets read only)
If that works, remove that user, add a group to the ACL and try and log in using a user that's listed in the new group specified.
Perhaps if you supplied a little more info about your server and how it's connected to it's network. What it's roles are etc. we might be able to give a little more insight.
HTH
-Graham

Problems Logging in to Domain from Windows XP

So, I just set up a Mac server as PDC, and I've bound a couple of Windows XP Pro machines. I've set up a couple of user accounts. When I try to log-in from any user other than diradmin (my one admin account), I get a screen that says the domain controller is down or unavailable, but its not. What should I do?

So, I just set up a Mac server as PDC, and I've bound a couple of Windows XP Pro machines. I've set up a couple of user accounts. When I try to log-in from any user other than diradmin (my one admin account), I get a screen that says the domain controller is down or unavailable, but its not. What should I do?

Error while connecting to SAP Server from Windows XP Client.

Hi,
I am facing the problem while i am trying to connect my Windows XP Clients( With Service Pack 3, DI-API Installed and Microsoft SQL Server Native Client Installed) to SAP server i got follwoing Error.
Connection Failed :
SQL State : '08001'
SQL Server Error : 233
[Microsoft][SQL Native Client]Named Pipe Provider Could not open the connection SQL Server [233].
Connection Failed :
SQL State : "HYT00"
SQL Server Error : 0
[Microsoft][SQL Native Client]Login Timeout Expired
Connection Failed:
SQL State :'08001'
SQL Server Error : 233
[Microsoft][SQL Native Client]An Error has occured while establishing new connection to the server.
When connecting SQL Server 2005, this failure may caused by the fact that under the default setting SQL Server does not allow remote connection.
Regards,
Arpit Shah

Hi Arpit,
Solution of Error in starting B1 after installation should help here too.
Kind regards
Mario
SAP Business One Forums team

Anybody know anything about Windows 7 joining Samba/NT4 Domains?

Hello all,
I recently failed at getting a computer running Windows 7 to join a Samba server's domain, I was later succesful at joining the machine to the domain after installing Windows 2000 and discovered the solution (adding missing data in the ldap database for the machine account) would possibly have allowed me to join the domain w/ Windows 7 on the client machine.
While I'd love to find this out by trial and error, I can't experiment right away, since other people need to use these computers. Google searches seem to yield mixed results; some people have indicated that they've successfully joined domains w/ a Samba PDC or NT4 PDC (which should be, for all intents and purposes ecquivalent feats), but other threads seem to indicate that
1) there might be regressions in later Win 7 releases, preventing people who formerly were able to join NT4/Samba domains from doing so as of May 2009.
2) Microsoft considers this functionality (the ability to join NT4 style domains) depracated.
3) Microsoft has promised to fix things so that Win 7 machines will connect to Samba PDCs.
I was wondering if, pending my own direct expirementation, somebody could help me cut through the FUD.
thanks!
Last edited by pseudonomous (2009-07-29 05:29:40)

I don't know if I'm ressurecting a dead topic or not, but in my experience Windows 7 fails a trust relationship with samba versions below 3.3.4. After 3.3.4 it joins just fine. I know this because at the time I was running an Ubuntu Server as a samba PDC. I had to recompile a newer version of samba. I replaced it with Arch soon after, which had an up-to-date package.

Error in join to SMB domain from windows pc

Similar Messages

Maybe you are looking for