Just to post a follow-up for people who were trying to connect to a standard install of WinServer 2003, and were unable to do so, due to error -5000. I was getting errors every time, regardless of the user settings.
The referenced hint above requires you to downgrade the security settings on the server. Instead, I changed one line in the file /etc/smb.conf/. Change the line that reads:
client ntlmv2 auth = no
client ntlmv2 auth = yes
After making this change, it works again. No need to restart or anything. This may not work for everyone, but it does solve the issue for me.
The iDisk feature of .Mac can be very useful, however it seems to be plauged by slow speeds (I find it impossible to use without the local iDisk turned on) and sync issues (automatic sync causes corrupted files in some apps). Even with auto-syncing off, open/save dialogs and even opening Finder windows can cause a spinning rainbow cursor; sometimes for over a minute.
The problem lies in the fact that the local iDisk (stored in /Volumes/iDisk) has symbolic links (aliases) to folders on the remote iDisk (/Volumes/your_mac.com_name). When OS X lists the local iDisk's contents, info for these folders must be loaded from the remote iDisk, which can take some time. The Open and Save dialogs are particularly bad if they default to a location on the local iDisk, because the column view that displays the files and folders includes the alias folders at the root of the local iDisk.
As some people have noted, the problem gets better after the first incident. This is because OS X is kind enough to cache the remote folder info. However, I have found that the problem can persist and present itself in various ways.
With the new child in the house, I've lately found myself working in many locations at many odd hours of the night. The end result is that my 12" PowerBook is getting a lot of exercise lately, including a lot of hint writing and editing. (And it's also making me yearn for a 15" Core Duo machine; as much as I love travelling with my 12" PB, it's not the ideal machine from which to work remotely within the house. The lack of pixels leads to too much reliance on Exposť to help get things done.)
My Dual G5 desktop runs a local copy of Geeklog, so I do all the previewing and editing of stories from its database on the G5. When working on the PB, I enter the G5's IP address to load the submitted stories, preview my edits, and then publish to the G5. (Later on, I dump the SQL data files from the G5 and upload to the web server to publish the hints.)
I was doing this the other evening when the G5 suddenly stopped serving pages. So I put down the PB, walked over to the den, and found that the G5 had decided it was time for its pre-set "sleep if idle for 30 minutes" timeout. But clearly the machine wasn't idle -- it was serving web pages to the PowerBook. I guess, though, from the system's perspective, this didn't show as activity as far as the sleep schedule was concerned (no mouse movement or screen updates).
I didn't really want to disable sleep on the G5, so after a bit of expermentation, I found the solution: to keep a networked machine awake, you simply have to connect to it via file sharing. On the PowerBook, I mounted my home directory from the G5, and went back to work. Hours later, the G5 was still awake. I unmounted the drive when I was done, and the G5 fell asleep again as scheduled.
I assume there are other tricks to keeping a "non active" networked machine awake (setting a cron task to do something every so many minutes?), but this one worked for me.
I'm currently a student at Davidson College. The school currently protects its network with a program called Cisco Clean
Access. A compulsory client exists for XP machines that enforces all sorts of local policies (like running a virus
scanner) before automatically providing the machine access to the campus network after the user provides their login
name and password.
On non-XP machines, a user has to provide their credentials via a web-based form before access to the network is granted. I have a MacBook Pro, and I've gotten really sick of having to re-login to the campus network (both Ethernet and wifi) via this webform every time my computer goes to sleep or I change locations. So, I've managed to write a bash script that uses curl to log me in through the web forms.
Thanks to some amazing work by macrumors forum member Wombert, I've also found a way to have it activate automatically, any time the campus wifi network SSID is detected. This automation avoids heavy-handed cron jobs by leveraging two OS X features, configd and Kicker.xml. (There's a previous hint here that relies on AppleScript and iCal scheduling.)
Now the script and Kicker.xml transparently log me onto our campus network, and hence the internet, any time my computer senses a preset group of SSIDs. The curl commands are specific to Cisco Clean Access, but they could easily be adapted to other environments where users must login through web forms, making this script potentially
One downside to the script right now is that it stores the username and password in plaintext. Perhaps someone
could make this part more secure with more sophisticated code. Instructions are included in the comments of the
script. To use the script, just copy and paste into a .sh file, and make it executable. You can also see it all marked up at pastebin.com.
After using OSXvnc for a while I installed Apple Remote Desktop client 2.1 because I have two screens. Chicken of the VNC to ARD works great (though slowly) as long as I do not choose 8-bit mode and remember to send a password. That is not the problem. The problem is that I had OSXvnc working over ssh, but ARD added a firewall entry for itself that opens ports 5900 and 3283 every time I start it. This was a general problem for me; I did not like how enabling a service would open ports for it in the firewall, since I forward everything I can over ssh. In 10.3, I had a startup item that would configure ipfw itself, but you are supposed to use launchd in 10.4. So I decided I would figure out how to not have ports open automatically when I start a service.
[kirkmc adds: I had a bit of a problem testing this hint (well, at least verifying the steps; I didn't fully test it). The author mentions expanding "udport" in the plist file in Property List Editor, but I didn't find that key. I tried activating ARD VNC access, and setting a user and password, but the key still didn't show up.
By iChat, I asked Rob if he had it, and indeed he does. I don't know why there is a difference, so if you don't see it, well, I don't know what to suggest. Since this ARD access is a system function - you don't need to have a copy of ARD installed - there's no reason why one Tiger system would have it and another wouldn't.]
My daughter bought a cheap Windows PC a couple of years back to play the online game Final Fantasy XI. The company recently released a game expansion, but the software is on a DVD and her computer does not have a DVD drive. After trying to share the DVD drive from another PC and failing, we gave up on a pure Windows solution.
So we put the DVD in my Mac laptop's drive, and after it mounted, I opened Terminal and created a Unix link in my public directory to the DVD.
ln -s /Volumes/FFXI
Once her PC located the shared drive on my Mac, she could install the software as if the DVD drive was part of her computer.
Here is a hint that may save you some trouble figuring out how to print from your Windows machines to a Mac-connected printer. There have been some really good suggestions on this website, so I tried to put all the info together in one hint (though it's probably still not comprehensive).
I have one desktop PC, one laptop PC, and a Mac mini connected on my home network. My Mac is running the show, and so, my printer is connected via USB to this machine. So my problem was to figure out how to print off the other two PCs to my Canon i960.
The key software you want on your PC to make life good is Bonjour for Windows (it's linked at the bottom right of that page). Get this, and you are gold. When specifing your printer on your Windows machine, do not select your own printer (ie. my Canon i960). Instead, go with Generic Postscript.
Here are some simple steps that I compiled. First install the printer drivers on your PC and Mac. Download and install bonjour on your PC.
On the Mac:
Go to System Preferences and open Print & Fax.
Check to see if your printer is installed (ie. mine shows i960).
Go to the Sharing preferences panel.
Check the following: Windows sharing, and Printer sharing.
On the PC:
Follow the steps for setting up Bonjour.
Once you have found your shared printer on the network and it asks you to specify the driver, go with the Generic Postscript.
And, pretty much at that point, I was printing. Hope this works for you.
Soon after installing the OS X 10.4.6 update, some of us discovered that some of our server volumes were suddenly locked. And some of the folders in these volumes were write locked for no apparent reason.
It didn't take someone too long to come up with a solution -- solutions can be found in Macintouch's Reader Reports, and in this thread on Apple's Discussions boards. However, those are all command line solutions.
As an alternative, here's a little AppleScript that I wrote to make it a little easier for the not-so-techie-geek-types to handle:
set theFolder to ""
set theFolder2 to ""
set theFolder to ¨
(choose folder with prompt "Select a folder to unlock:")
if theFolder is not "" then
set theFolder2 to POSIX path of theFolder
say "Unlocking selected folder."
do shell script ¨
"sudo chflags -R nouchg '" & theFolder2 ¨
& "'" with administrator privileges
I recently had to purchase a new printer, and so I took time to choose one to network. I chose an HP Deskjet 5940. The box said it was compatable with both OS X and XP, and the documentation inside claimed it could be shared on any network.
But I could not convince the iBook and the XP machine to share the printer with each other. Apple said it was the router (D-Link); D-Link said it was the printer (HP); and they said it was my AirPort!
After several weeks of research, I discovered that a Mac quirk with OS X and XP is that OS X will not recognize printer names that have special characters in them (like spaces, underscores, dashes, etc.). This little piece of information would have saved me hours and hours on the phone to the various tech support groups.
After many hours, phone calls, and profanities, I am printing wirelessly using a Linksys WPS54G Print Server. I am printing from a Powerbook G4 running Mac OSX 10.4.5 to an Epson Stylus Photo R320. Here's what worked for me:
Ensure your existing wireless network is operational, i.e. router connected/functional, and computer AirPort card turned on. Plug the Print Server power adapter into the wall outlet. Attach power input to Print Server and wait for power led to glow. Attach printer USB cable to printer input and opposing cable end to Print Server USB port. Wait for USB led and Wireless led to glow.
On your computer, open your Web browser and log into your Print Server. For this application (WPS54G), in the address bar type 192.168.0.11. A login window will appear. Leave "Log In Name" blank and in the password field, type the word admin
Once inside the Print Server, you may see your Print Server's name. It probably corresponds with the Print Server model number, in this case WPS54G (write down the name of your print server).