GUI to simplify my Mac speaking to a Linux server

Hi everyone,
I've managed to communicate successfully with Amazon Elastic Cloud Linux servers
through the secure shell.
My aim is to use the servers as a render farm. I don't just need to move files
between my Mac and the Linux server but I also need to install appliactions and
manage the servers as part of my network.
Is there any graphic interface remote-desktop style client that you recommend?
Would make life much easier as I'm not terribly skilled with the command line.
Best Wishes
El

I have no idea if this would work with the cloud server, but No Machine has a free client/server system that would provide you with a remote desktop environment in a local window over ssh. You'll need to install the NX client on the server via CLI, and the client on your local machine. http://www.nomachine.com/download.php
Many file browsers, particularly linux file browsers, can be set up to communicate over ssh as well. This enables drag and drop file transfers. For example, here is a guide for using Nautilus over ssh: http://linuxers.org/article/how-connect-over-ssh-using-nautilusfile-manager

Similar Messages

How to make mac speak when logging on or waking up

hi, i was wondring how you make your mac speak to you and say welcome or hello everytime you log on or wake it up.
if anybody knows, plesae help.
Thanks!

A login greeting is simple. Make a small application with Automator:
1. Choose Application from the Automator template.
2. Add one action: Run Shell Script. In this action, replace cat with say welcome.
Save the application and store it somewhere. (The Applications folder is a good choice.)
Open System Preferences, choose Accounts, then select the account you want to target. In that account, select Login Items. Drag your new application to the login item window to create a link to the file. Close System Preferences.
Each time that you login to that account, the application will run and the Mac will say "Welcome." Once it becomes annoying, return to the Login Items to remove the link to your application.
A spoken wake-up message is trickier, but it can be done. See these discussions: https://discussions.apple.com/message/3240458 and http://hints.macworld.com/article.php?story=20060908113605812, then get a copy of SleepWatcher, http://www.bernhard-baehr.de/.

Common Configurations for Mac mini (w/ OS X Server)

I am interested in buying the lastest Mac mini with OS X Server installed. I would like to get some recommendations on "reading material" on the most common configuration(s) for home use. Thank you in advance for the assistance!

Hello,
http://krypted.com/mac-os-x-server/a-guide-to-using-mac-os-x-server-10-8/
http://abottlerocket.net/2012/08/os-x-10-8-server-tutorials/
http://arstechnica.com/apple/2012/07/the-server-simplified-a-power-users-guide-t o-os-x-server/

How do I add my phone's Wi-Fi Mac address to my home server so that I can use my home Wi-Fi with my phone?

Hello. I am using an Android cell phone and, though the phone sees my home server name and accepts my password, it won't connect. I understand that I may have to add my phone's Wi-Fi Mac address to my home server in order for it to allow my phone access, but I have no idea how I might do that. Could someone help me with this? Thank you.

Tdalso wrote:
How do I add a phone number so I can use either my US or Canadian number (depending on where I am) with iMessage and Facetime on both my iPhones?
You need to log out of iMessage and Facetime, make sure your number is correct in Settings/General/About, then log back in again to send a new activation request.

Mac Mini as a Media Server

I'm debating between Mac Mini and Apple TV. My wife and I are making some final decisions about which we want to go with. And she wants my decision quickly so she can pick up an Apple TV before Christmas if that's what we're deciding on. However, I'm seriously leaning towards saving up for a Mac Mini as a home media server, to buy sometime next year.
But I have several final questions I need clarity on. Hopefully someone here can answer all or even just a few of these questions. I've been to three Apple stores, and they're all technologically clueless, not to mention trained to avoid discussing Mac Mini as a media server product.
1. Can I get a Mini DVI to HDTV adapter, so I can use HDTV with the Mac Mini?
2. Can I upgrade the hard drive of a Mac Mini through an authorized service center without voiding an Apple TV warranty? Apple says they won't do it.
3. Anything Apple TV’s software can do, I can do directly with Front Row and iTunes using the Mac Mini, right? My understanding is that Apple TV is essentially a modified Front Row.
4. NetFlix cannot be streamed with Apple TV without hacking it with Boxee or something, correct? (Which, presumably, also voids the warranty?) I know Mac Mini can stream Netflix through a Microsoft Silverlight component.
5. I know I can always use screen sharing with the Mac Mini and my MacBook Pro so that I can control the mini without having to connect a keyboard and mouse. But can I also use the television (a 42” widescreen plasma) as a monitor if I have a bluetooth keyboard and mouse connected to the Mini? Does the OS actually adapt to the TV screen correctly? The last time I hooked up my MBP to a TV, it would cut off my menu bar, blow up the size of fonts, or I'd have to reduce the resolution significantly, making the OS appear incredibly small on the huge TV!
6. To use the TV as a monitor, I assume I would need an adapter that converts the Mini DisplayPort to VGA or HDTV or something or another?
7. Is there any way I can use a Mac Mini as a DVR for something playing on the television, or will I still need to get a DVR box from my cable company or Tivo?
8. With Mac Mini, can I stream music from iTunes libraries on another computer? (An iMac PowerPC G5 running Tiger, and a MacBook Pro running Snow Leopard; both have separate iTunes libraries as they each have an iPod or iPhone that syncs with them; the MBP/iPhone is mine, and the iMac/iPod my wife's.)
9. If Apple ever gets around to building a Blu-Ray DVD player for their systems, I assume the DVD player in the Mini is not replaceable?
10. Is it my imagination, or does the $999 Mac Mini not actually include a *built-in* DVD player??
11. Is there any meaningful performance difference in audio/video playback between a Mini vs. an Apple TV? Better or worse for either? I’m particularly concerned with bad/choppy playback of both streamed movies (from Netflix or the iTunes Store), and locally stored movies (purchased from iTunes Store).
12. I currently don’t have any speakers or sound systems, but will probably add one some day. Sound currently just plays through the relatively decent built-in speakers of the television. With a Mac Mini, will volume be controlled through the Mini, or through my television?
13. Lastly, are there any remote control options for the Mac Mini? Or, at the least, an app I can put on my iPhone to control the Mac Mini? i.e. remote for DVD control (accessing the DVD menu, changing chapters, rewind/ffwd, and so on.)
Many, many thanks and happy holidays to all...
Dan

Hi- I'll have a go at your list...
1. Yes. Belkin sells one. There are cheaper alternatives that work just as well.
2. If you order from Apple online store, they can bump up the gigs for you, and keep the warranty intact.
3. Yes, and perhaps better, with programs like Plex and VLC.
4. Correct, but the 'hack' is easily removed, with no one knowing that you actually did it, should you need to send it in for service.
5. Absolutely! I've got my mini connected to a 46' Sony Bravia TV, and am using it to write this post right now. Running at a full 1080p, and loving it.
6.The mini comes with a mini-dvi to dvi adaptor. You will need to buy a DVI to HDMI cable (as I mentioned in #1 above, Belkin makes one, and you can find alternatives for around $5 on the net.
7.I believe you will need some extra gear for this. The Apple TV also cant do this. It IS possible with a mini, though, and I believe impossible with an Apple TV,
8. Yes. I am also doing that at this very moment- With home sharing turned on, I am streaming my itunes library from the iMac G5 in the other room.
9. Not without voiding your warranty.
10.That is correct. The server version of the Mac Mini does NOT have a superdrive.
11. No choppiness on my 2.26 gHz Mini with 4gb of ram, running a full 1080p on 46' TV
12. If you connect via optical digital, sound volume is controlled by the equipment you have connected to it. If you connect via analog, the Mini controls the volume.
13.Air Mouse Pro is the iPhone app you should look at. There are others, but that will allow you to use your iPhone to control a whole lot. There are more advanced options like Jaadu as well
Good luck

I have a Mac on my home network and also a Systemline music server on same network. My PC was able to find the server but my MAC cannot. I can ping the server from the mac, but cannot actually connect . Also can't add the mac as a location from server

I have a Mac on my home network and also a Systemline music server on same network. My PC was able to find the server but my MAC cannot. I can ping the server from the mac, but cannot actually connect . Also can't add the mac as a location from server, despite following the Systemline instructions that impy this can be done.
Can anyone please advise what I am doing wrong?

Hi LowLuster
Thanks for reply. I am not an expert on these sharing protocols but I think I have turned on SMB sharing but still wont connect. I tried adding netwrik drive by using cntrl K in finder and using smb\\network address but nothing. It is driving me mad!!

HT2798 I have a Mac OS 10.6.8 server in my classroom that I have networked to each student's account. How do I create a folder that allows them to place their finished assignments in it, but does not allow them to go in and remove anything from that fold

I have a Mac OS 10.6.8 server in my classroom that I have networked to student accounts on the iMacs in the room. How do I create a folder that allows studnts to place their finished assignments in it, but does not allow them to go in and remove anything from that folder?

You want a "Drop Box" style folder. You should be able to achieve this by creating a folder and giving it permissions similar to the "Drop Box" folder in your users Public Folder (i.e. write only permissions.)

Mac OS 10.6 Print Server slow performance to Xerox Phaser 3600

Hi,
I have a client who has numberous printers captured on a Mac OS X 10.6 Server with print services running which works fine with every printer except for a Xerox Phaser 3600 (small A4 mono postscript printer) in that print jobs sent to it via the print server take upto 5 minutes to printer. If the client computers print direct then it is fine and very speedy.
Below is some more detail and any help or suggestions with this would be greatly appreciates.
• Printer server is a MacMini running Mac OS X Server 10.6.8 v1.1
• Xerox 3600 printer is a small A4 mono postscript printer.
• Printing direct to printer is instant, via the print server can take up to 5 minutes.
• The print server has various other printers setup and they are not experiencing the same performance problem.
• The print server is using the LPD protocol but they have tried the IPP protocol and again it is slow.
• When they send a job to print it remains in the users local print monitor and the servers print monitor for up to 5 minutes.
• The Xerox printer is running the latest firmware update.
• The print server is using a Xerox downloaded driver as opposed to one of Apple OS shipped drivers.
• Checked Xerox compatibility list and this printer is fully supported in 32bit and 64bit applications.
• Restarted printer.
• Test jobs have been small TextEdit plain text tests.
Thanks in advance
Anton

Try this:
https://discussions.apple.com/message/15518965#15518965

Mac Mini 2009 vs Leopard Server

Hi all...
I am hoping to get to the bottom of this asap, as I am looking forward to just getting on with things.
The issue is installation of Mac OS X Leopard Server 10.4 on a Mac Mini (Early 2009)
First of all.... Yes I have read the *Article HT3479* http://support.apple.com/kb/HT3479 and yes it allows you too boot your mini, however....
When you go through the installation process and are entering your information, there are several key steps missing from the interview[Server Assistant]. The main question missing is, "What type of installation" Standard, workgroup or advanced.
Another key set of questions missing is Network Setup.
So suffice to say the HT3479 does not address the issue i am experiencing.
Here are the methods I have attempted to use to install Server on this mini...
HT3479. {The result is that I can not run Server Preferences... Apparently the computer is in advanced mode and can not be reverted to standard}
The above method has been tried in the following examples...
* Install Mac OS X Client (10.5.6 from client disk)
+ Apply updates (at the time it was pre 10.5.7 so up to and including all updates to that time10.5.6)
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
* Install Mac OS X Client (10.5.6 from client disk)
+ Don't apply updates
+ Run Server installation from 10.5.4 Server Disk
+ Apply patches before rebooting
+ Run through shorted setup questions (See above)
+ check for updates before launching anything
I tried the above methods several times having no success
I contacted Apple support where I was asked to just try it again! and was told that nobody else was having these issues.
Great... 60Gb download capped reached so I had to wait for this month to continue.
10.5.7 update was released recently, so i thought I may be in luck.
So this month I have tried the above methods several times with the same outcomes.
In desperation I tried the following method...
Boot the Mac Mini in Target Disk Mode and running installation from an iMac targeting the disk in the mac mini. {The result is that during Boot up and Shut down verbose mode is invoked and there are numerous error messages in the log files, secondly I am experiencing several issues with DNS names etc.... won't accept SERVERNAME.local}
Anyway, this method gave me the most joy but still far from ideal.
Seemingly unfair it let me glimpse what leopard server can do, and yes i like what i see, but I really need to be able to install leopard server normally and have no issues.
*Hardware Configuration*.
Mac Mini (Early 2009) A1283 (2.0\1X1G\120\SD\AP\BT)
Upgraded RAM from 1GB to 4 GB (yes it works fine, full hardware test performed)
Upgraded HDD from 120GB to 320GB 7200 rpm (Caviar Black)
Samsung 22" monitor
Apple Keyboard (Aluminium with keypad) A1243
Apple Mightymouse A1152
Network
ADSL modem PPPOE
Apple Airport Extreme
Wired direct from rear of AEBS to Mac Mini
AEBS setup in DHCP, but reserved IP address for Mac Mini's Mac Address
Software
Mac OS X Server Version 10.5.4 [0Z691-6214-A] (Full retail version)
Mac OS X 10.5.6 Disk version 1.0 [2Z691-6344-A]
I am sure that others are experiencing the same issue, as many have listed similar issues to the above, however many are open ended with no resolution. I hope that if a solution is found or it is determined that there is an issue that news can be posted by apple so others are better informed before investing money in both products hoping to achieve a working network server.

I recently purchased a Mac Mini 320 GB model and OS X Server (Leopard). Before I purchased them I asked a couple of the Genius guys if I could run OS X Server normally on one of the new 320GB Minis? And the concensus among several Apple Store employees, was that yes, there should be no problem whatsoever...
So I bought the pair, and went through the install process numerous times, and was never able to get the standard installation until I resorted to dire measures which I have outlined below.
I tried to boot from OS X Server 10.5.4 on several machines at the Apple Store, and it does not boot any of the new machines (as of 2009.06.02). The normal install (use the os x server disk to boot) works perfect on an iMac 2.4GHz machine, and on a G4 Mirrored Drive machine, and on both of these machines the process is simple. Pop in the os x server disk, go get a sandwich, come back, answer a few questions, you are up and running, and life is great. It doesn't get any better...
The problem with the newer machines is that you must install the standard os x, get all the updates, insert os x server disk, and install os x server. The unfortunate part is that by the time you install OS X Server several items have already been set, OS X Server senses this and skips about 17 screens that allow for {"standard", "workgroup", "enterprise"} setup, and goes right into the "enterprise" mode.
One of the big conveniences with the standard setup is that quite a few things are created for you. Once you use the "standard" setup you can promote the installation to the "enterprise" mode by opening it with "Server Admin" which provides infinitely more control, but using "standard" setup to start with simplifies life considerably.
If you figure out how to do the "standard" install bear in mind that when it asks you for your administrative user account info it really wants :
name : Directory Admin
shortname : diradmin
password : astrongpassword
This will allow you to go from LOCAL to LDAPv3/127.0.0.1 when using Workgroup Manager
When it asks if you want add more users you can add one user, the "Local Admin" :
name : Local Admin
shortname : localadmin
password : astrongpassword (you will have to reset this password after you login as diradmin)
You can reset the "Local Admin" password via "System Preferences ---> Accounts"
and you can create the other users via the Workgroup Manager ---> LDAPv3/127.0.0.1 domain once you get DNS and Open Directory working.
if you use "standard" or "enterprise" the first thing to setup is DNS, everything else depends on DNS being configured correctly. "standard" really shines here because it won't let you screw up DNS.
You will need private DNS even if you have a provider handle public DNS for you.
If you are using standard you will be asked for, and can enter something like the following :
domain : crystal-palace.mac.private
machine : crystal-palace
if you are doing the "enterprise" mode you will also have to enter crystal-palace.mac.private in one more field,
Each machine will have a fixed PRIVATE IP address in the form of "192.168.1.n" and a "Computer Name" that was unique within the ZONE (the group of machines) via "System Preferences ---> Sharing".
Once you switch to the "enterprise" mode you can add more machines (using the "Computer Name" above) with their respective private ip addresses.
If you are using the "enterprise" mode, You want to setup Open Directory initially as "standalone", once that is working promote it to "Directory Master" via the "Settings" Tab. If you are using the "standard" mode, the Open Directory is setup automatically as "Directory Master" but there doesn't seem to be any way to add to the DNS, I think you have to use "Directory Utility" to do this. But if you've gotten this far it is easier to promote the setup mode to "enterprise" with "Server Admin".
I have a 1TB drive partitioned into 8 logical drives , the first seven standard partitions are named BUP_1 through BUP_7 and are provide 93 GB each. They are setup as test drives. The last partition is named TM_1 which is used for Time Machine backups and it provides close to 280 GB of backup storage.
On the first partition, I installed OS X 10.5.7 along with some basic applications that I normally use. I then created a dmg installer that I saved to TM_1 using disk utility and used that to install the image on the remaining six partitions (BUP_2 ... BUP_7).
The seven standard partitions then have OS X 10.5.7, which I basically use as test drives. It is here that I attempted different things trying to get this to be a simple deal. If one attempt didn't work I moved on to the next partition...
The BUP_n already have USERNAME setup as localadmin, not admin CHECK step ( 4 ) below. Also note that the dscl commands all have a dot following them.
Steps that worked for me, that allowed me to select the setup mode for os x server.
( 1 ) Boot mac into single user mode by holding down (CMD-S) during startup until you see text scrolling on the screen.
if the text on the screen stops, and you don't get the "root # " cursor, you may have to hit return once in order to get it. Once you get the root cursor you will need to enter the following commands very carefully. On the paths you can type part of the path and hit tab for auto completion. Everything is case sensitive...
NOTICE that USERNAME needs to be substituted with the correct shortname from step ( 4 ) in steps ( 6 ), ( 7 ) and ( 8 )
( 2 ) $ mount -uw /
( 3 ) $ /bin/launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist &
( 4 ) $ dscl . -list /Users
( 5 ) $ rm -R /Library/Preferences/
( 6 ) $ rm -R /Users/USERNAME/
( 7 ) $ dscl . -delete /Users/USERNAME
( 8 ) $ dscl . -delete /Groups/admin GroupMembership USERNAME
( 9 ) $ rm /var/db/.AppleSetupDone
( 10 ) $ rm -R /var/db/dslocal
( 11 ) $ mkdir -p /var/db/dslocal/nodes
( 12 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
( 13 ) $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
( 14 ) $ passwd
( 15 A) $ shutdown -h now (if you want to reboot outside of single user mode)
OR
( 15 B) $ exit (if you want to continue booting in single user mode)
I think that to make this an easy install, there should be a small script from Apple that you can run once OS X, and OS X Server are installed, and updated, that reset everything to pristine, so that after running the script everything that needs to be removed, or reset is done so that you can go through the normal 17 screens that allow for simple setup of OS X Server, just like if you had been able to boot from the OS X Server disk.
The answer I got from Apple Support is that when new machines come out it takes a while to get the correct drivers and release an installer disk for OS X Server. The unfortunate part is that there is no simple way to allow the installer to select which mode they need for the particular installation. They are forced to take the "enterprise" mode...
I am not SURE whether the steps I have outlined above cover everything, that is why I am suggesting that if would be far more accurate if Apple provided an installer script when they have NON_BOOTABLE versions of OS X Server Installer.
After three weeks and about 150 hours worth of work, I finally gave up and took the Mac Mini and OS X Server back and bought another iMac 24. Whenever a newer version OS X Server that is bootable on the newer machines comes out, I will get it another shot...
The guy I dealt with at the Apple Store kept saying, it works, you're just not installing it correctly. He also said "I've installed OS X Server on a Mini". But everytime I asked him, "Was it a new new Mini?" and he would respond, "Well, NO!". I also asked him "Were you able to boot the Mini from the the disk ?", he responded "YES!"
I ran into some other issues, for example one night I shutdown the server, and the next morning none of the passwords would work, not even the root password. So I came up with the following, hope this helps.
PROBLEM :
This morning for some reason the Mac Mini would not allow me to log in, neither as the Local Admin, nor as the System Admin. The database containing the login info must have become corrupted.
FIRST LEVEL REPAIR ATTEMPT
I started the machine using the Apple Install DVD, holding the "C" key to force the CD to boot
Once the installer screen came up, hit return and select :
( 1 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Permissions
( 2 ) Menu Utilities -> Disk Utility -> Select the Drive -> Repair Disk
( 3 ) Quit out of Disk Utility...
( 4 ) Menu Utilities -> Reset Password
( a ) Reset the password for the root user
( b ) Reset the password for the local admin user.
( 5 ) Quit out of Reset Password...
( 2 ) Menu Utilities -> Startup Disk
( 6 ) Select the correct disk to use for re-start.
( 7 ) Re-Start
( 8 ) I tried this several times, but could never get the new passwords to work after re-booting.
There must have still been some corruption in the database.
SECOND LEVEL REPAIR ATTEMPT
( 10 ) reboot and to hold the CMD-S to boot into the single user mode.
At the root prompt, type in the following commands. I might have to hit return, if there is a white cursor that appears to be hung up waiting for input, just hit return, then you should see the root prompt.
First try :
( 11 ) root # fsck -f
( 12 ) root # mount -uw
( 13 ) root # passwd
( 14 ) root # exit
( 15 ) when the login dialog appears try to login as root
( 16 ) if you can login, go to :
( a ) System Preferences -> Accounts and reset the password for the Local User in question.
ELSE
( b ) Go to step ( 20 ) below
THIRD LEVEL REPAIR ATTEMPT
This is the command set to reset the local DB on the server
20. $ reboot and to hold the CMD-S to boot into the single user mode.
21. $ mount -uw /
22. $ mv /var/db/dslocal /var/db/dslocal.old
23. $ mkdir -p /var/db/dslocal/nodes
24. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/Default /var/db/dslocal/nodes/
25. $ cp -Rp /System/Library/DirectoryServices/DefaultLocalDB/dsmappings /var/db/dslocal/
26. $ passwd
FOURTH LEVEL REPAIR ATTEMPT
( 31 ) Shutdown the machine with the problem( we will call it the pm for problem machine)
( 32 ) attach a firewire cable to the pm on one end
( 33 ) attach the other end of the firewire cable to a good machine (call it gm)
In my case the gm uses firewire 400, and the pm uses firewire 800, so I had to get a cable that had firewire 400 on one end, and firewire 800 on the other,
( 34 ) start up the pm while holding down the "T" key until you see a large image floating around the pm screen. This put the pm into the "TARGET" mode, now it will behave like a drive, and you should see the drive on your gm desktop.
( 35 ) You can now copy anything you need from the pm to the gm.
( 36 ) Make sure you BACKUP anything and everything you want from the pm to the gm
( 37 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X SERVER :
At this point, if nothing else has worked you will have to erase the drive and
( a ) re-install OS X, and
( b ) re-install OS X Server on the pm
( 38 ) IF YOU ARE WORKING ON A MACHINE CONTAINING OS X :
At this point, if nothing else has worked, from the Install DVD you can
( a ) Archive and re-install OS X on the pm
Another interesting thing that has happened several times now, is that I always install standard OS X on the first partition of the disk, and OS X Server on a different partition, and after installing OS X Server the machine would no longer boot from the standard OS X partition. This has happened like four different times, not sure what could be causing this problem. Booting from the install disk and running Disk Utilities to repair the disk (which comes back OK), and repair permissions always comes back with an internal error,and cannot be completed.
I have no clue what could be happening. I always had to reformat the drive and instal OS X all over again.
I have no clue what could be causing this to happen ?

Is PKCS#7 format supported by Mac OS X 10.6 server or above?

Couple of questions on Mac OS X 10.6 server or above.
1) Can a Mac OS X 10.6 server or above version supports PKCS#7 format for SSL certificate installation?
2) If PKCS#7 format is supported, is the file extension .p7b file?
Thank you!
J

Try it. Unfortunately, sometimes certificates can be mis-generated or can become corrupted.
X.509 is the overarching standard, and comprises various formats including PKCS7. I'd usually want a PEM format certificate file, though OS X 10.6 does support various formats. Including PKCS7.
Depending on exactly what you're up to here with OS X and OS X Server and these certificates, there might be Server Admin.app or Server.app service-specific steps required; additional general info here here or here.
If these are your own servers, clients and your own family and friends accessing these systems, then there's no need for a purchased certificate. Self-generated certificates work just as well and are just as secure as purchased certificates (if you have a trusted and secure way to perform the initial load), and — if you're inclined, and want to learn a little about OS X and certificates — you can set up your own certificate authority and load your own root certificate, and then your own client certificates are automatically honored.

Why can't I get my Mac to like the LDAP server?

On Monday I started hammering away at getting the LDAP server setup on the Linux server with openldap. I was able to get a test Mac running Leopard to see the LDAP server and the accounts. The next battle was to get home directories to mount under /home. I was about to do that after finding a working ldif example using automaster and autohome. After that I was able to get the Public share automatically mounted on /Network/Public. Wonderful!
Tuesday I came in thinking that the next battle would be with Samba. Unfortunately, somewhere in powering off the Mac and rebooting it, I lost all the share mounting! It still sees the accounts, but it absolutely will not see the mounts. In trying to figure it out I have wiped the LDAP database and restarted it, I have wiped the test Mac twice, I have made sure the Mac is running the latest updates, and still nothing.
If I go into dscl this is now what I see:
ls Automount/
Record Name Unknown
Record Name Unknown
ls AutomountMap/
Record Name Unknown
Record Name Unknown
cat Mounts/10.110.1.1:\/share\/public/
dsAttrTypeNative:cn: 10.110.1.1:/share/public
dsAttrTypeNative:objectClass: mount top
AppleMetaNodeLocation: /LDAPv3/10.110.1.1
RecordName: 10.110.1.1:/share/public
RecordType: dsRecTypeStandard:Mounts
On the LDAP server, the records look like:
dn: automountMapName=auto_master,ou=mounts,dc=example,dc=com
automountMapName: auto_master
objectClass: top
objectClass: automountMap
dn: automountKey=/home,automountMapName=auto_master,ou=mounts,dc=example,dc=com
objectClass: top
objectClass: automount
automountKey: /home
automountInformation: auto_home
dn: automountMapName=auto_home,ou=mounts,dc=example,dc=com
automountMapName: auto_home
objectClass: top
objectClass: automountMap
dn: automountKey=*,automountMapName=auto_home,ou=mounts,dc=example,dc=com
objectClass: top
objectClass: automount
automountKey: *
automountInformation: 10.110.1.1:/home/&
dn: cn=10.110.1.1:/share/public,ou=mounts,dc=example,dc=com
mountDirectory: /Network/Public
objectClass: mount
objectClass: top
mountType: nfs
cn: 10.110.1.1:/share/public
It looks like for some reason it's either missing entries from the LDAP server, and/or it's ignoring some of the mapping and leaving them out. The Mounts entry is missing the VFSLinkDir which maps to mountDirectory. The Automount stuff is missing the RecordName which maps to automountKey and automountMapName.
What the heck happened? Why does the Mac refuse to see the LDAP server the way it did on Monday?

I am having something similar going on and can't sort out what it is doing:
ldiffs:
dn: automountMapName=auto_master,dc=example,dc=edu
objectClass: top
objectClass: automountMap
automountMapName: auto_master
dn: automountKey=/foo,automountMapName=auto_master,ou=Mounts,dc=soe,dc=ucsc,
dc=edu
objectClass: automount
automountKey: /foo
automountInformation: auto.foo,dc=example,dc=edu -rw,resvport,
hard,intr,nosuid,tcp
Second one:
dn: automountMapName=auto.foo,dc=example,dc=edu
objectClass: top
objectClass: automountMap
automountMapName: auto.foo
dn: automountKey=tstaff,automountMapName=auto.foo,dc=example,dc=edu
objectClass: top
objectClass: automount
automountInformation: fileserver:/export/foo/tstaff
automountKey: tstaff
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 name=tstaff[] map=auto.foo,dc=example,dc=edu opts=rw,resvport,hard,intr,nosuid,tcp path=/foo direct=0
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 getmapent_ds called
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 getmapent_ds: key=[ tstaff ]
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 ds_match called
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 ds_match: key =[ tstaff ]
9/25/09 11:45:25 AM com.apple.automountd[1101] t0xb0289000 ds_match: Searching for tstaff,automountMapName=auto.foo,dc=example,dc=edu
9/25/09 11:45:25 AM automountd[1101] ds_search failed
exiting ...
It seems like it can't find the trigger point tstaff. It is looking for:
ds_match: Searching for tstaff,automountMapName=auto.foo,dc=example,dc=edu
which isn't what the DN is in ldap:
Distinguished Name: automountKey=tstaff,automountMapName=auto.foo,dc=example,dc=edu
any thoughts?
regards,
Derek

Mac OS X and Linux Zeroconf LAN irregularities

Mac OS X and Linux Zeroconf LAN irregularities
I would like to at least understand, if not remedy,
an annoyance in establishing the connection between
my Mac and my Linux box. I have yet to find anything
constructive relative to the issue via the google
shuffle or manual pages. Any thoughts, experiences
and/or further troubleshooting steps would be
appreciated. Thank you.
==============================================
Installation:
PMac G5 running OS X Tiger (10.4.4)
Linux printer is shared with Mac via CUPS,
not classic AppleTalk.
P4 with Debian Etch (testing), kernel 2.6.12-1-686,
Gnome desktop and USB attached printer and scanner.
With netatalk 2.0.3-4 and task-howl (0.9.5-2), which
includes the howl mdnsresponder (0.9.5-2), installed.
Only the netatalk afpd and cnid_metad deamons are
being run.
hardwired ethernet with the Mac and Linux box connected
to a Belkin 4 port router
==============================================
Trials:
If I boot up both my Mac and Linux box:
Linux has autoipd, mDNSResponder and nifd daemons running.
Mac has mDNSResponder and netinfod daemons running (don't
know which others are pertinent to note).
If on my Mac in a Finder pane I click Network -> My Network
-> debian1 -> Connect then I get the message:
AFP connection status
Looking up "debian1.local.."
which times out with the message:
Connection failed - server may not exist blah blah
In can however, on my Mac in the Finder menu bar select
Go -> Connect to Server -> enter afp://192.168.2.48/
(my Linux box) -> enter user and password of shared
directory -> select share to mount; and I have my
connection. If I dismount the share though, within a
session, and try to connect again this method works and
the Finder pane method still does not.
Alternatively, on my Linux box I can run the cli
# /etc/init.d/mdnsresponder restart
Then back on my Mac the Finder pane method of establishing
a connection (that failed above) works as it should.
Further, I can dismount the share and reconnect with this
method any number of times in the same session, and even
reconnect with this method after rebooting only my Mac.
However, if I reboot my Linux box I'm back to Finder menu
bar or mdnsresponder restart reconnect choices.
==============================================
What the above trials tell me is that if I restart
mdnsreaponder then everything is "peachy" until my Linux
box is rebooted. What they do not tell me is if there is
something flakey with mdnsresponder, my Linux installation,
an incompatibility with Tiger, or even some other
interference on either box.
==============================================
Lee C
"Life is judged with all the blindness of life itself."
-- George Santayana
(see Backup::Restore article
http://homepage.mac.com/lee_cullens/Bx3.html )
(see Artworks sampling
http://homepage.mac.com/lee_cullens/Artworks.pdf )

I posted the following to the Debian list for obvious reasons, but I'm also posting it here in the hope that someone might shed some light on my suspicions relative to the Mac log.
The howl-tools portion of my zeroconf installation is being phased
out in favor of the newer Avahi as I understand it. However, Avahi
hasn't made its way down to testing yet so for the time being I'm
trying to make do with howl-tools. The point in my mentioning
this here is that much of the information I find is outdated.
That said, the only thing I've found in the Linux bootup logs yet
(using dmesg) that I recognize is the line
autoipd uses obsolete (PFINET,SOCKPACKET)
So, using autoipd as a starting point for further researching
this issue I found the following
(at http://www.porchdogsoft.com/products/howl/InstallUnix.html )
Ideally, autoipd should run only in the event that the interface has not been statically configured and DHCP fails. Running autoipd this way requires modification to the standard distribution boot scripts for your OS. These modifications vary depending on your version of Linux or FreeBSD. On RedHat Linux, for example, the /sbin/ifup script may be modified to launch autoipd in the event that dhclient fails. On our systems, we added the following line to /sbin/ifup right after dhclient is launched so that autoipd runs whenever DHCP fails:
elif [ -z "`pidof -x dhclient`" ] && [ -z "`pidof -x dhcpcd`" ] && [ -z "`pidof -x pump`" ] && [ -x /usr/local/bin/autopid ] && /usr/local/bin/autoipd -i ${DEVICE}; then echo $"started autoip."
Note that since this change causes "$NUMDEFROUTES" to become zero-length, the subsequent code in /sbin/ifup for fixing the duplicate routes generated by DHCP also gets modified in the howl version of ifup.
You may need to modify your boot scripts differently depending on your platform. We have included the original ifup script for RedHat 9 along with our modified version (howl_ifup) as an example so that you may more easily identify how to modify the boot scripts for your platform.
A lot of Greek to me but I did look in /etc/init.d and found
the autoipd script which is the normal boilerplate (same as all
the others with autoipd substituted for the daemon name).
Even if I felt comfortable adding the above in the
/etc/init.d/autoipd script, I have no idea whether it would be
dealt with after dhclient.
I also found in the Mac system log after a reboot:
Jan 26 02:22:48 slpmacg5 mDNSResponder: Adding browse domain local.
Jan 26 02:22:48 slpmacg5 configd[33]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jan 26 02:22:48 slpmacg5 configd[33]: posting notification com.apple.system.config.network_change
Jan 26 02:22:48 slpmacg5 lookupd[80]: lookupd (version 369.2) starting - Thu Jan 26 02:22:48 2006
Jan 26 02:22:49 slpmacg5 configd[33]: target=enable-network: disabled
Jan 26 02:22:50 slpmacg5 configd[33]: AppleTalk startup complete
Jan 26 02:23:59 slpmacg5 automount[148]: NSLXResolveDNS will try and resolve [debian1] of type [afpovertcp.tcp.] in location [local.]\n
so I'm thinking (dangerous at my age) that my Mac isn't "discovering"
what it needs until I restart (stop and start) mdnsresponder on my Linux box????
What I'm asking is whether anyone thinks this (autoipd) on Linux is a
likely cause of my described connection annoyance?
If so, is the referenced info applicable to Debian today and how
would one go about applying it?
Or alternately if so, might it make sense to just disable autoipd
startup altogether and how would I best go about that - just something
like update-rc.d autoipd remove????????
Thank you,
Lee C

Mail rules on Mac OS X 10.6 Server

Hi,
can some body help me.
I wold like to create some server mail rules, that should work for all people that have an mail account on server, but i can only create for each member separatly.
I would like to create new folder for junk mail and move there all emails that are marked as junk mail from server.
I'm using an imap mail acounts on my mac os x 10.6.2 server.

You may have more luck with back-end matters if you ask in the Mac OS X Server area.
I presume you've read the information starting on page 36 of the Mail Services Administration guide in the Mac OS X 10.6 Server documentation, and the notes in the appendix in that guide, yes?
Regards.

The past few days my Mail app has started downloading multiple copies of e-mails from all pop servers. This is only happening on my Macbook not other macs. Deleting mail from server does not help. I ran ClamXav found 2 viruses deleted problem continues

opps. Long title there... The past few days my Mail app has started downloading multiple copies of e-mails from all pop servers. This is only happening on my Macbook not other macs. Deleting mail from server does not help. I ran ClamXav found 2 viruses deleted those. Checked for software update and installed suggested downloads. Problem still contintues. Any suggestions?

Folks,
even after having repaired the inbox folder under "properties" a few times, I still had some e-mails where the contents are different from the subject line.
In other words in the inbox there are two e-mails: one with subject line "abc", and another one with subject line "def".
When I display the e-mail with the subject line "abc", the contents are from the e-mail with the subject line "def" in the in-basket.
What else can be done to correct this problem?
Thanks and best regards.
Fred Kunz-Shirzad
Chemin Ronzeures 6A
1297 Founex VD
Switzerland
[email protected]

To Intel 64bit based Macs (laptops) may installed Linux(Ubuntu lastest 64bi

To Intel 64bit based Macs (laptops) may installed Linux(Ubuntu lastest 64bit)?

Yes, you can install 64-bit Ubuntu Linux on an Intel Mac.

GUI to simplify my Mac speaking to a Linux server

Similar Messages

Maybe you are looking for