As the title says. Wondering if it makes sense to make the move over to SLS; easier admin of all my macs, sharing of one home directory regardless of computer, file sharing ease, etc.

 

No idea it existed...

 

Oh, but it does....

http://www.apple.com/server/macosx/

 

Going to buy mac mini with it preloaded or something stronger?

 

hmmm, since I just got an MBP my boss was just talking to me about maybe getting more Mac clients and that a colleague of his was going to become an Authorized Apple reseller. Somehow that may involve me and I might get some work/training on OS X Server.

 

:ibthunder04:

 

Subscribed. Always toyed with wanting to know more about it to run it at home as a place to link to for calender and address book syncing for my MBP, iMac and both our iPhones.

 

I'm with him I use linux.

 

I have a mini already.

 

*found teh torrent* :ftw:

 

^thank god for no for no product keys!

 

 

Steve Jobs frowns on this thread.

 

He's more focused on yelling at Adobe these days.

 

And people loosing his shit at bars....

 

lol

 

Just in case anyone didn't see this over at Gizmodo.

 

Installed this as a VM to play around. It's pretty neat. Very easy to manage.

Unless I'm mistaken it looks like I can put a large hard disk onto a mac mini and backup all of my mac workstations over the network via time machine.

 

It's dirt simple to use.

 

We have it at the office

We need to test with it for all our software.


What are you using now to manage your macs

 

That's what I do now. Don't need SLS to do that, however...

 

Do you have iPhone(s) Scrib?

I've always wanted a mac mini running SLS so that my wife and I can make use of the caldev and address book syncronization capabilities of SLS for my MBC, iMac and iPhones.

 

Aww, I'm honored!

All I have experience with now is 10.4 server. We just ordered a Mac Mini /w Snow Leopard Server the other day...I'm waiting with bated breath! We need to upgrade to properly manage our 10.6 clients, and since all of our Mac servers are G5 Xserves...we need new hardware as well. The Mini should be plenty powerful for Workgroup Manager (best invention ever) and the occasional NetBoot, so it's pefect for us.

 

Yup

 

I tried putting SL on my old Mac Mini and it told me I couldn't...

 

Probably going to finally take the plunge on this... With the backup drive having failed and my RAID gear arriving, might as well throw it on and see what happens.

Gonna be a busy weekend.

 

Ok, just some updates on this.

I ended up putting it on the mac mini in the basement. Overall, I'm pretty pleased.

Set up was pretty much straight forward. There is a learning curve however on some of the apps, but for basic stuff it's certainly the "apple way". I've been able to create some groups, and turn on the appropriate services and manage them accordingly.

I do like that there are iPhone/iPad apps out there that allow for remote server management, SSH and all sorts of other goodies. My next thought it to try and get the mail server going, but that may be easier said than done, mostly due to my ISP and what I understand to be a challenge to get elements like MX Records working properly (or at all) on a residential-type of service.


And not feeling like updating my other thread, but the Hitachi 2TB disks are humming along with no issues, yet!

 

So I'm batting 2 for 2 at fixing your problems!

not bad since according to sarlacc I'm talking out of my ass 90% of the time

 

HaXor attempt from Poland. Bleh. Nice try.

Guess I'll block Poland's IPs.

Aug 17 17:43:44 squall sandboxd[6050]: sshd(6033) deny mach-per-user-lookup
Aug 17 17:43:49: --- last message repeated 16 times ---
Aug 17 17:43:49 squall sandboxd[6050]: sshd(6072) deny mach-per-user-lookup
Aug 17 17:43:54: --- last message repeated 16 times ---
Aug 17 17:43:54 squall sandboxd[6050]: sshd(6110) deny mach-per-user-lookup
Aug 17 17:43:55: --- last message repeated 16 times ---
Aug 17 17:43:55 squall emond[98]: Host at 83.20.250.163 will be blocked for at least 15.00 minutes
Aug 17 17:43:55 squall afctl[6145]: Firewall not running or managed by another entity, rule not added
Aug 17 17:43:55 squall emond[98]: Host at 83.20.250.163 will be blocked for at least 15.00 minutes
Aug 17 17:43:55 squall afctl[6148]: Firewall not running or managed by another entity, rule not added



Aug 17 14:31:12 squall sshd[2453]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:12 squall sshd[2453]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3569 ssh2
Aug 17 14:31:12 squall sshd[2478]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:12 squall sshd[2453]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:12 squall sshd[2453]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3569 ssh2
Aug 17 14:31:12 squall sshd[2485]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:13 squall sshd[2453]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:13 squall sshd[2453]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3569 ssh2
Aug 17 14:31:15 squall sshd[2494]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:15 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:15 squall sshd[2499]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:16 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:16 squall sshd[2504]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:16 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:16 squall sshd[2509]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:16 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:16 squall sshd[2492]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3570 ssh2
Aug 17 14:31:17 squall sshd[2516]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:17 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:17 squall sshd[2492]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3570 ssh2
Aug 17 14:31:17 squall sshd[2523]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:17 squall sshd[2492]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:17 squall sshd[2492]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3570 ssh2
Aug 17 14:31:20 squall sshd[2532]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:20 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:20 squall sshd[2537]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:20 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:21 squall sshd[2542]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:21 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:21 squall sshd[2547]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:21 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:21 squall sshd[2530]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3621 ssh2
Aug 17 14:31:21 squall sshd[2554]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:22 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:22 squall sshd[2530]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3621 ssh2
Aug 17 14:31:22 squall sshd[2561]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 14:31:22 squall sshd[2530]: error: PAM: authentication error for root from admp57.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 14:31:22 squall sshd[2530]: Failed keyboard-interactive/pam for root from 79.185.45.57 port 3621 ssh2
Aug 17 16:18:55 squall sshd[4577]: Did not receive identification string from 189.75.51.46
Aug 17 17:43:36 squall sshd[6029]: Did not receive identification string from 83.20.250.163
Aug 17 17:43:43 squall sshd[6034]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:43 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:43 squall sshd[6039]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:43 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:43 squall sshd[6044]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:44 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:44 squall sshd[6049]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:44 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:44 squall sshd[6032]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2198 ssh2
Aug 17 17:43:44 squall sshd[6057]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:45 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:45 squall sshd[6032]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2198 ssh2
Aug 17 17:43:45 squall sshd[6064]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:45 squall sshd[6032]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:45 squall sshd[6032]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2198 ssh2
Aug 17 17:43:47 squall sshd[6073]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:48 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:48 squall sshd[6078]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:48 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:48 squall sshd[6083]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:49 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:49 squall sshd[6088]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:49 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:49 squall sshd[6071]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2199 ssh2
Aug 17 17:43:49 squall sshd[6095]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:49 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:49 squall sshd[6071]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2199 ssh2
Aug 17 17:43:50 squall sshd[6102]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:50 squall sshd[6071]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:50 squall sshd[6071]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2199 ssh2
Aug 17 17:43:52 squall sshd[6111]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:52 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:53 squall sshd[6116]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:53 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:53 squall sshd[6121]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:53 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:54 squall sshd[6126]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:54 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:54 squall sshd[6109]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2201 ssh2
Aug 17 17:43:54 squall sshd[6133]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:54 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:54 squall sshd[6109]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2201 ssh2
Aug 17 17:43:54 squall sshd[6140]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Aug 17 17:43:55 squall sshd[6109]: error: PAM: authentication error for root from exa163.neoplus.adsl.tpnet.pl via 10.0.1.103
Aug 17 17:43:55 squall sshd[6109]: Failed keyboard-interactive/pam for root from 83.20.250.163 port 2201 ssh2

 

 

I get SSH attempts on my Debian box all the time.

 

Well, with root disabled, they're not going to have much luck. Trying to determine how best to make sure I'm protected, though.

 

Strong passwords, non-standard usernames, and keeping up to date should do you good.

 

I'm trying to remember how to limit the number of unsuccessful access attempts before the offender gets a time out.

 

You are going to get that crap all the time. It's not really a big deal unless you are paranoid. If you want to avoid the bulk of that stuff you can run sshd on a non standard port and tell your client to use that port.
http://discussions.apple.com/thread....ageID=10141032

 

Was that necessary? lol

 

Soooooooooo, I was at work today and a friend of the boss who's also in the IT industry came into the office and was chatting it up with us. He was wearing a black polo with the Apple logo on the sleeve and it says "Business" underneath. He says "I wish you guys worked with Macs." Then everyone looks at me, cause according IT people I'm an uber Apple fanboi. I then pointed him to my MBP, iPhone and iPad sitting on my desk.

He then goes on to tell us about becoming part of the ACN (Apple Certified Network) by taking some tests and giving Apple more money. Then in return we get a small discount (I think 10%) on Apple shit and whenever someone comes into the Apple store and buys some Macs or Servers for their business the Apple Store will give them our business card for them to contact us to help them setup their new macs and servers! Apple Store Business Employees aren't allowed to go on site and setup a network so they hand that off to a ACN qualified member.

So now my bosses are kinda wanting me to become trained in Apple Server shit and get qualified so we can get another revenue stream coming in. Sweet!

So I'm thinking about picking up one of the Mac Mini Servers and connecting it along with a KVM to my desktop at home so I can switch back and forth between my Windows 7 machine and the Mini Server.

I'll post updates in this thread....

 

 

 

i see your hax!