I have checked the forward and reverse FQDN many times and it appears
to be correct.
fpamax.fpa.pdx.edu
121.252.176.22
However, I have a problem that I've had from the beginning. In
Directory Access (DA), I have been using the IP address of the server
and not the FQDN as has been advised. I set this up by myself before
anyone told me of this peculiarity (it does say to enter either above
the window, after all.)
So if I try to change it in the client, the client will no longer
connect to the server. If I try to delete the mcx_cache from within
NetInfo Manager, the computer will never connect again no matter what I
do and I have to reimage it.
Also, I started out with NetInfo checked in DA with network filled in
in the box. If I turn this access off and then reboot, same problem --
client will never connect again to the server.
So I'm kinda stuck right now.
I'm using the ldap database on the Xserve (kerberos and the whole nine
yards) but I need to have NetInfo activated to gain the access to the
server. We've pondered whether there are problems with the switch we
have for the lab (an HP switch) but the network guys assure me
everything is fine from their end. Famous last words, huh?
I don't exactly know how to get the lab set up with its own DNS and
DHCP because the network guys have told me I absolutely cannot turn on
DHCP without it screwing up their setup for the rest of the building
(we're not on our own subnet, we are just part of one that encompasses
the whole building.) And they have strongly advised me not to turn on
DNS either. So I'm stuck without someone to come in and correctly
diagnose what's going on.
Thanks for letting me pick your brain on this. Appreciate the help.
Ira
On Wednesday, February 23, 2005, at 08:27 AM, Ed Crelin wrote:
Ira,
First you need to check your reverse lookup to be sure. Use your open
directory server's fully qualified domain name (in proper format,
should be what you named it when you first created it mine is mhs.lan
for mount holly school), open up terminal on the server and type
"nslookup www.yourserver.name" without the quotes, hit enter
it informs you that ns lookup is an old command etc but it should
return you the IP address of you server, do the IP address and it
should tell you its domain name. That is your reverse lookup.
If that doesn't work nothing will.
Second, You need to manually point to the server for authentication
especially if you are not providing DHCP services.
You do not need NetInfo and should not use it it is superfluous. Also
if you have changed any of these types of settings as you have been
working on this over time you should delete the entire mcx_cache in
Directory Access on the clients to start fresh it keeps old info and
gets corrupt easily.
If you have problems with any of the above and they won't help you you
can do as I did and create your own little universe for the lab (DNS
DCHP LDAP) and as I did allow access beyond your server by letting the
clients find the network "around" yours by manually putting
alternative DNS entries in the client network prefs panel (your's
would have to be the primary or first in the list). It is really
pretty easy to do, once I found out how to do it I reloaded the server
from scratch and had it up and running in twenty minutes.
Good luck, Lemme know how you make out.
Ed
