SL server share mounting not working for 10.7.4 Mac Mini

I'm running about seven Macs on a network with a 10.6.8 Mac Mini server.
The older Macs (PPCs and 10.4.11) mount the share immediately.
Newer Macs recently have had a problem.
My 10.6.8 MBP can mount the share, from a dock icon, but it can take minutes.
Another Mac Mini (10.7.4) now refuses to mount the share manually. It can't make contact with the server share. I've tried via Ethernet and WiFi. It just hangs with Connect to Server.
And yet, it has no problem with the iCal server running on the server.
Another older MB and 10.6.8, mounts the share immediately.
Has anyone had newer hardware with 10.7.4 develop server connection problems?

Hi iToaster,
These were all good tips, and I tried or investigated them.
As it turns out, I noticed my SL Mac server needed a Java and securtiy update.
After installing, mount time on my Lion and SL client Macs was near normal, not minutes. (Again, my older Macs had mounted the server share quickly and normally, when the newer ones did not.)
My suspicion is that a modern OS sensed that the Java and security updates were not in place and took extra time to check the share mount in some manner.
Thank you for your time, experitse and ideas, iToaster!

Similar Messages

Lion Server DNS service not working for locally created zones. Caching working fine.

OS Lion Server DNS service not working for local zones. Was fine under Snow leopard server but Lion server upgrade has severely broken my DNS and web sites. Zones look fine under Server Admin but keep getting "query failed (SERVFAIL) for xxxx at /SourceCache/bind9/bind9-42/bind9/bin/named/query.c:3921" in the logs. BTW - Server Admin cant seem to see the log file either.
Surely someone actually tested that DNS still worked on Lion?

I upgraded from Snow Leopard Server to Lion Server on day 01. I hit the same issue where, after the upgrade, my Lion Server stopped serving names for my private local domain.
I finally took a few minutes to figure out what was wrong. After turning on debug logging and looking through the logs, I found my particular issue, now resolved.
The issue I had was, when the domain initially was setup when I installed Snow Leopard Server, for some reason it created a zone just for the server (in my case, something like zone "s-01.mydomain.priv"), and a separate zone for all the other machines (zone "mydomain.priv", containing all the private IPs for my local domain). I never messed with it because it worked, but generally I would have put all of them in the same zone.
My zone "mydomain.priv" had a nameserver and mail exchanger entry for my server, s-01.mydomain.priv. I could see this in the Server Admin app on the DNS bubble, Zones tab, mydomain.priv selected, and the General Info panel. This was fine in Snow Leopard. This was failing the zone load in the updated bind for Lion Server, though. The issue was that the "mydomain.priv" zone was referencing the s-01.mydomain.priv server, which was not defined in the "mydomain.priv" zone but rather in the "s-01.mydomain.priv" zone.
My fix:
1. In Server Admin, add the server to the zone "mydomain.priv". I put an A record (Add Machine) in the "mydomain.priv" zone for my server named s-01.mydomain.priv.
2. shut down DNS on the OS X Lion Server (hit the Stop DNS button on Server Admin).
3. edit /etc/named.conf by hand, removing the specialized zones that contianed just the server. In this case, it would be the section titled 'zone "s-01.mydomain.priv"' and the section titled 'zone "3.10.1.10.in-addr.arpa"'. Your in-addr.arpa zone name will change based on whatever your server IP address was. My internal one happened to have s-01.mydomain.priv mapped to 10.1.10.3.
4. Once the specialized zones for just the server were removed, I started the DNS up again. Instead of serving four zones as it had in OS X Snow Leopard Server, it now servers two zones. And, now, it is resolving my local machines for the mydomain.priv zone.
YMMV. I did note that it wasn't totally necessary to do step 3, but I never really understood the need for the specialized domain, and keeping it around would have a copy of data that would just confuse things.
Hope that helps. That's been the only hiccup I've noticed updating to OS X Lion Server thus far.

HD Audio is not working in bootcamp windows in mac mini 2012

HD Audio is not working in bootcamp windows in mac mini 2012

Update to the latest bios: https://forum-en.msi.com/index.php?topic=163918.msg1260356#msg1260356 (Follow the guide)
>>Clear CMOS<<
Afterwards update the Intel Management Engine Driver in Windows.
Reboot and afterwards install current Realtek drivers: http://www.msi.com/service/download/driver-22481.html

BFG 8800GTX NOT working for me in my mac pro.

Well Da**it guys. I can NOT get the BFG 8800GTX to work in my mac pro.
The machine will boot but you do not hear the apple chime.
After that it just sits there and makes the cd rom drive click and the hard drives click and spinup as well.
It is NOT a power problem. I even tried an external 550 watt PS and that will not work either.
I even tried the other pcie slots and its a no go...well not sure what to do now. Sigh

Are you trying to get this card to run on your Mac Pro with Bootcamp, or OS X? A PC video card will NOT work under OS X as they are not compatible with the Mac's EFI firmware.
There have been people who have gotten PC video cards to work under Bootcamp, but I believe you still need to have a Mac compatible video card installed, just to get the machine to boot.
If you're trying to get this thing to work with Bootcamp, you may want to post in the Bootcamp forum.
http://discussions.apple.com/forum.jspa?forumID=1165

Graphite base station not working with my Intel Based Mac Mini and iPhone.

My Airport Express died after 2 years of use. I had to resort to plugging in my old but still functioning Graphite Airport base station. Since the set up assisant on my Mac mini does not work with the older base station, I used my G4 400 tower to set it up. I got it working and tested the connection. On to testing my iPhone. It sees the new network. Password is entered and the wifi icon shows full signal strength, but does not connect to the web. Next I try my Mac mini out on the new network and it too sees the network, but does not connect to the web. I double check the older G4 and the connection is still strong and fast. I shut the G4 down thinking that maybe the Graphite can only support one computer at a time, and the Mac mini and iPhone still can't connect to the web. I'm not sure what to do with this one. Is there a setting that I need to use? As far as security goes, the Graphite base station was set up with a WEP password. Any help would be great
Message was edited by: Soriano

I suggest using AirPort Admin Utility (version 4.2) to check the base station settings and change them, if necessary. (AirPort Admin Utility should be able to configure a Graphite base station from a computer running Mac OS X 10.4, even though AirPort Setup Assistant can't.)
In the Network pane of AirPort Admin Utility, please make sure that "Distribute IP addresses" and "Share a single IP address (using DHCP and NAT)" are checked, and that everything else is unchecked. I am assuming that the Graphite is the only router in your local network and that there are no computers connected via Ethernet.
The Access Control pane of AirPort Admin Utility should list either all of the relevant AirPort ID's or nothing. You can find the AirPort ID of an OS X computer by looking at System Preferences>Network>Show:AirPort>AirPort.
The Internet pane of AirPort Admin Utility should be set in accordance with your Internet provider's requirements. Most likely, it should be set to Connect Using:Ethernet and Configure:Using DHCP.
After verifying the settings, power down the computers, base station and cable or DSL modem for a few minutes, then start them up sequentially, leaving time for each to get fully up and running: first the modem, then the base station, and finally the computers.
The network preferences on the Mac Mini and the iPhone are also relevant. I assume that the preferences are unchanged from those that worked with the AirPort Express.
I hope this helps.

Share tool not working for Messages

When I attempt to use the Share tool for a photo in my camera roll, and I select the Messages option, first the message input screen delays for a few seconds. Then after the delay unfreezes and I'm able to type or tap Send, it seems like no message is sent. Because when I check the conversation chain back in the Messages app there is no message for the photo I attempted to share. This isn't supposed to be the case right? I should see the shared photo as part of my Messages history, right? I noticed this problem started occuring last week. I don't recall exactly when I updated to iOS 7.1.1 or if there was any problem immediately after updating.

Thanks... and then for the suggestion to sign out and sign back in. I've already done that though (see #3 in my original post... that's what it meant). And I've already sent a link to the person with the other phone, suggesting she do that too. Also thanks for the point on the MacBook not being able to send SMS. Good point.
That said, yep... I'm sure I'm not trying to send an SMS. Even so, that would at least go in green... right? But we cannot send either SMS or iMessage from this end. When I open a new Message... and type in the contact name... it goes red. Just red. As though it's already unreachable. Even though it's the right number and the right email address. I would at least expect that it would, if she weren't registered to iMessage, be deliverable as an SMS (green)... but no.
Here's the process, if it helps:
I open a new message and type in the address -- it goes red (already a sign of trouble).
Then I try to type in a message anyway. It goes green.
Then I hit send and get back a "Not Delivered" error.
Same on her end.
Now, here's something interesting.... I'm typing to you now on a different machine, running under a different administrator (me) and I've just tried to send a message to the same two recipients. One, my mother-in-law's, works just fine. The other, my sister-in-law's ALSO goes red on my machine.
Hmm.
Question: You say "I would suggest you both go to Settings > Messages > Send & Receive, sign out and sign back in. Also make sure that the addresses that you are trying to reach each other at are listed there."
By this, I'm assuming you only mean that each person's sending and reachable addresses are listed in the settings, right?
I guess it's possible she never set that up (on the other end) but she says she can text fine with everyone except her mom.
On the other hand, why would her email address go red in my new Message window too?

'Share Card' not working for Outlook 2011.

I'm trying to email a contact as an attachment from the Contacts app by using the Share button specifically. I want to send it via Outlook and it gives me the option to within the list. However, upon clicking Share Card with Outlook, all that occurs is a blank new message in Outlook with no .vcf attached. Can't figure out what is causing this to fail, as there are no variables that I can think of that would be getting in the way of this simple procedure.

Contact Microsoft support. Those are MS products. Neither one uses the spell checking facilities built into OS X.

Bluetooth not working for file transfer between Macs

I just got a MacBook Pro, with OS 10.6.1. My desktop is the iMac 2.66Ghz Intel with 10.5.8. I cannot get Bluetooth file transfers to work between the two.
I've got file sharing turned on for both machines. I've got all the frakkin' folders I need to transfer added to the file sharing list and all are set to "read & write" permission for every user I see in the list. Both machines can discover and seemingly connect to each other in Bluetooth.
However, I cannot send files between them; the connection just times out. I turned off the firewall on both machines. I've got file-sharing allowed on both machines. But the Macbook insists on only seeing the "public" folder on my iMac, but won't accept any files from it, and vice versa. I can't see anything on my iMac (and vice versa); I can't browse, I can't send.
I don't want to use the Migration -- I don't want to transfer everything under the sun to the laptop (and why in the WORLD Migration doesn't allow one to pick & choose what you want to migrate is beyond me), just specific files. Using my regular wireless connection, it's going to take over 6 hours. I want to get Bluetooth working -- it's irritating enough that the Firewire ports between my two Macs aren't the same type, so I can't use my existing firewire cable to do it, but this issue with Bluetooth is driving me up the wall.
Any suggestions? I've tried searching this forum, but can't seem to find anything that would fit my specific problem, and all the KB docs I've found, I've followed. HELP!

HI Chris,
Sharing files using Bluetooth
To share files using Bluetooth, you first need to make sure Bluetooth is turned on, and then use Bluetooth File Exchange to send a file.
To turn on Bluetooth:
Choose Apple menu > System Preferences and click Bluetooth.
Select the On checkbox. To allow other Bluetooth enabled devices to “discover” your computer and send files, also select the Discoverable checkbox.
Select “Show Bluetooth status in the menu bar” so you can quickly send files and perform other actions using the Bluetooth status menu in the menu bar.
To send files using Bluetooth:
Choose Send File from the Bluetooth status menu in the menu bar.
If the Bluetooth menu isn’t visible, choose Apple menu > System Preferences, click Bluetooth, and select “Show Bluetooth status in the menu bar.”
In the window that appears, select the file you want to send and click Send.
Select the device you want to send the file to and click Send.
If you don’t see the device you want to send the file to, make sure the device has Bluetooth turned on and is discoverable.
You do not need File Sharing turned on for Bluetooth technology.
Another way to share files between two Macs is How to use Firewire Target Disk Mode
Carolyn

Acrobat 9.0 serial not working for Acrobat XI update (Mac)

The subject line says it all. When I try to run my newly downloaded XI update, it requests a serial number for a qualifying product. I have Acrobat 9.0.0 Pro installed, and when I try to run XI, I get a window reading: "Serial Number you provided is valid, but a qualifying product could not be found on this computer."
Then I manually input the serial (correctly--I've triple checked), select Acrobat Professional 9.0 for Mac in the pull down menu and click "Next." I get an error message saying, "This serial number is not for a qualifying product. Please try another."
What the heck?

start here, http://helpx.adobe.com/creative-suite/kb/error-serial-number-valid-product.html
if that info fails to resolve the problem, contact adobe support https://helpx.adobe.com/contact.html

"Use this mailbox for" not working for Spam on one mac but fine on another

I have Mail running on my Macbook Pro using IMAP. I have a business email account and a personal email account both with the same mail provider. When I create the account it creates a folder under the IMAP folders for Sent, Trash and Spam. I highlight each of these and use the "Use this mailbox for" command to set them for Sent, Trash and Junk respectively. This moves the folders up under the Mailboxes section at the top of mail. Everything is great.
Now, exactly the same on my brand new iMac. When I get to the part about "Use this mailbox for", Sent and Trash work exactly the same as on the Macbook Pro but Spam stubbornly refuses to change and I am left with an extra folder under the IMAP folders.
I am using the same version of OS X, the same version of mail and exactly the same setting in mail preferences. I don't understand why I can't get the Spam folder to be used as Junk? ANyone out there got any ideas?

I have the same problem on my new MBP with Snow Leopard. I have multiple gmail accounts in Mail with IMAP. I can set the Sent/Drafts/Trash mailboxes to be used by Mail. But when I do the same with the Spam mailbox nothing happens at all.
This is really annoying as I now have to go through all of my Spam mailboxes manually to check if there is a false positive. This seems to be a bug in Apple Mail? I also tried to set up all my accounts again but it didn't help, same problem.

Why does double clicking not work in photos on my Mac Mini?

Why can I not open a photo by double clicking my mouse in Photos App?

Has nothing to do with ios6, the last update to the Facebook app did it. Mine has been like that for weeks on ios5.0

Find My Mac not working for a non-admin account

I would appreciate some advice, or comment, on what I perceive is "Find my Mac" not working.
I use a Mac Mini (late 2009) to run my home media; it on 7/24, connected to a drobo drive and is running the latest Mac OX X Lion. I did a complete erase and install of the OS, and the recovery partition IS there.
I use an auto-login account, but with no administrative privileges. There is no monitor, keyboard or mouse connected to it, but in case it gets stolen, I want to find it.
When I log in with an admin account, I can turn on Find My Mac, under icloud prefs. When I relog into the normal user account, this preference is greyed out, and says "Needs administrative authorization".
So, is Find my Mac running, cause I turned it on with an admin account, or not?
If no, how do I make sure it is always running?
thanks

These are the notes of the steps I took which finally got my MBP to appear in FMM:
I clicked on the MBP remove device-> I took the MBP Wi-Fi off line-> I went to iCloud Pref's, unchecked find my Mac-> turned Wi-Fi back on-> went to iCloud pref's re-checked 'Find my Mac'-> went online to iCloud.com, selected the MBP, which had found it's location. I sent a message and sound to the MBP from the Mac mini, which instantly came up on the MBP.
SO, eventually my MBP 'Find my Mac' is working.

Server Shares will not Auto-Mount on Clients

Hi,
When I log onto my network, my server shares do not auto-mount.
Clients are able to log onto network. Connection to server on clients shows a
green light. When I go into finder and try to connect to shares network with
client user name /password it will not open shares. Shares will open with server
password, but I don't want to save server password on the clients.
All other services will setup and work as expected using client username / password.
I'm using Mountain Lion Server 10.8.2 and Mountain Lion Clients 10.8.2.
File sharing is turned on in the MLS Profile. Service access for clients File Sharing is checked.
I have tried restarting server clients.
Any ideas on how to fix this, short of a reinstall?
Thanks,
John

Imagine you want to enter your parents' house. You have a key for your house but it won't work on their locks. They won't give you their key and now you complain you can't get in with your own key. Same thing, server password and client password are two different keys for two different locks.

HT4890 Shared photoStream not working for public share

Shared photoStream not working for public share and keep showing the same url for the first shared stream i have published. this means everytime i try to share to anyone else not using an iphone it comes up with page not found. I have also notice the in first initial public url which was given is the same url keeps showing up everytime i try to make it public. how do i reset or change that url so other public share stream will work. how do i get this to work

I've read some posts from users with a similar problem who were able to fix this by changing the download folder (or just click Change next to Download Folder, then click cancel). Not sure if this will work for you but thought I would pass it along.

OOF not working for mailboxes homed on Exchange 2010 server during migration

Hi There
I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
enable OOF via exchange powershell.
Users homed on the exchange 2013 servers does not have any issues.
The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
in the meantime I'm checking if anyone else had similar issues.
Any pointers will be welcome.

Hi ,
1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
3.Then please un check the proxy settings in browsers and check the same.
4.please use the command to check the auto discover
test-outlookwebservices
Please check the below links also.
http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
Regards
S.Nithyanandham
Thanks S.Nithyanandham

SL server share mounting not working for 10.7.4 Mac Mini

Similar Messages

Maybe you are looking for