[Anonymous]

I was trying ProFTPd again last week. The fink distribution is the best one to use. I had problems getting the distribution from proftpd.org working.

The fink distribution had the fixes in to tweak it for PAM auth to be compatible with Panther.

Things i tested:
sql auth worked
anonymous ftp worked

I haven’t fully tested it, and used it with the reverseDNS turned off.

Good luck!

[Anonymous]

Dave,

We’re trying to do the very same thing. I was hoping I’d find some ideas here. I’ve talked with an Apple tech and he verified that using an OSX server as a login “agent” for clients will work just fine, IF you can figure out all the LDAP mappings with eDirectory. There doesn’t seem to be much documentation on that yet. Hopefully, all will be answered in the MacOSXLabs webcast February 17th.

–> John

[Anonymous]

Any updates on this?

This is the only thing keeping me from replacing my aging OS9 mailserver with a brand new Mac OS X Server one.

FVR

P.S. I forgot my password and registration email adress… d’oh!

[Anonymous]

I have been working on trying to get this working for the past few days. Talk about lost days. I can get very close and then it falls apart. Most of this comes down to Perl issues. MySQL and Apache with mod_perl are a breeze to install. The furtherest I have come with Request Tracker is to run make testpdeps. This gives a list of three bundles I can’t install for the life of me. CPAN craps out, so time to do it by hand. I am to the point where I have edited three makefiles so far.

Documentation is limited. Mr. Boksa has some good docs. You can find them at http://www.boksa.de/tutorials/rt3_macosx.mpp

[Anonymous]

After a tiny bit of investigation, I have determined that when the user logs on initially, no tickets are issued. It seems apparent that the logon is occurring independent of the KDC. How do I get the login process to acquire tickets? TIA.

[Anonymous]

Actually, NAT needs to be done in separate steps and quite manually.

You need to turn on NAT first of all.

You need to create firewall rules to allow for those addresses:ports to be forwarded from one address to another.

The biggest part is the /etc/nat/natd.conf.apple file:

interface en0
dynamic no
log no
log_denied no
deny_incoming no
use_sockets no
same_ports no
unregistered_only no
reverse no
proxy_only no
clamp_mss no
redirect_port tcp xxx.xxx.xxx.xxx:3389 3389

The “redirect_port” attribute has to be manually added to this file(as the plist screwes this up and isn’t working properly), and then you need to change the immutable flag on the file: chflgs uchg /etc/nat/natd.conf.apple.

[Anonymous]

Thanks for the reply. After numerous starting and stopping of services I could not get this working. However, for other reasons I had to reboot the server this morning. When I got back to this it suddenly started working. Once again it seems Apple is taking a page out of the Windows book where rebooting fixes a world of problems. 😉

[Anonymous]

I’ve around 10 imap accounts on a 10.2 box that I’d like to migrate onto our 10.3 xserve. I’d like to use the mail server that comes with 10.3 server. Is there an easy way to do this?

[Anonymous]

I have been digging around with this and now believe the ‘user/$USER’ arguement is correct.

However, there are still no logs anywhere I can find to help me debug this. One thing I did find is that in the SMTP log, when relay=procmail; delay=1. I believe this means the message is not being sent but rather held. I really need someone to help me debug this problem or at least point me to a log somewhere of procmail activity. TIA.

[Anonymous]

btw; I have 2 accounts set up on this server, 1 and 2 and the root account lets say. I can log in with all 3 via ssh and do work fine, so if I have aftp enabled and running via the server admin (as i do) i should be able to connect via afp with all those acocunts right? or atleaste with root..but none of them work, 10.3 client afp browser just keeps coming back with incorrect password. any ideas or am I missing something vary obvious since i know this is a fairly simple thing to set up.

thanks again.

[Anonymous]

Thanks for the reply. I had the home directory stuff working but it was the other mount points that were at issue. You are the first one I found to confirm that the code is broken, even Apple support has not said that to me.

The only other thing have a question about is why you think custom is not needed.

[Anonymous]

Some people have had success with netscreen. You can do a search for the limited comments on the subject. I am trying to get it to work right now, and am not having much success.

[Anonymous]

Thank you so much for your help! I am going to re-do everything this morning.
I knew it had to be some crazy little detail like that. (aside from the fact that .local just didn’t look quite right to me) 😆

[Anonymous]

I can post it here. It will seem convoluted but it works. You must do this using the remote server tools as this does not work if you do it on the server itself.

First, connect to the desired server share(s) using Finder (command-K) on a client machine with the remote server tools installed. This sets up the correct path for remote connections. I suppose if you were a little more savvy with OS X then I, you could probably type it in manually but this is the easiest way for me to be sure it is right.

Next, fire up the Workgroup Manager and go to the groups tab. Highlight the desired group to automount the share(s) you connected to above. Then select “Preferences” in the ‘View” pull-down menu (or press shift-control-R). Click on the ‘Login’ icon and this should open the “Login Items” panel (make sure that is the tab highlighted). Then drag the connected share(s) from your desktop into the panel. With that share(s) highlighted, make sure you check the box to “Mount with User’s name and password.” Click the “Apply now” button and continue with other shares and groups as necessary. That should do it. Good luck.

[Anonymous]

Does anyone happen to have an example set up/screenshot where this actually works?

Right now I have the Xserve using the AD server’s IP for DNS. Resolution seems to work, and records on the AD server seem right. Do I need to add any records to the Xserve?

Also, the AD server is using “.local” instead of “.com” could this have any effect on it?

[Author]

Posts