Mini Server SMB woes

Trying to configure a new Mac Mini Server with Lion 10.7.1. So far I am disgusted with Lion server, realy wish I could go back to SL on this mini.
Anyway, here's my problem...
Trying to set up an SMB Share for end users to set Windows backup to backup their laptops to. The Mini Server is connected to a windows 2003 Active directory server, and on the domain. I have stabilized all the domain stuff, I can login using domain accounts on the mini, i can authenticate to AFP shares with domain accounts, yada yada yada.
Windows (7) however, when browsing the network the mini server shows up twice, one entry is on the domain, the other is on the workgroup 'workgroup'. Both are accessible, i can authenticate, and view the SMB shares. First off, I'm assuming this shouldn't be on the network twice?
Next problem, after I go through windows backup setup, i try to enter the credentials into windows backup to use the share folder, but it says 'unexpected network error'. If i add domain.rnd\ before the username, it seems to work once, then fails to backup. I then try to access the share via \\ip\share right from the start menu, and it's like the mini became unresponsive, or the SMB service crashed. Restart the mac mini once, sometimes twice, and it seems to work again, until I repeat this process.
Can anyone give me any tips to what might be wrong here?

I would be happy to help you Alan. I experienced this problem for SO long, and after this quick two minute fix haven't had a single issue since. Hope this helps you as well.
So I'm not GREAT at explaining things, but here is what I do on Windows 7 Ultimate x64.
1). Type 'regedit.exe' in to the 'start' searchbar and open up 'regedit'.
2). This will open Registry Editor. You'll see a few expandable folders in a sidebar all startin with "HKEY". Click on HKEY_LOCAL_MACHINE.
3). The majority of changes will be done in "\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parame ters\".. so go ahead and navigate to this location.
4). When you click on Parameters you'll see a couple of different reg values to the RIGHT. If you follow the article linked here - http://blogs.msdn.com/b/openspecification/archive/2013/03/19/cifs-and-smb-timeou ts-in-windows.aspx - you will be able to create/edit the needed values.
5). When I first did this.. none of the values (except maybe one) existed. So I had to CREATE them myself. Do this by 'right-clicking' in the right window pane and going to 'New > DWORD (32-bit) Value'.
6). I hope you'll be able to do the rest. I used '36000' for EVERY single entry in that article. I think the most important ones for our issue would be 'SessTimeout' and 'ExtendedSessTimeout' and 'OffLineFileTimeoutInterval...'.
7). In order to 'modify' or when creating a new value you need to use a 'DECIMAL' base and put '36000' as the Value data.
Do this for all of the values in that article (well the first half.. the rest of that article isn't about editing reg anymore).
Let me know if you need any more explanation.
Joey

Similar Messages

Mac Mini Server 2011, with lion, sleeps every day

My new Mac Mini Server 2011, with lion, sleeps every day! Server not responding.
All services are down, smb, vnc, ssh too. And it not should be happen because this is a server, right?
Please, I need help with this problem!
How to fix it?

1. Go to System Preferences.
2. Select Engery Saver
3. Slide the setting for Computer sleep to never.
4. Slide the setting for Display sleep to never (though I believe the display should be able to sleep without much issue.
5. Make sure the following are not selected:
a. Put the hard disk(s) to sleep when possible.
b. Allow power button to put the computer to sleep.
6. Make sure the following are selected:
a. Wake for network access
b. Start up automatically after a power failure
c. Restart automatically if the computer freezes.
Good luck!

Cannot print to Mac mini Server print server from MBP

Setup two USB printers on a Mac Mini server, they were recognized and new drivers downloaded. I can print from this machine. I shared them over LPR, IPP and SMB and announced through Bonjour
I installed the printers on a new MBP
When I try to print it starts to spool but the printer goes to pause. If I un pause it just goes back to pause.
The error log said printer does not exist, I have removed and reinstalled the printers - no change
I have no quotas
Firewall ports open
Have tried printing via LPR, IPP using generic PostScript driver and vendor specific
Printer service is up in Server Admin
I have not setup a an LDAP entry for this device as I thought I would not have to - am I worng here
The other odd thing is I have Parallels setup on same MBP and I loaded Bonjour there and it prints fine from the VM - wierd huh?
What have I done wrong here

How do you locate the firewall settings on the server?

Windows 7 and Mac Mini Server not connecting

I'm running a small design studio in Central Asia. For four years we've had a Mac Mini Server (Snow Leopard/Lion), working with three Macs, and two PCs (Windows XP) connecting, sharing files and accessing accounting software without any issues.
Due to Windows XP being discontinued we upgraded the PCs to Windows 7 Ultimate (it was the best that was available legally locally). The Windows machines both continued to connect to the server, although getting it to work initially was harder than with XP.
Our Mac Mini Server showed signs of dying, so this week we purchased a new Mac Mini Server with Mavericks (10.9.3). The macs in the office can see it fine, however the Windows 7 machines are unable to see the server on the network or access using the smb path. They can access the old server using smb, however in the network control panel, the old server is also invisible.
The server has SMB/AFP enabled. The Windows 7 machines are set to recognise networks and supposedly therefore to see others. They are failing to do either. It seems like both MS and Apple changed the way they communicate pretty significantly.
How can I get the Windows 7 machine talking with the new Mac Mini Server?
Thanks for any advice.
Richard

The problem of the machines connecting seems to have solved itself today - with one small tweak to the setup.
I inserted an underscore (_) instead of spaces into the Mac Server name, and although the Windows 7 machines still can't see the server they can now connect using SMB.
I can't believe something so small kept me so flummoxed for so long....

My Mac Mini (Server edition) has insomnia!

Greetings!
Let me begin this by clarifying that, while I have a Mac Mini Server (mid 2010), I purchased it for the hardware and do not use it as a dedicated server, hence why this is actually a problem for me. Now that that's out of the way, the problem:
Up until this morning my Mini has slept fine whenever I manually put it to sleep via the Apple menu. This morning, however, when I tried to put it to sleep before leaving for work, it seemed to sleep for about one minute (at least the screen was dark and the light was pulsing), after which it suddenly sprang back to life. It did not even ask for my password as it should after emerging from sleep. At first I thought it might have had something to do with the FireWire drive I had connected to it, so I disconnected it and tried again. Same thing happened. After work I tried a third time just for kicks, and after appearing to sleep for one minute and then waking up again I checked the console. Here is what I found:
8/17/10 4:08:44 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:45 PM configd[33] network configuration changed.
8/17/10 4:08:45 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:45 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:45 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: rfb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: 00000000-0ce0-873e-4da3-bcaa784446af._sub._home-sharing.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: afpovertcp.tcp.local. (PTR)
8/17/10 4:08:46 PM mDNSResponder[36] SendQueries: No active interface to send: smb.tcp.local. (PTR)
8/17/10 4:08:46 PM configd[33] network configuration changed.
8/17/10 4:08:46 PM watchdogtimerd[58] Automatic reboot timer re-enabled.
8/17/10 4:08:46 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:46 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:46 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:47 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:48 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:48 PM configd[33] network configuration changed.
8/17/10 4:08:48 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:48 PM configd[33] network configuration changed.
8/17/10 4:08:48 PM /usr/sbin/serialnumberd[6198] Responding to network change notification.
8/17/10 4:08:49 PM configd[33] network configuration changed.
8/17/10 4:08:50 PM servermgrd[64] servermgr_jabber[N]: Network change ignored - no change in host(s) or address(s).
8/17/10 4:09:04 PM /Applications/Microsoft Office 2008/Microsoft Entourage.app/Contents/MacOS/Microsoft Entourage[17985] Warning: accessing obsolete X509Anchors.
8/17/10 4:09:06 PM /Applications/Microsoft Office 2008/Microsoft Entourage.app/Contents/MacOS/Microsoft Entourage[17985] Warning: accessing obsolete X509Anchors.
8/17/10 4:09:07 PM /Applications/Microsoft Office 2008/Microsoft Entourage.app/Contents/MacOS/Microsoft Entourage[17985] Warning: accessing obsolete X509Anchors.
8/17/10 4:09:13 PM /Applications/Microsoft Office 2008/Microsoft Entourage.app/Contents/MacOS/Microsoft Entourage[17985] Warning: accessing obsolete X509Anchors.
8/17/10 4:11:19 PM watchdogtimerd[58] Automatic reboot timer disabled for sleep.
The last bit about Entourage caught my eye, but I had put my computer to sleep successfully with Entourage running in the background plenty of times in the past (and the problem persists even after quitting Entourage and putting the computer to sleep). The only thing out of the ordinary is that, as of last night, I now use OpenDNS. Because of all of the mDNS Responder events in the console, I'm thinking that might be the culprit. Does anyone else agree and might have a solution to fix this? I would prefer to use OpenDNS but if it is going to continue to prevent my computer from sleeping then I suppose I'll go back to using Comcast's DNS servers.

Have you installed any software which provides for remote system access? Such software frequently disables sleep. For example ShareTool from YazSoft and the LogMeIn service.

Ricoh Aficio scanning to mac Mini Server

I have a brand new Mac Mini Server, os is up todate 10.8. something.
I have two XP Pro SP3 pc's that access file shares on the mac mini.
They are ok except the drop the connection due to what I believe is the SMB 1.0 on the XP and 2.0 version on the mini fighting each other.
But it works for now with the XP machines till I can upgrad them to windows 7.
We have a Ricoh Aficio MP C2550.
I want to scan to the mini.
I cannot access SMB shares on the Mini from this printer.
I tried FTP but cannot access the FTP site either.
I can access both SMB and FTP from the XP machines.
I am new to Mac's. I have been a Windows guy since 1994.
Any help would be greatly appreciated on this.

Hi Fultonm. I had the same issue and the steps below resolved my scanning and it is still workin OK now.
Scanning to MAC 10.7 and above using FTP
Turn on the FTP server on the destination MAC using the following command which needs to be enter from within the “Terminal”:
sudo -s launchctl load -w /System/Library/LaunchDaemons/ftp.plist
To stop it:
sudo -s launchctl unload -w /System/Library/LaunchDaemons/ftp.plist
Confirm the FTP server works by typing:
ftp localhost
If the ftp server is configured correctly, you should see the below:
$ ftp localhost
          Trying ::1…
          Connected to localhost.
          220 ::1 FTP server (tnftpd 20100324+GSSAPI) ready.
          Desktop/My ScansName (localhost:):
To enable the FTP server, you will need to enter the password of the user account that your are currently logged into in order for the FTP server to be created. If you need to turn off FTP enter “unload”. The FTP server will usually be com.apple.ftp.
Create a scans folder on the desktop, i.e. My Scans.
Share the scans folder
Log onto the copier which the scans need to be sent from.
Open address book and select to add a new scan destination.
Select “file” as the scan type and change the send method from “SMB” to “FTP”.
Enter a name for the scans destination as usual.
Enter either the IP address of the MAC or the hostname and folder path into the relevant boxes.
On a Ricoh both the IP/Hostname and the folder path can be enter into the “Hostname” Box.
On a Canon, enter the IP/hostname into the “Hostname” box, and enter the folder path into the “Folder Path” box.
You do not need to use the “\\” for the hostname or folder path as you would when setting up scanning to a Windows machine, i.e. \\MYCOMPUTER\DESKTOP\MYSCANS.
Instead you enter the IP/hostname and folder path in the following format;
Ricoh –
Hostname: MYCOMPUTER/DESKTOP/MYSCANS
Canon –
Hostname: MYCOMPUTER
Folder Path: DESKTOP/MYSCANS
Enter the user account name and password that is going to be used for authentication.
Save the settings and test the scanning. IF configured correctly using the steps above the scans should be sent to the MAC using FTP and appear in the scans folder you have created.
The fields (hostname, folder path, authentication, and so on) for setting up the scan destination information on the copiers GUI will be dependent on the manufacturer, but will all follow the same principle.
Hope this works!

Xserve to Mac mini Server

Hi,
I have Xserve Late 2009. It has hardware issues
I want to switch on Mac mini with OS X server.
I have 50 users working on Xserve.
The following service are in use in Xserve.
1. File Sharing (AFP, SMB)
2. Open Directory Master
3. Network user login ( users profile (home folder) located on Xserve)
4. SVN
5. Web services
6. Calendaring
7. DHCP
8. DNS
is the mac mini with OS X server will support for 50 users using above services. I also want to add NAS to expand the storage for users home folders.
Now, the mac min server also discontinued, Can I use the mac mini desktop and installed OS X server separately and will support all 50 users.
Client workstation use photoshop and web designs.
Please recommend the solution for above services.
Thanks,
Prem

I agree with Antonio. There shouldn't be any significant performance drop with that many uses. I'm running about 25 users in a shop on a new Mac Mini Server with a Promise Pegasus 2 R6 for storage, and for a server, it's very peppy. I'm only using the internal drives for the server OS and mirroring them as a form of backup for that. I'm backing up the Pegasus2 back to the old server which has a Promise VTrack E-class 12TB array attached to it. (Which is also serving up some image files and running a Data Asset Management application.)

I am having keyboard problems when trying to boot up an OS (bootcamp on Mac Mini Server)

I recently tried using bootcamp on my new Mac Mini Server.
I uploaded a windows ISO Image perfectly the way it asked, Windows 7, I followed the correct steps, euqally divided one of the hard drives, and I was ready to actually set up the new Windows section of my computer. During this booting session, my dog came in the room with her ball and knocked the computer plug out of the socket. Now when I turn on the mac, the fan still works, the same Macintosh sound comes up, the screen turns that usual very bright gray, but it stays on that gray. After a minute or two, the screen turns black, with a blinking underline, as if it were confused to choose which operating system it has to boot.
My problem here is that I use a wireless keyboard (not by Apple) -- and I suppose that bluetooth syncronizes with the OS and not the computer system itself -- so my keyboard commands do not get recognized in order for me to navigate into Windows 7 or OS X Mountain Lion. I tried solving this problem by purchasing a brand-new USB keyboard (since Mac Mini Servers do not have the PS/2 entrance). I guess this new USB keyboard didn't work, I imagine, either because the USB slots on the machine are not recognized by the computer's internal system, only by the Operating Sysytems (which I hope isn't true), or that the mac had never used that USB Keyboard and wasn't going to be capable of using it until it had installed the necessary drivers, but without the OS running that would become impossible.
So my question is: Is there a way that I can connect a keyboard to the mac so I can continue installing my alternate Operating System? Is it maybe another problem all together?

It is starting to sound more like Bootcamp failed to install properly.
Have a look at > Boot Camp 5: Frequently asked questions
then perhaps > Failed bootcamp instlation - Google Search

Cannot Search Mac Mini Server

Setup a small office network for our art dept, but have lost the ability to search for files on the Mini server. I have seen a ton of threads about this, but no definite fixes or reason. Please help! It is very difficult to work with a server that you can't use a search function on!
Imac- OSX Lion 10.7.4
Imac- OSX 10.6.8
Mini Server- OSX Server Lion 10.7.5
Thank you
-Prodigal

This sounds like a simple port forwarding issue, but I don't understand your LAN setup.
The WRT300N has DDNS service set up. NAT and RIP are disabled.
The chances are, you're running NAT somewhere in your network. If not the WRT then what? If it's your cable modem then you must have port forwarding configured on the cable modem, and that's where you need to focus - change the port forwarding to point to your Mac Mini's address rather than the WRT.
HOWEVER, it is far more common to have the wireless router perform NAT and DHCP, which is why I question your setup.
Not directly related, but:
The Mac Mini DHCP is reserved
Nix this. Your server should be configured manually, with a static IP address, not DHCP, even with a reservation in the DHCP server. The only advantage of DHCP is for dynamic hosts (hence the 'D' in 'DHCP') or if you expect to change your entire local subnet on any kind of frequent basis. The reality is that you can't just change the IP address of Mac OS X Server like this - there are too many dependencies, so it's better to set it manually, knowing that there's a cost (and pain) to change the server's address.

Website on Mac Mini Server not accessible. Error 403 index document not available.

Dear all,
I'm trying to host a website on my Mac Mini Server. As far as I can see, my DNS is working correctly. Also my firewall is setup correctly. (I'm hosting another website which works OK). But I setup a new site. Basically a copy of the working site. But this site doesn't reflect an index.htm page. I receive an Error 403 with further information that there is no index document or that the site is secured. There is a contact link on this page directing to my webmaster. So I conclude that something is working, but no index.htm page. Has anyone similar experience? And offcourse a solution?
Many thanks.

Launch Terminal.app and issue the commands:
cd /Library/Webserver/Documents/
ls -al
And see if the files are readable by the web server. Here's an example index file listing that's owned by root and with group access for admin folks, and this file is marked as readable and writable for the owner and the group, and is readable for everybody else:
-rw-rw-r-- 1 root admin 5094 Jul 25 2009 index.html
In this configuration, the web server would be using the other access; the web server can read this file, but not write to it. Here is how to duplicate these ownership and access settings on your own index.html file, assuming that you have that file present in the ls listing above, and assuming that you have issued the cd (change default directory) command shown above:
sudo chown root:admin index.html
sudo chmod ug=rw,o=r index.html
You will need to enter your administrative password for the sudo command.
I would very strongly suggest that you start learning some basics of bash and of Apache, because you're going to be needing those skills very soon.

How to set up my mac mini server to use two drives seamlessly?

I have a mid 2010 mac mini server, with OSX Lion installed. It has dual 500gb hard drives.
I've been moving all my important files to it, and I've always assumed that once I filled one disc, it would seamlessly transfer over to the other and continue backing up. This does not seem to be the case.
I'm at roughly 495gb of data, and when I try to move a 10gb file onto my server, it tells me that I don't have enough disc space to continue the operation.
What can I do to make use of both drives?
-Thanks

It sounds like what you're asking for is to have the two drives in a RAID 0, where the two 500 Gb drives look like a single 1 Tb drive. I'm not sure the exact procedure for installing RAID 0 on a mini's internal drives, but the process would involve backing up, reconfiguring for RAID (which destroys all data,) restoring data from the backup, and more risk than I would personally find acceptable. I'd expect to lose a full day with the backup and restore steps. I can guarantee, there will be pain.
Instead, I'd suggest looking at what's consuming the 500Gb, and seeing if there are particular folders that can be moved. For example, a shared folder is pretty easy. Copy it over. In file sharing setup, edit the share to point to the new location. Make sure remote users disconnect, and reconnect to the "new" share. When you're happy there is no data loss, delete the old location.
User's home directories can also move, but the process has a few more steps, and depends on how the accounts are built (local vs. OD)
If the majority of the data is in a single "your backup files" folder, shared or otherwise, then I would just set up a second folder on the second drive and write to it, leaving the first alone. If it is truly a backup, then you could make the first folder read-only at this point for extra protection. If you go the 2 folder route, keep in mind your boot drive is operating with 1% free space, I like my drives to have at least 15% free, and OS drives more like 25% (you'll find some range in recommended %-free, but most will agree 1% is too little) so move SOME stuff to the new folder, before closing the old.

Using a Mac Mini Server quad Core i7 for FCPX ?

I am a student trying to
configure a final cut pro X edit system with a budget of around $4K.
I have over 400 hours of video (some Hi-8 but mostly mini-DV tapes).
For the Mini-DV tapes I plan on ingesting video into FCPX
directly from the camera via firewire DV. I will be using a Sony GV D800 to ingest
the Hi-8 tapes via firewire DV as well. I already have a 30" Apple Cinema Display.
H.264 will be used to deliver finished content to the web and/or Blu-ray.
I was leaning toward the macbook pro 17" but then I realised that a Mac Mini Server
could be configured with the same number of cores and RAM for less money.
Mac mini Server
2.0 GHz Quad Core Intel i7 -- same number of cores as macbook pro 17"
8 GB RAM
750 GB Serial ATA Drive 7200rpm + 256 GB Solid State Drive
Mini DisplayPort to Dual-Link DVI Adapter
Apple Magic Mouse + Magic Trackpad
Other Peripherals:
Promise Pegasus 8TB R4 Raid System in RAID 5 configuration or equivalent
Sonnet Echo Express PCIe 2.0 Thunderbolt Expansion Chassis with
Matrox Compress HD MAX encoding card
LaCie d2 Blu-ray 12x
Do the extra cores in the server make up for the difference in GPU?
(2.7 GHz Mini dual-core i7 with AMD Radeon HD 6630M graphics processor with 256MB of GDDR5 memory) VS (2.0 GHz Mini Server quad - core i7 with Intel HD Graphics 3000 processor and 384MB of DDR3 SDRAM shared with main memory)
Am I thinking about this configuration the right way? Is there
any overhead given that the mini will be a server? Anything missing?
thanks for your help,
Tom

Take it back for a replacement while you are within 14 days from purchase.

Using a Mac Mini Server as a traditional stand alone desktop

Hello all, currently I have a late 2008 model 17" MacBook pro, Time Capsule, Apple TV and an Iphone 3GS and Ipod Traditional. I would like to add a desktop system to coordinate all of these items, to be the centerpiece is you will, in my home. I'm interested in buying a mac mini, I began to do research however and saw the Mac Mini Server which has greater memory capacity 4GB vs 2GB RAM, and dual 500Gb vs the standard Mac Mini which has one at 320GB. I would like to take advantage of these upgrades as I'm a writer and will be constantly on the web for work as well as likely keep a lot of items on the hard drive.
However I noticed the Mac Mini server utilizes Mac OSX snow leopard SERVER as opposed to the user grade Mac OSX. *My question is if the Mac Mini Server with MAC OSX server can still be used as a stand alone desktop, connecting it to a spare LCD television I have and a mac wireless keyboard/mouse?*
I'm aware that unlike the other mac mini and imacs it does not come with ilife and other pre-installed software, and *I want to know if it's still possible to purchase after market and install said software utilizing them in the traditional manor?*
Thank you in advance for any feedback you can provide and I apologize if my question was difficult to comprehend due to my lack of computer knowledge. I also apologize if this question is similar to others you've received lately as I did a quick scan of google and these forums and did not seem to find the specific answer I was looking for.

Welcome to the Apple Discussions!
Let me clear up a misperception that you have. Both the Mac mini and the Mac mini Server have a capacity to address 8 GB of RAM. There are two SO-DIMM slots in each model. The mac mini comes preconfigured by Apple with 2 GB of RAM (2 x 1 GB). The mini Server comes preconfigured with 4 GB of RAM (2 x 2 GB). You can buy and install yourself up to 8 GB of RAM (2 x 4 GB).
You can even install Mac OS X Snow Leopard client, which will meet your needs a bit better than Server, now that folks have figured out how to do it;
http://discussions.apple.com/thread.jspa?threadID=2539663&tstart=0
And yes you can buy and install iLife, and pretty much everything else that you want to include in your kit. Either model of mini works fine with wireless keyboards and mouses. If your LCD TV has an HDMI port, then a simple HDMI to HDMI cable would be the simplest manner to connect it to the mini.
Dah•veed

Is the mac mini server the same hardware as the other mac minis (except for the quad core i7 and dual hard drives) with different software or is it configured differently?

I have a mac mini with an i7 dual core processor. It is perceptably slower than my macbook pro with a quad core i7. Does the mac mini server have the same hardware configuation as the regular mac mini with server software or is the hardware different (aside from the i7 quad core and dual hard drives)? I want a mini with a quad core i7...

Your assumption is correct. The server does however only
have the Intel HD3000 graphics like the base model with
no option, at this time, for the discrete graphics chip. So,
depending on what you are using it for, that could be a deal
breaker. Remember that your MBP does have a discrete
graphics chip.
I have a 2011 Mini Server connected to a Thunderbolt display
that gets used as an engineering workstation and general
personal use (some photo editing, LP restoraton, general
internet browsing). You simply just not enable any of the
server services. I find the combination to work quite well
for my purposes. I also have a 13" 2.7 GHz i7 Macbook Pro
which is pretty much strictly for work. As far as CPU
power it is pretty much equivelent to your Mini. For the most
part I find the Mini does outperfom my MBP. I heavily use
Parallels and Windows7 virtual machines, so the more cores
the better.
So, If you do a lot of CPU intensive stuff that is multithreaded,
the Server may help. If it is graphics intensive and your software
heavily leaverages the GPU, you may actually take a hit on
performance.

Mountain Lion Mac Mini Server Ethernet Port Not Working

I have a Mac Mini Server and once I upgraded to Mountain Lion Server the Ethernet port is unresponsive. It worked before upgrading. Is there something with Mountain Lion Server that is causing the Ethernet port not to work properly?

Make a "Genius" appointment at an Apple Store.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

Mini Server SMB woes

Similar Messages

Maybe you are looking for