[mgaslowitz]

Having the server manage both the public and private was the headache (and obviously not the most secure), so I dropped the server behind a external firewall (which now has the public ip), giving the server only a private ip with dns working properly, open directory singing, and clients machines binding left and right.

[mgaslowitz]

ok solved afp….

http://www.macosxhints.com/article.php?story=20070226213016446

[mgaslowitz]

on the off-chance someone will look at this on a Sunday…

So the server has two ports:
public 65.202.106.66
private 192.168.2.1

running “sudo change ip -checkhostname” from the server returns

Primary address = 65.202.106.66
Current HostName = gadisputes.com
DNS HostName = gadisputes.com

running “host 192.168.2.1” from a client returns
1.2.168.102.in-addr.arpa domain name pointer xserve01.gadisputes.com.

running “host xserve01.gadisputes.com” from a client returns:
xserve01.gadisputes.com has address 192.168.2.1

When I went to promote the server to Master is wanted the realm to be “GADISPUTES.COM” and through these efforts have used that and also “XSERVE01.GADISPUTES.COM” but the results are always the same…

I cannot get the clients to bind to the directory and AFP won’t work at all.

I can access the server with SSH, FTP, webmail, ect using local and hosted accounts, but any attempt at using a network login or command-k (connect to server) brings AFP down.

Help.

[mgaslowitz]

Wicked. Thanks guys.

[Author]

Posts