The file sharing and connecting to samba servers functionality would be a lot cooler if it didn't give impossible errors like "An error occured - error = -5023". Or error = -47. WTF?! -47 is impossible to search for too. (Guess how often 47 shows up in your average mailinglist archive).
They both meant that I got the password wrong when I tried to connect to the other computer, I think.
My dad is visiting and I was trying to copy some photos from his laptop to mine so I could put them on a CD for backup. Yes, in the end we did succeed, but I'm not sure that my demonstration of how cool OS X is at connecting to other devices was so good.
"Well, dad, if your windows POS followed the Zeroconf spec, which Apple calls Rendezvous, this would have been very very easy."
hehe, no kidding. I need another Mac just so I can demo Rendezvous properly.
:-)
(now waiting for either the 17" or the new 15" when it comes out ...)
You can go to Apple's support site (apple.com/support) and search for "error codes." There are a few files listing many of the cryptic error codes.
Part of brian d foy's Mac::Errors module is a command-line tool called macerror:
% macerror -47
Mac OS error -47 (fBsyErr): File is busy (delete)
% macerror -5023
Mac OS error -5023 (afpUserNotAuth): No AFPLogin call has successfully been made for this session
Wow. That is just brilliant. Thank you for pointing that out. :-)
I was getting the dreaded -5023 warning, and the definitions posted by Chris Nandor got me thinking that I was not listed in Win2k as an authorized user. So, I added my iBook name to the Win2k users (Start: Settings: Network & Dialup Connections: Incoming Connections: Users). That did it, and I was able to log in.
Try setting your registry key:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Lsa/LmcompatibilityLevel to 3
This worked for me on a W2k system.
"Well, dad, if your windows POS followed the Zeroconf spec, which Apple calls Rendezvous, this would have been very very easy." ... ?
It would also be easy if the Mac handled SMB properly, and perhaps also didnt give some stupid ass error that you have to piss around with trying to find out what it means.
Then we have the stupid fuck Mac lusers who no matter what, will NOT accept critisism of the Holy Platform Macintosh itself.
It's got a LOT of fucking problems - get over it and accept some fucking critisism assholes.
well, regarding error 5023 :
the OS X seems to be implementing properly due to the fact that the Wintel machine connects to the samba service on the mac no problem...
while in the other direction , hello...
getting your "authorizations" straight on Win is the key as is the least straightforword using windows as a user and not some "expert"...
Another dynamic to this issue...
I manage a Windows domain w/ a couple Macs (os 10) and have run into the -47 error while dealing with mounting shares. The first share mounts fine (using smb) but when I try mounting a 2nd share, the error -47 apears.
My solution was to just create a "Mac" share on the win2k server and use AFP on the Mac to mount it. Works fine...
Every OS has it's issues... OS X is an outstanding options, as is win2k, and they both (with a little work and research) provide reliable connectivity to each other.
Fuck macs, their shit and overpriced.
It's "...they're shit an overpriced" as in "they are".
oops....typo. "AND".
i'm trying to connect a mac to a freebsd server running samba. i also geht the 5023 error. any ideas?
"i'm trying to connect a mac to a freebsd server running samba. i also geht the 5023 error. any ideas?"
Use netatalk instead? I don't mean to be a smart ass but _if_ you don't need samba for anything else, netatalk is easy to set up.
Hey guy above! I 'm having the same issue. I setup a samba server on a FreeBSD machine and all I do is get errors. Does anyone have any suggestions?
just edit your /etc/samba/smb.conf file to have 'valid users = [username1] [username2] [etc]' and then run smbpasswd as each username, osx has some problems figuring out permissions.
Wondering if anyone's heard of Rendezvous causing problems on a PC network. I'm a graphic design instructor who insisted on having OSX and now the IT dept has found that our macs are pinging about 2000 times a minute... maybe an hour. All that I know is our macs are responsible for network congestion and I'm wondering if there's a better solution than a) reverting to OS 9, b) taking our maclabs off the net, or c) sticking us on a windows server. Any advice will be much appreciated. Thx.
PS - Why do people who bash others on posts always seem to misspell critical words. It's an idiot thing, not a PC user thing... So I'm wondering what an idiot's doing reading about computer issues anyway...
I've been having a lot of problems saving with the -47 error showing up every time! something to do with pdf ? even though I'm just trying to re-save an .ai file! Wish you guys were on hand in my office!
hey pinged_out just a wild guess but maybe your macs have a virus similar to sobig or blaster the only reason that I think that it might be somthing like that is because that is what happened to several of my PC running 2k... they just start pinging like crazy all the time and I seem to remember somone saying that they had blaster on an osx machine although I'm really not at all sure worth looking into anyway. oh yeah and umm Macs AND PCs (ok well win2k) are both good and bad.
Can't be a virus - there aren't any for OS X yet.
I had the same error. Probably because i wasn't sharing any folders on my pc!!! However, there's a dozen other things that could be wrong...
This might be all you need to do -- if everything else is set up right:
So, if you haven't already, on your windoze box, right click on the folder you want to share and select "sharing..." or whatever it says. If You're trying to share your "My Documents" folder, you MAY need to right click on it, get Properties, and then say "Find Target..." and share the actual folder. It depends on what version of windows you'e using, i imagine.
You _may_ have to "add yourself to a workgroup" before you can share a folder. XP walks you through this, I dunno what it's like on 2000 or 98... But, you want to make up a new workgroup and tell the pc to allow files to be shared on the local network. If you're at home, you (most likely) do NOT want to add yourself to a domain. You want a workgroup instead, and you can just make up a name. You also need to give your pc a hostname (like WINDERZ) and a common name (like 'my crappy pc")
Then, on the OS X finder, do a "connect to server" and type in smb:// and then the hostname you gave the compute (WINDERZ). It will magically figure out the correct workgroup.
Once you've shared at least one folder on the pc, typing in your username and password will bring up a dialog asking you to pick the folder you want to connect to instead of "error -502029191234333".
It WOULD be nice if the Finder had simply said "Error: there are no shared folders on that machine"... :(
If you have broadband and don't have a firewall or know EXACTLY what you're doing, i would recommend "unsharing" the folder(s) after you're done with it -- don't leave any more doors open for hackers than you have to... Also, don't use the default workgroup name "WORKGROUP", "WKGRP", "HOME", or anything it suggests. Make up something unique -- the mac will figure it out on it's own.
I have run into error 5023 when connecting my mac to pc. I heard that the solution is to go here on the pc:
[HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Lsa/LmcompatibilityLevel to 3]
I know it's a bone head question but how do I get to there (the registry key).
... remember to repair permissions on os x (disk utility, first aid)
helps a whole load, as does having BSD installed...
How about this. I have done everything suggested in this thread... and yet cannot get things to connect. Before anyone asks, all obvious things are set up correctly. I'm running a Windows 2003 Domain Controller and the share is located on the domain controller itself. I've decided to lock things down AFTER I get things working right so the share is with the "everyone" group with all permissions and security is also "everyone" group with all permissions. I've created a "macintosh short" name acount on the Win2k3 machine as well as a long name account. Even put these accounts in Enterprise Admin group just to be sure. Put my Mac computer name into WINS with a static IP. I can see them, they can see me, and I can even connect to other shares on other Windows 2003 computers that are set up as clients (from my mac). But when I try to connect to any properly set-up share on the Domain Controller I get an "error code -5000"
Performing a search on Apple provided no results as to what the error code stands for. Also, if I setup appleshare on the Win2k Domain Controller and create and Apple spacific share, MacOS X doesn't connect to it as it should.
Someone please give me any advise (besides the obvious "trash MS" crap). Thnx.
"It would also be easy if the Mac handled SMB properly, and perhaps also didnt give some stupid ass error that you have to piss around with trying to find out what it means.
Then we have the stupid fuck Mac lusers who no matter what, will NOT accept critisism of the Holy Platform Macintosh itself.
It's got a LOT of fucking problems - get over it and accept some fucking critisism assholes."
lighten up, francis.
I had some great luck today. I continually got the error -47 until I did this. Turned off sharing on the XP computer. Then renamed the root drive. Then turned sharing back on in XP. Then i simply went to "connect to server" and poof! no problem mounting the root. FYI.
I got around this error by deleting my WinXP account, then re-creating it. Definitely a WinXP problem, I'd say.
And yes, OS X has problems - as does every platform.
i find it hilarious that os X and linux/unix use samba (same OS platforms acutally), but they don't talk properly ...
just wonderful when you know its faster to transport a 100MB file across the network instead of by a CD which you wont even fill
....so much for trying.
Hey guys
I too was getting the error -47 with my os x.2.8 while trying to connect to a share on my win2k pro machine. I got this error only after I had connected to my first share, and then went back and tried to also connect to a seccond. I tried some of the suggestions and still nothing.
It wasnt until I realized that the share I was trying to connect to was actually my cd-rom drive, that did not have a cd in it. so i shared out my other hd on the win2k machine, tried to connect and (as stated above) POOF! it connected
I too, will add that it os x would make life easier if ti had REAL error messages, rather then "An error has occured. -47"
a better example of os x error messages is better put by Jay donaldson. Check it out.
http://www.weaselcircus.com/funpages/clown-tech-support.shtml
THANKS! Rick Butzberger's post did the trick, I added my Mac name to the Win2k "users" (Start: Settings: Network & Dialup Connections: Incoming Connections: Users). That did it, and I was able to log into my Mac and transfer files into my PC. HoRAY!!!
On an OS X 10.2 -> Redhat Linux 9 setup the trick was using no username or password. It connects every time now. DOH!
-Note Macs ARE better then PC's Ive had like 7 PC's and 6 of them broke within the first week of using them, 3 of them where modern PC shit and the lucky one had a messed up Hardrive= HP sucks, Gateway sucks. IBM has probolems but now they got Linux (yesss!) I recently had an error -47 to but wanna know what? PC's dont tell you they have an error they just grin and say "can do" then ask themselfs "why cant I do this?" and the comp never tells you... and I can file share with PC's no probolom, the error turned out to be some BBedit thing..
Correction: It was a filesharing error but it came from the PC end it only showed up on the mac side
This thread's 2 years old but for all the future readers:
To people discussing Macs versus PCs:
You're dumb.
Get off my internet.
Posted by: James Gibson | April 15, 2004 6:35 AM
I know this post is old but maybe someone may still look!
I REALLY DOUBT YOU HAVE PURCHASED 7 PC's and 6 broke in a week.. maybe your just retarded and dont know what the hell your doing..
I have been a cerified professional for quite some time now.. I've worked on many systems and it doesn't matter what OS you have everyone does different things with thier computers.. causing different types of problems.. Most people assume they are the grand wizards and try things they shouldn't on thier computers. Also hardware fails from time to time.. It doesn't matter if its a cheap ass stereo from walmart or the most expensive MAC you can buy..chances are its not going to last forever..
If you want a solid free standing tower i suggest building a PC.. AMD is responsible for helping IBM build your precious G4 - G5 processors..also....IBM has been partners with MAC for years.. You should do your research before you boast
Fish:
-Note Macs ARE better then PC's Ive had like 7 PC's and 6 of them broke within the first week of using them, 3 of them where modern PC shit and the lucky one had a messed up Hardrive= HP sucks, Gateway sucks. IBM has probolems but now they got Linux (yesss!) I recently had an error -47 to but wanna know what? PC's dont tell you they have an error they just grin and say "can do" then ask themselfs "why cant I do this?" and the comp never tells you... and I can file share with PC's no probolom, the error turned out to be some BBedit thing..