Login issue on Windows XP, connecting to 10.4

Fingermouse and Vortec,

Just wanted to make sure that you have an account enabled on the Mac for the PC to browse.


Mike

iMac G5 Mac OS X (10.4.5)

Yes. I believe the problem is deeper than that. The Mac can't see any of my shared Windows printers or anything where my iBook can be browsed by the PC and can print to the PC and so on.

Intel Mac Mini Mac OS X (10.4.5)

Vortec,

Seems to be an issue with the new intel core duo's. Hopefully my original will help raven who is having an issue with her iMac G5

Thask,

Mike

I'm having the same issue ....


I've got the intel core solo mac mini running 10.4.5

I've turned on file sharing, I've edited the smb.conf and the xp machine to use non-encrypted passwords.

I know its not an issue with my XP machine because I have tried to login locally from my the terminal with smbclient.


everytime I do this I get a NT STATUS_LOGINFAILURE


I see this everytime I try to log in in the samba log file at /var/log/samba/log.smbd

[2006/03/09 18:11:38, 1] auth ods.c:opendirectory_smb_pwd_checkntlmv1(371)
opendirectory smb_pwd_checkntlmv1: [-14200]opendirectory user_auth_and_sessionkey key_length(0)


something is wrong with the file sharing when it checks the password.

I wanna know if there is a way to setup a seperate user/pass word file for samba uses only. normally it would be something like smbpasswd, but I get errors in terminal trying to do that.

Yes, there's definitely an account enabled for Windows Sharing.

I've got two Mac Minis here, a G4 and an Intel Core Duo. Both are running 10.4.5 but I can get into the G4 fine, as long as I login using my main account.

Another account on the same machine (created more recently) is completely inaccessible, in much the same way as the Intel machine is unreachable, no matter how you try and log in or set up a network drive. The older account was setup under 10.4.0 (I think) and hasn't stopped working under 10.4.5 (yet).

So there's something else going on here... It looks like 10.4.5 has done something odd that can affect both the G4 and Intel machines, but it's clearly completely broken Windows sharing on the Intel platform.

Well, at least it has for me!

Mac Mini Core Duo Mac OS X (10.4.5) 2GB RAM

That could actually be a very good clue. Perhaps 10.4.5 does something strange with account creation that doesn't allow the SMB services to work properly? That's why I can log into my iBook which is running 10.4.5, because the account was created using 10.4.2 - and just upgraded to the latest. It would also explain why most people are having problems with their Intel systems - though it isn't exclusive to the Intel systems - because they're all coming with 10.4.5 now and the account is created when the system is bought.

I am having the same issue. did all the obvious stuff enable windows sharing, remote login etc...i can ping the mini and see it when i browse the network just cant login

I'm having this issue too. So I guess turning on FTP until someone can figure out how to fix this is the best workaround.

Having exactly the same problems and have been pulling my hair out! FTP is a work around but I hope apple fix this ASAP!!!

Just like to add another to the list of people with the problem. I was starting to think it was me, or I'd broken something somewhere else.

Something is definately not happy though. Even using the smbpasswd command to change password causes errors, so it seems to be something a little more deeply rooted.

Here's hoping there's a workaround soon!

[snip]

I know its not an issue with my XP machine because I
have tried to login locally from my the terminal with
smbclient.

Actually, it is an XP problem. Or, rather, an NTFS problem.

everytime I do this I get a NT STATUS_LOGINFAILURE

This usually means that you generated a user which doesn't have file system permisssion to access the volume or folder you're trying to access. In other words, the user exists, and has a valid logon, but NTFS security is locking him out. How did you generate the user? Did you grant the user permission to access the folder or volume using the Security tab of the folder or volume's Properties dialog? If NTFS permission was not set, you can try to connect from now until the 12th of Never, and you'll never get in.

has anyone used the info on this page: ? I've found it to work every time.

Charles,
Thanks for the tip, but that's old news that has long since been factored out of the equation as a solution. It is basic Applesque instructions that we have long since done and it failed.

I stumble back on that bookmark every so often and try it for the heck of it and it never works.

okay. That means that there's something strange going on here. Okay, I just launched one of my WinBoxes. XP Home. Nothing shared. Let's see what happens when I try to set up a share point... Let's pick a random folder on a volume other than the C: drive. Set up network permissions, share the folder... Okay. I can connect to the share. I can view the share. I can open files, move files, write to files, delete files, create files. That's all with the username on the XP system set to be the same as the username on the Mac. (different passwords, though.) Let's try a different username. Generate a new user. Generate a new folder. Put some stuff in there. Step through all the permissions stuff... can I log into the share? Yes.

Okay, I got it to work first time on a vanilla XP Home, SP2, system. Took maybe 30 seconds, not counting time to boot the WinBox. All I can say is that either you have a configuration problem on either the WinBox or the Mac, or there's something Very Strange™ going on.

Wrong way round!

I think most people in this thread are trying to map from Windows to a shared folder on a Mac, i.e. Drive Z: on my Windows PC points to a shared folder on my Mac.