Accidental Server Install - No More File Sharing

Hello All,
I was about to install from my iMac to a Mac Pro Snow Leopard Server but I accidentally installed it over my Snow Leopard version. The install didn't ask again and just installed it. Everything worked fine but I didn't want to have Server on my machine so I made a time machine backup and reinstalled snow leopard and reconfigured the system from the time machine backup.
Everything works except file sharing. It is really annoying since no one in my workgroup can connect to me anymore. I tried everything from deleting system preference, checking firewall settings etc. but I can't find a way to get it working again.
I just want to avoid reinstalling the whole system because there is too much to reinstall.
Yes, totally stupid that I installed server but it should ask if one is sure to put it over snow leopard.
Help would be great!
Thanks,
Mik

Functionally, I don't believe so. If you're able to back up and restore your Macs over your LAN using File Sharing then the Time Machine Service in OS X Server won't do you any good.
I use OS X Server and the Time Machine Service for back ups/restore. I know I can restore any Mac client as long as the server (Mac Mini) is up and running. I simply select the network back up while in the Recovery HD of the client, log into it and select the date I want to restore. I don't know how File Sharing works if you have to restore one of your Macs from the Recovery HD.

Similar Messages

Is FTP server better than common file sharing

what is better : ftp server or common file sharing on server
i need to convince the management that ftp server is better than file sharing on server but i need some strong security points.

I agree on DropBox.
In DropBox, Favorite (Star) the files (documents, MP3...) when you are on-line. They will be available when you are off-line. Test access to your files in Airplane mode before you leave home.
To bring the document into an app (e.g., Pages), use 'Open In..'.. the MP3, you can just tap in DropBox.
There are solutions to get files back from different apps to DropBox, but honestly it is probably just easiest to email it to yourself (and then use your Mac to copy the final file back to DropBox for reference purposes).
Have a good vacation.

How do I set up file sharing in Lion Server to work like file sharing in Lion Client?

I've just installed Lion Server on my home iMac to enable remote access via VPN to my home network.
When the iMac was running Lion Client (before the upgrade to server), and when File Sharing was enabled on the iMac; when other Macs on the LAN connected to the iMac via AFP, they were always able to connect to (share) any mounted external volumes (external USB or FireWire drives connected to the iMac). e.g.
Now that I've upgraded to Lion Server, when other Macs on the LAN connected to the iMac via AFP they are only able to connect to (share) the sharepoints listed in the File Sharing pane of Server.app. e.g.
Is there any way to set up File Sharing in Lion Server so that it works the same way as it does in Lion Client with respect to mounted external volumes? i.e. they are automatically shared? I know I can add each volume manually to File Sharing in Server.app but this gets tedious.
Many thanks!

I normally have a Firewall enabled. I recently had to do an erase and install of Lion, followed by a one-by-one re-install of all of my software. One of the first things I did was to set up all of my System Preferences the way I like them; Turning the Firewall on was one of them. Later I noticed it was off and turned it on again. I had already set up sharing and was surprised to see the problem when I turned it back on.
As to why do I think it needs to be on. It is another part of my security layer.

Got Connect to Server to work again, file sharing 4.9 to 10.1.5!!!

Folks:
Have a number of unanswered questions lost on this forum, and been following as many of the threads pertaining to file sharing as possible--and finally pieced some of the suggestions, mostly from BDAqua, together and got the two units to connect. Before this I got "Log In Failed" or "Connection failed" error windows. Haven't had time to actually move files, but I did open some JPEG's from the 10.1 computer in the 10.4.9 . . . what got it working doesn't totally make sense--but it worked.
When I first posted my issue after erase & upgrade from 3.9 to 4.9 BD asked me if I had another User in account to do some testing with--and I said yes, but what will that do? And he said, ah, you could test things . . . wasn't real encouraging--I think I logged into one new account and tried to connect and it FAILed. Went on to the "roll the AppFileServer kext back to 4.8 version--didn't work. Kept whining--eventually everybody stopped replying. Then I saw another comment by BDAqua answering someone about some issue with having the same user name when trying to use File sharing; that was awhile back.
Today--put those ideas together and logged both computers into the other user and then used Connect to Server, entering IP address--got the Log In window--put password in and--IT CONNECTED, but only to a "Drop Box" folder that I didn't have "privileges" to open. Following another thread's idea I changed both of those accounts to "allow user to administer computer" in Acounnts. In Tiger I had to log back into the main account to do that--and then I tried to connect, and that time it worked. The most important thing is having another user name to enter--and then I could get access to the HD of either computer. Still some things to work on--going from the iBook to the iMac I can open all files, going from the iMac back to the iBook I can mount the HD, but some of the original files in my Home folder have red minus's and can't be opened. What was odd is that both of my other user accounts have the same name/password, but I could connect; but couldn't with the main accounts--having the same name/password. When I changed those extra accounts into admin also and then logged back into main accounts--I connected by using the name/password of the OTHER account in the second computer.
The Key is as BD "recalled seeing somewhere" that the User name should be different, so you can use another account on that computer. In Panther it didn't matter if both computers had the same name--in Tiger apparently it does. Hope this helps--took me a lot of messing/time to bring all the details together--1.5 months. A head's up from Apple might have been--nice???
eep
iBook G4, 14, 933 MHz, Mac OS X (10.4.9) iMac G4, 15, 800MHz, (10.1.5)

Rick/BDAq:
Verbosity doesn't really begin to cover it--that was the short version of the process. 1.5 months ago had 15 posts--100 posts later a solution was developed. Don't know if rolling back the kext to 4.8 is needed--won't get a chance to try doing a full install of 4.9 + Security update on my Ext HD to test what is really necessary. Or whether it is necessary to make the New Account an administrator or not; when they connected it was so surprising and so simple. I'd like to find the thread where it shows how to change the original User Name for the admin/computer & see if that is all that is needed. Like all creative people I named my units after me, my name. Now I'd like to change one to be "Johnny" or I'll name it "Tiger" after all the fiddling it's taken to find such a simple solution--I've grown attached to my OS. : - 0
Haven't had the chance to check the link to Hornware--thanks Rick, but Firefox couldn't find the server. BD--thanks for being there, buddy.
eep

Install Tiger with file sharing?

I have an Emac with a cd drive. I realize I can install Tiger via target disk mode with another Mac with dvd capabilities. I can also see how this might be the preferred method.
Is it acceptable/advisable to install with file sharing?

Is it acceptable/advisable to install with file sharing?
Do you mean NetBoot, ARD, or something else?
http://www.peachpit.com/articles/article.aspx?p=445094
http://docs.info.apple.com/article.html?artnum=306051
(Vague reference).
FWTDM will be fastest, surest, easiest.

OS X Server not saving my File Sharing settings

Hi there,
Hoping there is someone out there who can help as there are a few head scratching issues going on!
Basically the main issue I am getting is to do with File Sharing in OSX Server.
I have two raid servers set up with a mac mini server acting as the link to the main network. I use GlobalSan Xtarget to mount the Raids.
I have set up OSX Server primarily so that I can use the VPN function on the Mac Mini, otherwise it is a very simple set up. However, when I attempt to change the settings of my second raid, (As Displayed) clicking ok doesn't save the settings or infact close the window, it just does nothing, with no warning errors as to the reason why. What I am trying to do is remove allow guess users access to this share.
Now your probably thinking why don't I just remove the opportunity for a guest to log into the server, while yes this will work, it's just that I am getting other issues that I am wondering is linked to what is happening In OSX Server.
For instance, I have a Capture One Catalog archive which is supposed to link to a selected folder on my raids. One is for my commercial work, and one for personal. I have a raid for Commercial Work which works completely fine (All the images display and import into the catalog), and a raid for Personal Work (The raid with the file share issues in Server). When attempting to import the images from the Personal Raid, it doesn't recognise them, it knows they are there, but it doesn't recognise it as an image file. However, you can view them fine in Finder.
I thought it was maybe a Sharing and Permisions issue, so I matched the settings from the Commercial Raid with no success. So I am wondering if it is to do with this issue I am having In OSX Server.
To add to these points, I am also getting an Unknown User showing in the User list for the Commercial Raid, not that it seems to be causing a problem, but it is another thing thats happened since migrating the server from 10.8 to 10.9.
Any help will be greatly appreciated!
Thanks in advanced.
Aaron

Ok so I've solved the Capture One Issue, it was due to the / in the Personal/Moving name of the Raid, so that is all fine.
But if anyone does know why server won't save the File Sharing issues, and the issues with the Unknown User, it will still be a great help!
Many thanks,
Aaron

Server Time Machine vs File Sharing TM

For a couple of years I have used file sharing on my Mac Mini to provide Time Machine backup space for the Mac Books in my collection. This has worked well, with multiple hard drives and partitions providing redundant backup space (every Mac has at least two concurrent Time Machine backups, each in different hard drives attached to the MM). I have been examining OS X Server, and am wondering what benefit Server Time Machine service offers over my current arrangement. I can see no functional difference. Is there any?

Functionally, I don't believe so. If you're able to back up and restore your Macs over your LAN using File Sharing then the Time Machine Service in OS X Server won't do you any good.
I use OS X Server and the Time Machine Service for back ups/restore. I know I can restore any Mac client as long as the server (Mac Mini) is up and running. I simply select the network back up while in the Recovery HD of the client, log into it and select the date I want to restore. I don't know how File Sharing works if you have to restore one of your Macs from the Recovery HD.

My office uses windows based computers setup with a server setup. Can an apple server emulate or find compatibility with an apple server or apple computer linked to the server and allow full file sharing and printer sharing with pc's?

I have 11 computers all pc's linked to an old windows server and all used primarily for microsoft office and printer sharing as well as for internet browsing. Can an apple joining the setup cause compatability issues?

HI,
grey-haired IT guy here, old enough to come from the counter culture. I ran (COO, including IT & compliance) a third billion dollar financial institution all on Macs 15 to 20 years ago. All the "experts" had a long list of reasons it would be impossible, and it drove the examiners nuts, but it's only gotten better.
So your benefits are going to be mostly in ease of administration after the learning curve, less aggravating glitches, better overall reliability, and arguably better security. And reductions in cost and improvement in time to implement changes.
In my current environment of mostly dozens of PCs, the moment I let the OS X Server be the domain master controller, the Windows network browser settled down and instantly showed network neighborhoods like it should have. (We may have some forgotten pre-NT machines plugged in somewhere -- this is NOT a financial institution).
Couple anecdotes might explain the feeling of coming in out of the cold: Putting a test copy of a web site from the cloud onto the Mac server, XAMPP or MAMP is pretty much already there. The site has a couple WordPress blogs, and they need .htaccess files, and Apache needs an option set to permit remapping URLs. After much searching far and wide to find why it didn't seem to be working, I found the checkbox right there on Apple's management screens. Much easier than editing .conf from command line. Linux web admins hate it.
Tale # 2: We aren't fully Windows domain controlled -- just using the old network browser. Need to upgrade that, and I Googled quite a while trying to understand what needed to be done to use Apple's Open Directory instead of setting up an Active Directory on Windows -- both SLDAP3. Turns out one reason I couldn't find much is there isn't much to say: it just works. Just join the domain from a Windows machine.
One more and I'll be quiet a bit. We use the Wiki collaboration which is nice enough as far as it goes (no spreadsheets, fatal flaw) and it occupies the server's native web site slot. So the test copy needed to be another site. Easy enough -- site setup is all GUI and works fine, but WordPress could not handle a multiuser blog coming to a non-standard port (other than 80) so I needed a second IP multihomed on the server. How do you do this? Go to Network in the System Prefs, click on the Ethernet interface and select "duplicate". Set your IP address. Done.
In summary a Mac OS X Server is a better server for a Windows shop than Windows Server 200x.
My bottom line for choosing Apple: lower blood pressure. I SHOULD be money. After all is said and done, it's about money. The incredibly more pleasant experience is a free benefit. You'll pay more for better hardware, but way less in time and trouble. And you won't be hounded on a daily basis to update the system. Not that Adobe or Firefox are any better about it on a Mac, but the Apple approach to updates stays in the background.
Think different. Simplify. Focus. Enjoy your work.

Lion Server 10.7.3 file sharing permissions

I'm having really strange issues with Lion Server. Since upgrading to 10.7.3 I no longer have permissions to modify files on Share Points that I was once able to in 10.7.2. When I go to modify certain files or folders I get "The operation can’t be completed because you don’t have permission to modify some items."

Background
Access Control Lists (ACLs) are applied to folders and files to define user (and group) access privileges.
I have setup two Mac mini Servers at our company – one in our Melbourne office and one in our Sydney office. Each file server is made up of the following hardware:
1x Mac mini Server (with Lion Server).
2x Promise Pegasus 12TB (6x2TB) R6 RAID System (thunderbolt) in RAID5 configuration. The two Pegasus unit are mirrored (RAID1) using SoftRAID.
Users and Groups are replicated between the two servers via Open Directory.
The PeachPit book "OS X Lion Server Essentials" is the best book I've found that explains OS X Server services and configuration. It has a good explanation of POSIX and ACLs.
The Problem
It seems there is a bug in Lion Server that causes ACLs be ignored. A couple of times I've managed to fix the problem using these steps:
   1. Remove the share-point.
   2. Setup up the share-point. /Volumes/promiseraid/work
   3. Apply an ACL to a folder.
   5. Propagate the ACL to sub-folders.
When ACLs are not applied to a folder the older POSIX permission define access privileges. With POSIX mechanism the user, group and other access privileges applied to new files and folders is defined in the 'unmask' value. The default 'unmask' value sets file/folder group to read-only access. The upshot is when POSIX mechanism is used and a member of staff creates a file or folder it is read-only to colleagues. System Administrators shouldn't need to change the 'unmask' value – too technical. Apple documentation encourages System Administrators to use ACLs to define access privileges – use ACLs to overcome the limitations of POSIX.
The workarounds I've been considering
Stick with Lion Server, apply POSIX read&write (group and others) permissions to all folders at regular intervals (daily) and wait for Mac Apple to fix the problem.
Abandon Lion Server (10.7) and revert to Snow Leopard Server (10.6).
Abandon Lion Server (10.7) and setup a Microsoft Windows Server solution.
A solution?
Scanning the several threads here I think I discovered a "fix". Mac OS Lion doesn't seem to honour ACLs if
it is a volume is being shared (AFP and/or SMB), or
it a folder at the root level of the volume is being shared (AFP and/or SMB).
However, if the folder being shared is at least one folder deep ACLs seem to be honoured!
    !!! This did not work – ACLs are not honoured !!!!!
    /Volumes/promiseraid
    /Volumes/promiseraid
    /Volumes/promiseraid
    !!! This did not work – ACLs are not honoured !!!!!
    /Volumes/promiseraid/share1
    /Volumes/promiseraid/share2
    /Volumes/promiseraid/share3
    !!! This works – ACLs are honoured !!!!!
    /Volumes/promiseraid/shareditems/share1
    /Volumes/promiseraid/shareditems/share2
    /Volumes/promiseraid/shareditems/share3
Acknowledgement
I should acknowledge gmbion for his time troubleshooting this and reporting his findings to this thread.
A response from Apple
It would be good if Apple could address this limitation with either:
A note from Apple acknowledging this limitation ("undocumented feature") witch advice to not share a volume or a folder at the root level of a volulme. Instead, share a folder at least one level deep; or
Fix Lion Server so that any volume or folder can be shared and ACLs will be honoured.

Mac Mini Server and Time Capsule, File Sharing Issue

Setup:
MacMini Server, Time Capsule, 2 Macs connected.
All Macs use the time capsule to backup.
Problem:
I can't use filesharing from over the internet anymore to connect to my server.
Ports 139 and 548 seem to be reserved for the internal backupdisk of the time capsule.
The port mapping rule gets turned off.
How can i still access my files from the outside ?
If i change the filesharing ports to something else, how can i access it ?
Anybody an idea ?
Thanks in advance.

Hi
+"I can connect to my server using vpn but my workgroup shortcut in the sidebar of finder doesn't work"+
That's about right. Bonjour won't work over VPN unless you work at it. AFP548 has an article on how to achieve it if you want to go to the trouble.
+"Isn't there a way without manually connect using go?"+
You could drop desired share points into the dock. Next time you initiate a VPN connection simply click on the icon in the dock. Works for me every time.
+"Perhaps some tweaking on the vpn server side?"+
None that I'm aware of. Perhaps someone else knows a way?
Tony

Lion Server File Sharing Crashes

We have a brand new Mac Pro (12 core with 64GB of RAM) running OS X Lion Server in a corporate environment. The server is running only file sharing and software update servers, and we have around 40 users who need to be connected over AFP at all times. This company runs 24/7 and we have an XSan environment using an ATTO Celerity 8GB 4 channel fiber card (84EN) along with a 6 port 10GB Ethernet card. The Ethernet card is configured in a link aggregation bond using ports 1-4. The idea is that clients who do not have fiber cards installed on their machines can still connect to the SAN via Ethernet and this file server. They AFP connect to the share, and of course the share is the SAN. It's a single mount point and everyone has read/write access.
The issue is that this machine keeps crashing (multiple times per day) and I cannot find any reason why. Syslog shows nothing of value and I've called into Apple Enterprise Support who also brought nothing to the table.
We initially had SMB and AFP file sharing activated but as soon as a Windows 7 client connected the machine was brought down. So, I disabled SMB via terminal (sudo serveradmin stop smb) and deactivated it via the Server app for the share point). That at least allows the machine to be up for 4-6 hours before crashing again.
This is seemingly the simplest of setups for file sharing and I would've thought that this beast of a machine would be able to handle being a file server without issue for far more than 40 clients. I'm seeing high CPU usage, which Apple support told me was perfectly normal (around 60% on the kernel_task process and around 55% on the AppleFileServer process). It also seems to consume all 64GB of memory, though it shows 60GB as inactive, but at the same time it's paging in and out.
Virtually all of the clients are running Lion (10.7.4), the server itself is running 10.7.4. There are a few ethernet connected clients running 10.6 along with two running 10.5. As I mentioned I disabled SMB so there are no Windows computers connecting to this machine at this time (though it would be nice to get that functionality back if AFP can be stabilized).
None of this makes any sense to me and I'm hoping someone can shed some light on this issue. This company simply cannot be down, especially not multiple times per day. The only way to bring things back and running from a crash is to hard boot the machine via the power button as you cannot perform a restart or a shutdown. Once the machine comes back up everything is back to working order for a few more hours until it happens again.

All the memory is fine. The server rarely if ever goes down when there are only around 10-12 users connected. When there are 20+ users connected and working heavily it goes down often. When I say working heavily, I mean they are transferring huge files to the SAN (100GB+), sometimes 5 at a time per user, and there are a bunch of others who are reading large video files at a minimum of 220MB/sec from the SAN.
Though this worked on Snow Leopard without any issues, Lion just doesn't seem to be able to handle it. The odd thing is, on Snow Leopard there was only a single 1GB ethernet connection to a NAS system, whereas with Lion we have a much more powerful machine with a 6-port 10GB ethernet card and a 4 lane 8GB fiber card to a true SAN. You would think that the newer scenario with Lion would handle far more users with ease.
So far, very disappointing with regards to Lion's file serving performance.

Automatically reset file sharing in Server

Hi everyone.
I have a Mac mini with Server (Mountain Lion) and file sharing enables. When I turn tehe unit on, computers on the same network can't find the shared folders until I turn file sharing off and on again.
Does anyone knows what's happening?
Is there a way to automatically do this (turn off and on)?
Thanks

Everything you can do in the Server.app you can do via the command line. For example, you can setup a launchd script to execute the following commands:
     serveradmin stop afp
     serveradmin start afp
You can find out more about serveradmin via terminal, with the command
     man serveradmin
The problem you describe sounds unfamiliar to me. You should look at the server logs to see why afp is not working.

File Sharing Keeps Crashing on Snow Leopard Server

I use a Snow Leopard mini server running OS 10.6.4. The server works as a file sharing hub for my network. Lately, something strange has been happening. On several occasions, the network file sharing function has suddenly gone dead with no warning -- in other words, open file sharing connections are suddenly cut off, and when I try to re-access the server to reinitiate file sharing, it lists no drives available for browsing.
When I restart the server, the problem seems to resolve itself (temporarily), and the server gives no indications of anything having gone wrong. The other weird part is that this problem is exclusive to Mac systems trying to access the Mac server. In other words, PC computers on my network are still able to connect and share files without any trouble, even after the apparent stall has occurred.
Any ideas? It is getting annoying to have to restart the server every few days. Thanks!

tibbs01 wrote:
I have a Mac Pro, Snow Leopard 10.6.4 and experience a similar problem - Windows clients, XP Vista and 7 alike can not access the server, This was all fine before going to Snow Leopard.
To fix it , I switch SMB sharing off and back on again, then it works fine. This happens several times per day, I am so far unable to detect pattern or even any log entry that might shed light on it. This is a big problem for me, as I have approx 40 windows clients accessing that server and it's shares.
There are so many post all over the internet about SMB and Snow Leopard having problems, Is Apple aware of this , has anyone heard back from them about fixing this ?
Apparently there's a major problem in Snow Leopard using a version of Samba that is not compatible with Windows 7. I think there are workarounds - a search on Google should help.
However, the original poster was complaining of a problem with AFP, which is what I'm having a problem with as well. If anybody has the solution ...

Time Capsule and File Sharing on Server

I am in the process of setting up Server at home. I've run into a snag with using a Time Capsule as my router and backup drive and also enabling file sharing through Server. When adding File Sharing as a service in the Server application, a warning comes up to disable disk sharing at the router before forwarding the ports. The problem is that if I disable disk sharing on the Time Capsule, I can no longer access my Time Capsule drive (for obvious reasons). I was reading another post that discussed enabling disk share from the router and then adding a port for file sharing manually, but that did not seem to work as I cannot remotely access my files.
I am running Server on an iMac which is running Mavericks. The Time Capsule says it's "version 7.6.4". It's a 2TB drive. The iMac is a 2012 system with 1TB drive. I also have a Drobo and a few external drives connected.
I appreciate any advice! Thanks!

If I turn on disk sharing (even without the LAN option) I can select the disk to back up, but then I cannot share files using my server due to the port conflict.
I find this hard to follow.. there is no port conflict on a local lan with sharing.. that is not even possible.
If you have several Macs for instance and set each to share.. they are all able to share.. there is no port conflicts.. You do not need all the devices on different ports because they have different names.
You only get into port conflicts when you have external access turned on.. and are having to port forward. Because the network is identified by a single public IP.. in that case you can port translate but you don't do that in a LAN.
There has to be something screwy in the server version of Mavericks for this to happen.
I am trying to think of way around it.. but I will do a bit of google work first on if others are having issues with latest server version.
What about giving me a few screenshots of the setup...
Network on the server.. and network on the TC ..
And run netstat scan on the server to see the local IP addresses of everything.

File sharing reports too many users connected

SPECS: Mac Mini Core 2 Duo 2 GHz, 2G RAM, Mac OS X 10.6.4. Other users in office also running similar hardware and Mac OS X 10.6.4.
CLARIFICATION: This Mini is used as a file server in a small law office (4 other workstations). It is running Mac OS X Client, not Server. I refer to the machine as "the server" but wanted to be clear the operating system is the same on all stations.
HISTORY & CONFIG: This system was setup in November 2009. It provides simple file sharing storage for a 4-user law office and runs Retrospect (version 8.1.626) to do some local and network backup operations. At the time it was setup, it was also running Now Up-to-Date Server but that program is no longer supported, and it has been removed from the computer (May 31, 2010). In late March 2010, I installed Daylite Server as a replacement for Now Up-to-Date. All stations are running Mac OS X 10.6.4, and have always been at the most recent Mac OS X 10.6.x revision within a few days of the release of a major update.
PROBLEM: Occasionally, clients cannot connect to the server (and I don't have the exact error message -- next time it happens, someone is supposed to get a screenshot). When this happens, if you go to the server and open the file sharing control panel, then click "options", you will see an impossible number of people are connected. The first time this happened was on April 28, 2010, when it reported 41 users were connected. Mac OS X Client has an upper limit of 10 simultaneous user connections, so you can see this number is not possible. Additionally, these are "phantom" logins because you can execute this command in Terminal to see the IP addresses of any connected users:
netstat -n | grep '.548'
And when I do this, unless there was someone who had logged in prior to the "phantom explosion", it never shows any connections. On two occasions, I've actually been in the office late one night to do maintenance, checked the server before I left and found 0 connected users, then got a call in the morning that the first person who attempted to connect was blocked and the server showed 10 or more users connected.
I do not believe this is some kind of security breach. The server is not Internet-accessible, and as is shown by the netstat command, there really isn't anyone logged in anyway. I consulted with Marketcircle (makers of Daylite) because it seemed very coincidental that I installed their software just prior to the beginning of this problem, but they claim Daylite does not make any use of the Mac file sharing system. But, again, since these aren't real users, I suppose it's possible a bug in their software is somehow upping the Mac's connected user count erroneously?
Restarting the server always fixes the problem -- until it happens again. This Mac Mini is a pretty simple station -- just runs Daylite Server and Retrospect Single Server, plus the basic file sharing. Anyone have any ideas why this keeps happening?

I would say odds are likely this is correct. On at least two occasions I can think of where I verified everything was okay and later discovered a "phantom explosion", a Retrospect backup would have run. Our backups typically run at 3 AM. Is this a known issue with Retrospect? If so... not sure why it doesn't happen all the time. And in my own office I have a pretty similar setup on an entirely different computer that multiple people connect to, and it never does this. Color me confused.

Accidental Server Install - No More File Sharing

Similar Messages

Maybe you are looking for