Forum Replies Created
-
AuthorPosts
-
OkiKowai
ParticipantJust wanted to add that after a few years, this still resolved the issue for me. It was really annoying as the first login failed with the error and then all subsequent logins worked. Thank you so much for finding this way back when.
OkiKowai
ParticipantI am having very similar issues and am considering moving back to the 10.4.10 AD plugin. However, without doing the install for 10.4.10 server onto some other hardware, does anyone have a copy of this plugin that I can get? It would be greatly appreciated.
Keith
June 2, 2008 at 5:08 pm in reply to: Leopard’s Login Window Doesnt Get AD Password Expiriation Warnings #372984OkiKowai
ParticipantBy the way, my machines are not running leopard, they are running Tiger. Most are 10.4.11. They get no warnings and once the password expires, the window just shakes not giving them any indication why it won’t let them log in. They go to a PC, it asks for a new password and voila, they are good to go. But obviously, this should work from the Mac the whole time. No idea what the cause of this is.
April 28, 2008 at 1:45 pm in reply to: Leopard’s Login Window Doesnt Get AD Password Expiriation Warnings #372463OkiKowai
ParticipantI too am seeing this issue. And of course this lack of warning also causes the machine to not allow the password to be changed from the Macs. It just shakes at them. If they go to a PC it tells them that their password has expired and forces them to change their password. If anyone has more information as to what could be causing this or better yet a good workaround/fix, that would be greatly appreciated. Thanks.
July 6, 2007 at 8:58 pm in reply to: Emulex switch (non-XSan), XServe, XRAID drives not mounting on reboot #369451OkiKowai
ParticipantI will have to look to see if there is a specific version. But the switch is the Emulex 375. It is the 20-port switch. Now I am regretting completely not pushing on this with Apple while it was still in the first 30 days. If we hadn’t had other issues we were dealing with which were more important, we would have. *sigh* I guess we are stuck now. The only other solution I can think of is getting one of the newer 4-port Fibre cards. But like alot of things, it costs money to do that. Sure the company in question has the money, but no one likes to shell out a thousand dollars when they already invested several thousand on a fibre switch. Thank you for your response. It is good to know that others had the same problems. Although quite frustrating that Apple just told you to reseat to fix the issue. I will keep plugging away at this, maybe even contact Emulex directly and complain. Who knows, it might get us somewhere.
Keith
P.S. The delay in responses has been partly caused by the birth of my second son. 8) Which is a good thing, but it has meant that I have been busy with this right before the birth and now after. Hopefully if someone else comes up with a good suggestion I will respond quicker. Thanks again for everyone’s help.
June 22, 2007 at 3:42 pm in reply to: Emulex switch (non-XSan), XServe, XRAID drives not mounting on reboot #369345OkiKowai
ParticipantUnfortunately from my research, Emulex switches are FC-AL type and the QLogic are FC-SW type. So they work differently. All the settings I have are setup as they should be based on Apple’s website and what little is on Emulex’s. We are going to look one last time for updated firmware, last time I couldn’t find any firmware updates at all. (not even something saying there are no updates).
The settings that I am curious about are the settings regarding notifications. The way it is described the Target ports (XRAIDs, etc) should be setup to only send notification messages and Initiator ports (X-Serve) should be setup to only receive messages. The reason I am curious about this is that when you restart the server, it is not able to tell the XRAID that it is down or that it is back up. However, I know I have heard of the troubles that can be caused if open the notifications up completely between the two, but it was not fully described what those troubles were. *sigh* So I am wondering whether or not to try the changes or not.
I am caught in a quandry because to call Apple and get support on this will cost the $700 Enterprise support fee. I have no idea if there is a wrong setting, something wrong that can be cleared up, or the switch itself is actually defective. This has been really frustrating. If we hadn’t had some problems when we first setup all the other things, we might have gotten the support early on when we were still in the first 30 days, but of course that didn’t happen.
Well if anyone has any other ideas, I would be very happy to hear them. Thanks Danomatic for your response, it at least gave me some hope for a little bit. And was still better than nothing.
-
AuthorPosts
Recent Comments