Running workgroup manager locally on an eMac

I've installed workgroup manger on a 10.3.9 eMac, and I want to use it to administrate this computer locally. The problem is that when I try to login in using my IP as the address and the username and password it says: The address you entered is not reachable. Please check your network connection. I do have a connection to our network, but for some reason I can not connect to this computer from this computer. One of my co-workers was able to get this same type of situation to work on a 10.4 eMac, but oddly it's not working on 10.3. Any suggestions?? Thanks

Is the server also running 10.3.9 server software or is this computer just another eMac? Are you trying to log in as local account on the server or as an Open Directory account on the server, in which case Directory Access should be configured to use the server for LDAP authentication.
I'm not sure I understand what you mean by "I can not connect to this computer from this computer."

Similar Messages

10.6.8 Server - workgroup manager not authenticated

I have 10.6.8 Server that has suddenly stopped accepting the dradmin password when using Workgroup Manager. Workgroup Manager connects, but in not authenticated mode. When I click the lock icon and am prompted for the ID & Password it is rejected. I know with 100% certainty I am using the correct administrator ID and password. I am running Workgroup Manager directly on the server computer. I'm able to log on to the computer as the local administrator. Server Admin works fine with no authentication issues.
I have not applied the 10.6.8 Supplemental update, but wonder if that might be helpful.
It is very concerning to be locked out of my own server. Any suggestions why this is happening and how to reslove it?
Thank you,
-Joe

The logs revealed that dradmin was actually authenticating successfully, but for some reason Workgroup Manager was still in unauthenticated mode. I installed 10.6.8 Supplemental update and found no improvement.
All users have portable home directories and everything with Open Directory was functioning properly. DNS and Kerberos were confirmed to be working properly. Several restarts and shutdown/startups were performed and I never was able to get Workgroup Manager to authenticate. So after a few hours troubleshooting last weekend I decided to restore the server to a disk image that was created 20 days earlier. I elected to do this this because I needed to get it resolved on the weekend to minimize the chance of downtime during business hours. The only thing on the boot drive is the server OS an everything else is stored on an external RAID so it was fairly simple for me to restore then get everything current again.
I kept an image of the server with the problem so I can restore it to a standby server to experiment with any possible fixes that I may come across in the future. As of now I don't know why it happened nor how to fix it without restoring.

Workgroup Manager doesn't create home directories for OD accounts

I'm having an issue where home directories aren't created for OD accounts. My setup is as follows, the home directories are stored on the OD Master (the only Apple/OD/AD server on the network), and the home directory paths are filled as afp://192.168.1.254/Customers, fakeuser, /Users/Customers/fakeuser
This same pathing scheme works fine for local accounts, however for OD, clicking Create Home Directory and saving the account does nothing (no errors, nor folders created). If I ftp into said account, I wind up being directed to /Users (definitely not the expected behaviour)
I am deploying a web based upload system that I want to authenticate against OD users so as to share home folders and permissions with the ftp server, once I have this figured out I will be migrating a bunch of accounts to OD from local.

In addition to potential DNS issues, it sounds like you may be using the wrong procedure to define the users' home directories. You should never have to specify the paths manually; instead, define the share point ("Customers" in your case) to be automounted, and then it should automatically show up in the list of available home folder locations, with all the necessary paths predefined. Here's the full procedure:
1. Run Server Admin, and select: the server name in the sidebar -> File Sharing in the toolbar -> Volumes & Browse under that -> navigate to the /Customers folder in the column view.
2. Make sure the folder is being shared (with it selected, you should see an "Unshare" button near the top right of the window); if not share it with the Share Button (then Save the change).
3. Select the Share Point tab under the file browser (NOT the one above it), and select the Enable Automount checkbox. A dialog will open asking for the automount details; make sure the Directory is set to /LADPv3/127.0.0.1, Protocol to AFP, and Use for is User home folders and group folders. OK the dialog, and be sure to click Save to make the change take effect.
4. Run Workgroup Manager, and select Accounts in the toolbar -> Users (single person icon) tab under that -> some user account(s) you want to configure under that -> Home tab on the right.
5. Select (None) from the location list and click Save (this wipes out any current setting, so we can rebuild it correctly).
6. The Customers share point should be in the list of available locations (due to being configured for automount); select it, then click Create Home Now, and finally Save.

Unix and workgroup manager in 10.4 & 10.5

hey folks:
since we don't have an OD master, we're running workgroup manager (WGM) locally on about 40 macs to manage access to certain system pref panes. we also prevented opening of WGM on each machine except from the root account.
i'm looking for an elegant way to use the command line to UNDO this work and push that solution via ARD. right now i've tried running these lines of code:
sudo rm /Library/Preferences/DirectoryService/*
sudo rm -dr /Library/Managed\ Preferences
sudo dscl . -delete /Config/mcx_cache
and this works, but only temporarily. while it immediately allows access to ALL system preference panes, if the machine is restarted, WGM re-asserts itself and the managed prefs are, once again, put into play.
i want to avoid going to each machine, logging in as root, launching WGM and unselecting the choice i made some years back to manage the system pref panes.
any thoughts?

Here is how I got mine to work, I figured ill share since it was driving me crazy...
open workgroup manager
Click "cancel" on the login window (with the grayed connect)
from the menu click on "server -> view directories"
workgroup will load in "not authenticated" mode
click on the lock symbol on the far right
enter your diradmin or admin user name and password
This seemed to do the trick for me, hope you have the same luck I did.
Now I want to know why it stopped working in the first place

Workgroup Manager Won't Authenticate Anymore

I'm using 10.5.2 on both a client and a server and I'm seeing some weirdness with Workgroup Manager. Last week, I had no problem using workgroup manager on my machine to connect to the server. Today, WM is not allowing me (or any other admin accounts) to authenticate at all remotely. If I screen share to the desktop of the server and run workgroup manager, I can use my credentials to authenticate.
What I'm seeing in the system.log is "Client response doesn't match what we generated" I found the relevant article here: http://docs.info.apple.com/article.html?artnum=306596
Following up from that article, I did some digging in the Password Service logs. When I try to login remotely to Workgroup Manager, the logs show this:
Feb 19 2008 09:49:47 AUTH2: {0x4787f45616bdec6b0000000600000006, mbydalek} DIGEST-MD5 authentication failed, SASL error -13 (password incorrect).
This line gets repeated 4 times.
When I'm on the server locally and authenticate, it uses CRAM-MD5 and authenticates successfully.
I did find the following article talking about testing authentication, etc. http://docs.info.apple.com/article.html?artnum=302942 All the methods described in there work test successfully.
Something really strange is going on here because my user can authenticate to AFP, SSH, etc. just fine - just not Workgroup Manager remotely.
I'm going to further chalk it up to weirdness because what I'm trying to do this morning is add a new user (normally a 2 min job). Adding the user from the manager on the server is fine, but it throws an error when trying to create the home directory.
Lastly, I thought it could be my machine, but I've kinit'd, afp'd, etc. from my machine without a problem.
Anyone have any other ideas that I can try?

Thanks for the pointer to createhomedir - that did indeed do the trick. (How on earth do people find these little nuggets).
I hesitate to mark this as solved however - it's a functioning workaround, but does nothing to explain why on earth the GUI suddenly stopped functioning.
But in the (likely) event that that question never gets answered, thanks again for letting me get on with working!

Workgroup Manager Quits!

When I open workgroup manager and open my local account info, and click on the "New User" button. Or, If I click on a already made user, and click on the "Home" tab, workgroup manager quits without any message (when having the server give back the 'unexpectedly quits' message it says thread 0 crashed) Everything works fine with the open directory accounts. Yes, I have tried reinstalling the admin tools. Any ideas??

Your posts didn't indicate whether you were running Workgroup Manager from the server or from a workstation (or both). I would be curious if it quits out in the same way when run on more than one machine. If so, this would indicate a problem on the server side, and not with the management application.
If it's on the server side, I would experiment with whether the problem occurred only with NetInfo (you mentioned you had problems there), or if you also saw similar issues when making changes to your LDAP entries, if you're using Open Directory.

Workgroup Manager Monitor Resolution

Hello,
I'm trying to run Workgroup Manager on my clamshell iBook 366 indigo, and I recieve a message that I need a larger monitor resolution.
How do I get around this?
All the other server applications run acceptably, except for Workgroup Manager which seems to need a 1024x768 resolution that I don't have.
I tried using Remote Desktop to administer it, but that doesn't work, and I don't know how to connect this old of an iBook to an external display. Is there some way to use 1024x768 as an unsupported screen resolution?
Thanks very much.

You will need a computer that supports a higher screen resolution. The clamshell iBook, although wonderful in many ways, cannot run WorkGroup Manager. It cannot run any recent version of iMovie either. Its screen is just too small.

HT1338 XSERVE 10.6.8 is running very slow, and Workgroup Manager is not responding

XSERVE 10.6.8 is running very slow, and Workgroup Manager is not responding. There is no more updates to download.

munish khanna wrote:
1. upgrade to lion, which should over write previous software and the reasons for it being slow.
No, you don't want to upgrade over a buggy system, Lion has issues of it's own that will only complicate matters, plus Lion is slower than Snow Leopard.
Learn all the pitfalls before you upgrade to Lion, like all your Rosetta/older programs will no longer work and more.
Leave Lion for a new hardware purchase is my advice, it's still got plenty of security and other issues.
For your performance, your likely better off replacing the hard drive with a 7,200 RPM model and maxing the RAM, download the free MacTracker to find out your specs, and OtherWorld Computing is good for videos, tools and parts.
http://eshop.macsales.com/installvideos/
2. Format the hard disc and reinstall snow leopard.
That will work, provided your data is off the machine first.
Now how do i reinstall snow leopard as it was an online purchased upgrade from leopard.
The 10.6 Snow Leopard disk that you upgraded 10.5 Leopard from actually has the full OS X 10.6 on it.
All you have to do is stick the disk in and hold the c key down while booting, use Disk Utility to erase the entire drive, quit and install 10.6.
Of course your not going to get the free iLife that came with the 10.5 grey disks, see if you can first install 10.5 with the same methods, then setup with the same user name as before, then upgrade to 10.6
I think Apple nulled booting off the 10.5 disks, but it won't hurt to try.
Another method would be to install 10.6 fresh by itself, then use the program called Pacifist to extract iLife from the 10.5 disks.
http://www.charlessoft.com/
Read here for plenty of how to's
https://discussions.apple.com/message/16276201#16276201

Workgroup Manager missing users running on 10.6.7 client

Strange issue I am coming across while running the most current version of Workgroup Manager (I just downloaded it again to make sure) on a Mac Os X 10.6.7 client! -> I notice that I am missing a lot of users when I log in and the application opens. I have already deleted the corresponding workgroup manager .plist (user/library/preferences) as well but this does not do much other than asking me to enter server and username/password again
Oddly enough ALL the accounts that are "missing" tend to be lower 3digit User ID's only... in fact the ONLY 3digit id that is showing up is my admin account.
Here's the really ODD part - Workgroup manager is only doing this when it is running on a 10.6 client mac! I am running the IDENTICAL version on a 10.5.8 client, logging into the same server, and ALL the missing users magically appear. Using the same server name, same login, same password - So I am pretty sure this issue is only due to some sort of glitch in how Workgroup manager is running on 10.6( my ver is 10.6.7)
AND of course the "missing" user names are still functioning perfectly well w/ clients receiving emails, logging in to folders etc. etc.
I cannot imagine that I am the only person having this issue, and am wondering if Apple or someone else can please give me some guidance as to the source of this problem and hopefully a bug fix / resolution of the same as I don't want to have to downgrade from 10.6 > 10.5 in order to perform user administration on my server (Server is also 10.6.7)
Thanks in advance for your help

You many not know how to do it now, but you will if you follow the instructions in the link. Or you can simply remove the original Home folder you configured in Setup Assistant while logged into the one you migrated. Then re-migrate your Home folder which will now take on the original account username. Then log into the newly migrated Home folder and delete the other one.

Create local admin from workgroup manager

Just wondering if there is a way to create a local admin on a 10.6 MacBook using Snow Leopard server in the Workgroup Manager?

SL Server

Cannot login with a account created with workgroup manager on local box

Hi my name is richard and i recentgly acqquired from one of ,y friends a macbook pro with leopard 10.5.7 and I downloaded the server tools to it because workgroup manager gives me more control over user creation and the like.there are three issues that i am facing right now:
1) I create an account for a user "VERONICA MARS" short name vmars with a password of apple. when I try to login using that account the login window just sits there and shakes its head at me like no no no wrong cridentials.
2) using the same account vmars i try to reset her password using wgm and it says that it cannot reset the password.
3) when i try to create the account it tells me that the home directory cannot be created.
oh and heres a bonus one:
most of the time in wgm it takes forever to get from one tab to the next and ill have to do a force quit to restore my mkac back to normal.
if anyone can help with these issues please respond
thanks in advanced
richard johnson
mac fan for life

Please let us know the username of the account that is giving you trouble.

Managing Computers with 10.5 Server, but NOT managing Local accounts?

I'll try my best to be clear here - I'm new to 10.5 Server and a functioning Open Directory environment! (formerly used 10.3 Server and never had the OD working).
Environment:
School (K-8), with old iMac G3's (10.3.9), eMacs (10.4.11) and a smattering of Mini's and iMacs (10.5.x).
Server:
10.5 Server, OpenDirectory and DNS appear to be working perfectly.
User Accounts:
Staff members have accounts for logging into sharepoints.
No one (yet!) has server based home directories except a couple for testing.
On each computer there is a "staff" account and a "student" account.
These are LOCAL accounts, and do NOT have same-named accounts on the Server.
I have bound client computers to the Server by OpenDirector
dsconfigldap -v -f -a servername.domain.org -n configname -u diradmin -p adminpass
Now comes the trouble;
I have added the computers to the Workgroup Manager computers list.
I have applied computer preference settings for the Energy Saver preferences ONLY. THey appear to have worked (managed computers slept/shut-down/started up according to the managed preference).
NOW comes the real problem;
The "staff" account on the managed computers is denying access to most applications on the computer!
Note: this "Staff" account is local ONLY, and is NOT a server-hosted account.
I have NOT tried to manage the computer preferences for applications on these computers.
I can resolve the problem by unbinding the computer from the OD Server - but I'd prefer not to do that. I just got them all bound! And, it screws up my migration plan TOWARDS server-hosted home directories.
I have tried managing application prefs for a COMPUTER, only to have both the STaff and Student account lose ALL of their local-only application managment settings (all of a sudden, Students can open terminal, grading programs, etc).
I am obviously missing something!
At this point, I'd like to back up... to NOT having my Server interfereing with the local accounts until I'm further along mapping out my migration from local-only accounts with file sharing access to Server hosted accounts and server managed preferences.
(I will also admit I'm a bit confused about when to manage USER preferences, vs when to use managed COMPUTER preferences.).
Tips appreciated!

Your last question - using managed user vs. computer preferences got my attention. Mostly, I use Group managed preferences. I do use computer preferences for a laptop cart, other than that I use group preferences. Perhaps your situation calls for managing users, but using group preferences allows me to change the settings for a bunch of people all at once rather than changing settings for each user.
In any event, check all the managed preferences for your computer level settings. And since you're using a 10.5 server, you have to check the settings for clients that are running 10.4 and earlier as well as the settings for 10.5 and later clients, as they are different.
At the user level, if you have an OD account and a local account with the same name, the local account will determine what the user can do - I honestly don't know if managed computer prefs will override local settings, but you should look into it. This could be your problem.
At the very least, you should avoid "testing" with systems that folks are using if you want to avoid the frustration that you are now encountering (speaking from experience i.e. similar mistakes, not preaching).

Unable to authenticate with diradmin in Workgroup Manager

This has happened before, and I have no idea how it got fixed - too many independent variables...
Anyway, I cannot authenticate the OD with diradmin even while using Workgroup Manager directly on the server.
The setup:
SLS 10.6.8
Split-brained DNS
     Both public and private FQDNs are the same (myserver.mydomain.com). External DNS maps machine record to my static public IP address. Using an AirPort Extreme router, port fowarding services that I want open to the server. The router provides DHCP via NAT to the local network, with a fixed private IP assigned to the server. The server is running DNS with the same zones, machine records, services and aliases that the public IP DNS has, except mapped to the fixed private IP. DNS checks out with changeip, etc.
     The server is an OD master. Yesterday I exported it, demoted it, and restored it. All services (mail, web, etc.) seem to work fine (although I admit to not using Kerberos on AFP due to another issue).
     I have a wildcard certificate that is generated by GoDaddy (*.<mydomain>.com) which seems to work fine with the hosted websites.
This is what the password service error log says when I try to log in with diradmin in Workgroup Manager:
Jan 10 2012 14:01:32    AUTH2: {0x4bbe71ca6b8b45670000000200000002, diradmin} DHX authentication succeeded.
Jan 10 2012 14:01:32    KERBEROS-LOGIN-CHECK: user {0x4bbe71ca6b8b45670000000200000002, diradmin} is in good standing.
Jan 10 2012 14:01:32    KERBEROS-LOGIN-CHECK: user {0x4bbe71ca6b8b45670000000200000002, diradmin} authentication succeeded.
Looks good to me. But I still get the "Information Not Valid for This Server" followed by stuff about invalid login ID or password.
I did notice in the LDAP log:
Jan 10 14:13:12 <myserver> slapd[52283]: SASL [conn=18] Failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Key table entry not found)
And at the last bootup in the directory service error log:
2012-01-10 08:52:03 EST - T[0x00007FFF7027ACC0] - DNSServiceProcessResult returned -65563
The other thing I notice when I log into the library in Workgroup Manager FROM THE SERVER, even if I use the FQDN <myserver>.<mydomain>.com that Workgroup Manager says (in the title bar of the window) <myserver>.local.
I have googled the various errors and messages, and I get folks with all sorts of variations ("change the binding options", etc.) none of which either applied or worked.
Help?

Continuing on my quest... I found this Technical note from Apple about re-kerberizing:
http://support.apple.com/kb/HT3655
Interestingly, in step 3 where it says to remove realm information from kdc.conf, there wasn't any of my realm information. Argh!
So I completed all of the steps and executed the slapconfig command. This resulted in:
bash-3.2# slapconfig -kerberize -f --allow_local_realm diradmin <MYREALM>
diradmin's Password:
Could not resolve hostname <MYDOMAIN>
Skipping Kerberos configuration
Sounds like a dreaded DNS problem. It had been working correctly, but changeip -checkhostname confirmed a problem. Turns out that there were EXTERNAL DNS servers in the Network preferences in System Preferences as well as on the router. With my Split-brained DNS this caused problems (thank you again MrHoffman). So I changed them both to my DNS server INTERNAL IP address and added the external ones to the Forwarder IP Address in DNS. Now checkhostname -changeip returns a favorable result.
So after rebooting ran the slapconfig command again and got the same result. Argh. Cleared DNS caches. Still nothing.
So I tried nslookup.
nslookup <mydomain>
Server:                    10.0.8.2
Address:          10.0.8.2#53
** server can't find <mydomain>: SERVFAIL
Where 10.0.8.2 is the fixed INTERNAL IP address.
However, nslookup on using the fixed IP address yields:
bash-3.2# nslookup 10.0.8.2
Server:                    10.0.8.2
Address:          10.0.8.2#53
2.8.0.10.in-addr.arpa          name = <mydomain>.
Scratching head here... changeip -checkhostname works, nslookup on the IP address works, but nslookup on the host name fails.

Cannot change short name of computer in Workgroup Manager

When a computer is bound to Open Directory on the client side I cannot change the short name of the computer. If the computer is added through Workgroup Manager I do not have this problem. When I try to change the name it reverts back to the old name and sometimes adds a .local at the end of it, but the new name I choose is displayed on the left side. When I log out and log back in the name on the left side reverts back to the old name.
Could it be the way I am naming the computers? I am using dept-username.location as a way to name all computers. Why does this problem only occur on computers that have been bound through the LDAPv3 service on the workstation?

I can't comment for sure on this one; but my educated guess may be that you're causing problems with your DNS (or DHCP) by specifying an extra dot in the name - Although I can't say for certain as my OD doesn't run my DNS.
Try using dept-username-location.domain.local instead of dept-username.location.domain.local.
Have you checked the console output to see if any errors are being returned?
-Kogen

Php mysql integration with workgroup manager

Hello,
I run a non-profit arts organization. We have active and inactive members that are tracked with a php mysql web app that I wrote. I was wondering how I could query the workgroup manager from php to make the inactive members not be able to login to our computers. Also, it would be great if we could just add new members into the php web app and then send that new member's info to the workgroup manager.
Is this possible?
Thanks
Alex

Yes, I have an OS X 10.4.3 server - which is also integrated in the AD. If i log on locally on the server with an account from the AD, then the workgroup manager works perfectly.
Guess my main problem is that i don't know where in the process things goes wrong.
- Is it on the client, that it is not able to sent the right requests
- Is it on the OS X Server, where something is misconfigured
- Is it security settings in the AD that prevents the server and client from getting the right information
I have the possibility on both the server and client to do ldap requests through the address book - this tells me that i do have some sort of connection. And that is also verified by actually being able to login with AD accounts.
Is there any logs i should pay special attention to? All the logs i can see through server admin doesn't contain usefull information. The logs on the client located in /var/log only tells me about some minor issues with mcxd (something about the uid being 1325883267 - which confuses me a bit - i thought uid's on unix was between 1 and 65535 :/ )
/Martin

Running workgroup manager locally on an eMac

Similar Messages

Maybe you are looking for