Logging in to my Leopard Server network keeps failing

This keeps happening - it's almost as if the OD or AFP services are dying after a while (although they seem still to be running). What happens is that suddenly a client on the network cannot connect to a sharepoint as a registered user (guests seem OK). Any valid login just gets rejected. If I reboot the server then the client can login again. I haven't had time to investigate whether restarting the services resolves the problem, but whether it does or not there seems to be a problem on the server.
Can anyone throw light on what may be causing the login capability to keep dying?
This is really annoying, because I have been using Tiger Server happily for 3 years and fell for the marketing to upgrade to Leopard Server (which feels more and more to me like a beta release).
Thanks,
Ian.
--

@Strontium, not sure what the basis for your opinion is, the server login processes *is* a client of OpenDirectory and Kerberos and subject to the same PAM authorization process and thus the creation of a Kerberos ticket.
After nearly two days of digging, I found the issue was caused by the existance of user records for some of my network users in the /Local/Default directory on the server which had an AuthenticationAuthority value pointing to an old, no longer used, Kerberos domain. As these were OpenLDAP users, I hadn't even thought of examing the local directory until I noticed that the expected Kerberos ticket behavior was working properly for one of my accounts which was not a 'mobile' account. I then realized only my 'mobile' accounts (which were nearly all of them) were the only accounts showing this problem.
I believe what happened is when I changed server's kerberos name at some point in the past (by backing up the OpenLDAP records, demoting the master, re-creating the master with the new Kerberos name, importing the records, and resetting passwords); I never thought to clean up any locally cached user records for my 'mobile' users.
To fix: I used the Directory Utility to delete the users from the local cache. On next login by a mobile user, a correct local user record was created reflecting the proper Kerberos authority and now I'm getting Kerberos tickets on login again.

Similar Messages

IPod Touch and Leopard Server network

At school we have staff and students beginning to explore iPod Touches as a classroom resource. There is no problem getting them to use the school's AirPort network, but some apps, such as Google Earth will not run.
I'm wondering if anyone has experience of using iPod touches in a Leopard Server environment and if they have any tips or hints to share please?
Brian Bowell
ICT Support
Berkley School
Hamilton
New Zealand

Hi Brian,
You really should have to do anything specific on your network to make the touch work with Leopard Server. Here are a few questions to point you in the right direction:
Are you seeing any specific error messages?
Are you blocking any ports on your network?
Have you looked at the log files from a device that is exhibiting this behavior?
Good luck,
Jon

Leopard server networking

I haven't run any version of mac os server before, so most
of my frustration is probably lack of experience, but the
things I am trying to do are easy under linux and seem all
but impossible under leopard server.
My configuration:
I have a dsl connection from at&t that uses pppoe to
connect. They give me a /28 block (i.e. 16 ip addresses).
I am using a Mac Pro for the hardware.
What I want to do is the following:
1: Automatically start up the pppoe connection at boot time,
and re-connect if it goes down for some reason.
Q1a: How do i start or stop a network connection from the
command line?
Q1b: Where are the ppp options to the pppd process set?
Although I don't think i need it for my configuration, I may
need or want to set the proxyarp option. /etc/ppp/options
is a possibility, but it would be nice to set it only for this
particular connection, not all the time.
2: Attach additional IP addresses to the ppp interface
when it comes up so i can run more than one ip based
service on the same hardware.
I can do this via the command line:
ifconfig ppp0 alias <new ip> netmask 255.255.255.240 <at&t gateway>
And i can probably put this in a script at /etc/ppp/ip-up but
it seems like this would be configurable elsewhere.
3: As a side note, why can't the airport extreme basestation
distribute a range of addresses if it is connected via pppoe
the same as it can if connected via ethernet?

Yes, the Cisco is configure for NAT and works fine via the airport and can reach the Server after unplugging and reconnecting the server.
The Server has a static IP address have has the appropriate routes in the Cisco. Again this config worked fine until I upgraded. Additionally, I have a route for FTP traffic to the server from the outside interface.
Apple Firewall is disabled.
It's the strangest thing. If you disconnect the server's ethernet cable and reconnect it the server can be seen again on the network. At that point you can connect using remote desktop and stay on for as long as you wish. Once you disconnect from remote desktop the computer again disappears from the network as if the nic card has gone into hibernate mode. I have tried to change the setting to never sleep and Wake for Ethernet network access. under the Energy Saver utility. Any other suggestions? Is there a config file that I could play with that might help keep the connection alive?
To get the server back on the network, unplug and reconnect and it show that it has been idle for X# of minutes.
Appreciate your input.

Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

My playstation network keeps failing

Every time I try to log in it says psn failed, I have tried resetting router and disabling media server connection. Can anyone help please?

For Playstation support you need to contact the Playstation group directly. Here is their contact page: https://support.us.playstation.com/app/contact_options. It includes live chat, forums, and a phone number if necessary.

Network keeps failing after recent kernel upgrade

I upgraded my kernel this morning to the newest version of 2.6.17, and as soon as I rebooted the Network started saying FAIL each time. Can anyone help me diagnose the problem?
Side note :
I remembered that I had also modified the inittab to use gdm before I rebooted. Would that have any kind of effect?

I've had that problem as well. It's because the modular kernels load the modules at the same time, and because of that which module is initialized first isn't the same at every boot. So the names eth0, eth1 and eth2 for example may change at next boot. Even if you have only one network card, the ethernet over firewire module might be loaded. I solved it by setting eth0, eth1 and eth2 to dhcp, starting them all at boot and starting network in the background (to prevent wating for the two devices that won't start). To find out what devicenames are used, do a "ifconfig -a"
IIRC there is another solution too - you can search through the forums for it.
ATM I'm running a custom kernel with all the network modules built-in - that way the network device names are the same at every boot.

HP Server Drive Keeps Failing

To be fair, I hadn't heard of them until today but if you are a Mitro user then you need to be aware that they are shutting down in six weeks.
Password manager Mitro will shutter itself on 31 August • The Register

Not too long ago we used to pull out our phones just to call a friend, or read a text. Today, we use our mobile phones for just about anything. Chief among these activities is social interaction. During sporting events, this urge to relate to others hits a fever pitch, thanks toplatforms like Twitter, Facebook, and Instagram.Feeling connectedTechnology has always influenced our behavior. But few things have reshaped society like the smartphone – a pocket computer that’s constantly on alert to fetch you the latest news, runs games to keep you entertained and utility apps for every-day scenarios, takes pictures that develop in a fraction of a second, and lets you share experiences on the go. In all senses, the smartphone is perhaps the most versatile broadcasting device ever created.Read more...

No Ethernet/Internet Connection on Parallels 7 Running Snow Leopard Server - Fix?

I have recently installed Parallels 7 on my 2013 iMac, and have both Snow Leopard Server and Windows 7 running great on the Parallels platform.
However, after installing some anti-virus software, "ClamXav" and "MacScan", I need to have the internet connected to my Paralells 7 so I can receive viral updates to both these programs. I am unable to get any ethernet/internet connection on my Paralells 7 running Snow Leopard Server.
I have tried to update the Paralells 7 Snow Leopard Server "network Info" (in SL systems preferences" ... as the same ethernet connection info that I have running my "network connection" on my main OS Mountain Lion, but still no ethernet connection in Paralells 7.
This is a screen grab of the locations where I believe I am able to update my "ethernet" info for Paralells 7 Snow Leopard:
Obviously, I've blurred out the current info in these two windows, for security purposes, but exactly what should be applied to these windows to get my "ethernet" connection in Paralells 7 up and running?
I would think entering the exact same "network info" as appears in my Mountain Lion "Systems Preferences - Network" window, would get me internet connected on Paralells 7 Snow Leopard? Evidently not ... what is needed for me to get this right?
Anyone have experience getting "ethernet/internet" connected on Snow Leopard Server, using Paralells 7?

MlchaelLAX
Since I have been directed to: "NOT waste everyones time on this discussion" the only thing more I am going to do after this post is click on: "Stop email notifications" and never return to this thread again!
Internet access through Ethernet in Snow Leopard Server installed into Parallels 8 on 2011 Mac Mini in Lion:"
I simply don't want to purchase and have to install Parallels 8 .... Parallels 7 should work fine on connecting to the Internet. Also, I was asking about the internet connection issue with the new 2013 iMac (running Mountain Lion 10.8.3 runiing Parallels 7), not a 2011 Mini Mac running Lion with Parallels 8.

Cannot Bind Leopard Server to Windows Active Directory

Trying to Bind new Leopard Server but keep getting an Unknown error. it there an issue with the new Server OS?
This is the error
12/10/07 6:36:37 PM com.apple.launchd[1] (0x0-0x2c02c.com.apple.ServerAdmin4479) Exited abnormally: Segmentation fault
12/10/07 6:37:08 PM Directory Utility236 Step 1 of 6: Searching for Forest/Domain information
12/10/07 6:37:08 PM Directory Utility236 Binding failed with error -14120
12/10/07 6:37:29 PM DirectoryService4626 * +NSCFArray shouldAttemptCheck: unrecognized selector sent to class 0xa0101740
12/10/07 6:37:30 PM com.apple.launchd[1] (com.apple.DirectoryServices4626) Exited abnormally: Bus error

Okay, I have now managed to setup up the server. I did this by creating a Open Directory Master and then binding that to our Active Directory. I have setup Active Directory and LDAP binding on the client Macs.
I then added a user from AD into Workgroup Manager and applied a few preferences. They worked brilliantly. However, the computer Workgroup Manager preferences are not working at all! Is there a different way to add computers to Workgroup Manager (I added them by using the + sign and dragging them in from AD) and is there a way to automatically add a computer once it's joined to the domain, like it goes in to AD?

Exchange server 2010 backup fails

My exchange server backup keep failing
the exchange server 2010 two node dag
netbackup 7.6
I have contacted Symantec support. They believed it's Exchange server problem as "Vssadin list writers"
show Microsoft Exchange writer Retryable error
Any help?

Hi,
Please try to restart Information Store service for testing.
Also try to refer following blogs:
Troubleshooting Exchange 2007 VSS Backups
http://blogs.technet.com/b/exchange/archive/2008/08/25/3406172.aspx
Exchange and VSS -- My Exchange writer is in a failed retryable state
http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx
Thanks
Mavis Huang
TechNet Community Support

Fresh Install, Fully Updated Leopard Server Keeps rebooting on its own

Just upgraded to Leopard Server from Tiger.
Fresh, new install, fully updated.
Only software installed is Retrospect 6 and Drobo client.
My Server keeps rebooting by itself after 5-10 after logging in.
Won't reboot on it's own if I don't log in. The services are running in the background.
But once I log in as admin, after 5-10 mins, it will reboot on it's own.
Any ideas are where I should start looking on how to resolve this?

You're going to get to try to isolate this.
Any details from the crash report? (Applications -> Utilities -> Console.) Basically you're going to have to dig around in the crashes, and (if there's nothing obvious there) then, well, "try different configurations and different stuff".
This could be bad memory or a bad sector somewhere on the disk, for instance. Or a bad processor. Or a corrupt file. Or a bug in whichever Leopard Server baselevel is involved here.
Some steps and some options...
Disconnect all external hardware.
Run the hardware diagnostics for whichever box is involved here.
See if the box crashes if you log in as some other user.
See if the box crashes with no external hardware, or with no network connected.
If the box isn't under warranty (and any user crashes the box) (and if you're familiar with and comfortable with working inside static-senstive electronics gear), crack it open and reseat everything.
If the system is available to restore or you can blank and install, reinstall everything and leave both Retrospect and Drobo, and see if it crashes. Then add one or the other and see if that crashes stuff, rinse, lather and repeat.
Or you can call up Apple and ask for help.

Mobile account users can not log on to the snow leopard server machine?

Hi all,
I've setup a network user and designated it as a mobile account. ** OS X 10.6.2 **
When the user logs out of the snow leopard server machine, home sync tries to sync the local and network home directories. It is never able to connect. The network home directory is automounted and is not the default path /Users. I can see the two home directories on disk.
Anyone else able to have their mobile users log in to the snow leopard server machine without issues?
OS X 10.6.2 **

It was the Sync server was down and did not know it

Log in with AFP brings down Leopard Server

Hello everyone. I'm not really sure what the problem is here so I'll do my best to explain how I got here. The problem is that when I accessed an afp share with the Finder, it made the entire server unresponsive for at least 10 minutes.
Our server is located in a datacenter outside of our office. We have multiple offices and have mobile users, so we chose to colocate it elsewhere. We haven't configured any client machines to use Kerberos or anything like that. I've just enabled a handful of services and we're going to log into them normally. I created all of the users in the Workgroup Manager and discovered that unless their machines are set up to authenticate against Open Directory at login, there's not really a good way to change the password. But even trying to dig deeper I was stumped- I created a test user and added the Open Directory server via Directory Utility to a spare machine. I was able to log into this machine with the account information on the Leopard Server and it was extremely slow because it was not a Mobile account. After configuring the Mobile account, I tried to change the password in system preferences but I would get an error. I found the option in WGM to change the password at the next log on but I was never prompted to change when I logged in. I moved onto another project and left it for later.
The other day I connected to an AFP share in the Finder as the test user and I was prompted to change my password! I figured this would be the best way to have users set their password: enable the change password at next login option and have everyone use AFP once to change their passwords before using other Leopard services. So I selected 17 users and applied that setting and saved it. Now, here's where the huge problem lies. Three times now I have logged in and gotten an error about the username or password being incorrect and then after entering it a second time the entire server becomes unresponsive for at least 10 minutes. Here's the error in /var/log/secure.log (tubes is the name of the server)
Jul 10 15:05:51 tubes /usr/sbin/PasswordService[11150]: client response doesn't match what we generated
Jul 10 15:06:21: --- last message repeated 1 time ---
I couldn't access any services during this time; web, iCal server, Server Admin, Workgroup Manager, ssh. It wouldn't even respond to ping. The next time I was able to get in was 15 minutes later via ssh...
Jul 10 15:32:00 tubes sshd[11245]: /etc/sshd_config line 70: Unsupported option KerberosGetAFSToken
Jul 10 15:32:01 tubes sshd[11245]: Accepted publickey for alan from 66.92.171.175 port 51427 ssh2
It didn't freeze immediately any time except the last time. The first time I had successfully changed the test user's password, ejected the share, and logged back in. Then I tried as another user and it froze. The second time I tried another real user, got the change password prompt, hit cancel, selected yet another user, and it froze. The third time I went to another machine, one without the server added in Directory Utility, and yet another user still, tried to log in and it froze the system immediately. Each time it froze we were first told the username or password was incorrect.
If this adds anything to helping solve the problem, we have what I have considered a separate issue, sshd contantly pegs the processor. While there are multiple sshd threads, at least one almost always looks like this
10649 sshd 99.4% 75:29.45 1 19 51 36K 924K 1492K 21M
Restarting sshd does not seem to help, it's almost always runs at a very high percentange. It's a dual proc system so it really measures around 48% total, but that's still way too high. Could this be related? I had the network admin force quit sshd the first two times the server became unresponsive but it still took several minutes until I could log in, which hints that they aren't related. I'm having a difficult time finding the sshd logs in Leopard to look them up.
Here is some more information to hopefully help. From the AFP Access log, the third time, the user brians logged in and it looks like was immediately kicked out for whatever reason. The first time he used his full name and then the second time I had him try his short name. (I'm changing the IP here) The times don't match the secure.log file strangely, but these are in fact the actual times.
IP 11.22.333.444 - - [10/Jul/2008:15:05:51 -0500] "Login Brian Smith" -5023 0 0
IP 11.22.333.444 - - [10/Jul/2008:15:05:51 -0500] "Logout Brian Smith" -5023 0 0
IP 11.22.333.444 - - [10/Jul/2008:15:06:04 -0500] "Login brians" -5023 0 0
IP 11.22.333.444 - - [10/Jul/2008:15:06:04 -0500] "Logout brians" -5023 0 0
The AFP Error log only has a single notification, and it's from several days ago saying "server shut down." The Directory Services Server log has no entries for today and neither does the Error log. The Password Service Server log has some interesting information. A user named rose is running iCal Server is the log says that the password needs to be changed, which follows the policy I set, but of course iCal doesn't prompt you to change it.
Jul 10 2008 16:01:55 AUTH2: {0x484d6d124c59d5b30000000800000008, rose} password change required.
Jul 10 2008 16:01:55 AUTH2: {0x484d6d124c59d5b30000000800000008, rose} password change required.
Jul 10 2008 16:01:55 AUTH2: {0x484d6d124c59d5b30000000800000008, rose} password change required.
The Password Service Error log has errors on different times than my problems. It's all the same error, registration is finished error, but are likely unrelated. Also, if it helps, we're running in the Advanced configuration of Leopard Server.
I hope this isn't too long of a message, I tried to provide all the details as I am desperate to get a solution. I just need to find a way for users to change their passwords before I roll this out to everyone, and I was hoping the prompt when connecting to AFP was what I needed, but now the system is showing itself to be unstable. Any and all help would be highly appreciated.

I had disabled ssh, thinking that maybe the high proc usage was making the system unstable. I successfully changed the password via AFP twice for one user on my machine. I had someone else do it and it immediately brought down the server. Same thing... I'm really at a loss as to what to do, can someone provide some insight? What logs can I look at for more information? Is there anyway to tell what's happening on the machine during these 10 minutes? The logs I've looked at show nothing.

Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

Hello,
I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4. While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD. I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager. Towards the end of the week though this stopped working. Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding". If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen. My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else.
I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly. I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD. I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
Is anyone else having this issue? Any help would help me keep my sanity.
Thanks,
Dane

Have you had any luck finding a solution to this? The only thing I have found was to unbind and then bind without authentication. Any help with progress on your end would be appreciated!
Nick.

Leopard Server 10.4 Blogs/Wiki and Safari error with www alias and Log Out

I have a Leopard Server 10.5 setup with dns and web services including blogs and wikis setup. If I browse to http://hostname.domain.com/users using Safari 5.0.1, I see that the session is not logged in (i.e. Log Out is not visible. I can login and create a blog and logout with no issue. I can do this on Firefox and Camino as well.
Now, if I browse to http://www.domain.com/users however... the Log Out button is visible all the time in Safari 5.0.1 only - Firefox and Camino show the correct status of a non logged in session. In Safari 5.0.1 it is not possible to login to post or create a blog WHEN the www.domain.com url is used.
I have rebuilt Leopard server twice on a physical and a virtual machine for testing and can reproduce the exact same error. It's a mix of using www.domain.com and Safari. Any other browser works fine and ALL browsers work fine with any other alias pointing to the same site, including hostname.domain.com
Testing on Safari 5.0.1 on the server itself works fine. Testing on clients was on 10.6 and 10.5 and was performed on 4 separate client machines. Browsing on the server was fine but browsing on any client would produce the error when using www.domain.com.
If anyone can offer any suggestions, please help!

I tried several new approaches, but nothing worked so far.
The update to 10.5.5 made things worse. Connections are dropping all over the place, when saving from Adobe programs in particular.
Printing from clients to a Xerox Phaser 5500 works, but choosing a different paper size than the default chosen in the cups admin interface goes all wrong and either prints on the default paper size, but down/upscaled to the chosen paper size or prints on the chosen paper size and down/upscaled as if you were printing to the default paper size. (e.g. default paper size is A4, you choose A3 with an A3 document. Document prints on A4 and is downscaled to A4, or prints on A3 and is downscaled to A4.)
There is no way I can keep this thing in production much longer. I tried reinstalling again, but that did not change any behaviour. Another nice "feature": InDesign disables "edit original" when the path to the linked file contains any directoryname with more than 8 characters in length.
Coupled with a sometimes disappearing "dirserv" (it just stops working until I reboot the whole computer) the decision stands to move away from the Xserve.
Leopard Server 10.5.x just does not seem to work well with windows clients.
We will migrate to a windows server 2003 running ExtremZ-IP for the macintosh clients this weekend. Too bad that Apple does not allow Bootcamp to work on Xserves, at least the hardware would have been useful then.
(As a nice finishing touch, the harddisk partition where all data resides did become corrupt over the weekend. "The volume Daten could not be repaired."
Disk Utility and first aid did show nothing on friday ... saturday after no work being done on the partition this error shows up. The only solution I could find was to reformat the partition and restore from a previous backup. Another weekend down the drain. Sorry for the rant, but 6 weekends in a row is enough.)

Logging in to my Leopard Server network keeps failing

Similar Messages

Maybe you are looking for