On 03/10/2008 14:42 PM, "David Stodolsky"
<email@hidden> wrote:
Is there a specific problem here, with perhaps specific
informational items,
or just Apple didn't read your mind.
Silent failure of the Standard Install and later the VPN doesn't turn
on as was requested during the Install.
And what steps did you take to troubleshoot?
See error message below.
Make sure brain is engaged, before putting mouth in gear ;-)
Since DNS config. is the first item on the agenda, it is easier
to do
an Erase and Install, in practice. Seeing as the error messages
tend
to be opaque, even determining what is wrong would likely take
longer
than starting over. So, you have a theoretical point, but in
practice
it doesn't apply.
I dunno. DNS outages generate some very specific errors in my
experience.
Sure:
Jan 10 10:33:05 WI named1020: /etc/dns/publicView.conf.apple:1:
undefined ACL 'example.com'
Doesn't matter, if you could spot this as being a DNS problem, as
opposed to a disk problem. Reinstalling was the only way out.
According to Support, Open Directory is populated with crap during a
Standard Install, if the DNS name is off. And even if that could be
fixed, it would still take a lot of time on the command line to fix
the DNS and make sure everything else was right.
Or, you could make sure your DNS was right BEFORE you start. Prior
Planning
Prevents Poor Performance.
Good manuals allow Prior Planning.
The distinction between internal (to OS X Server) and external DNS is
crucial to understanding what is going on here. It was explained
earlier.
Yesterday, I tried again to start an Advanced Configuration, with
point and click instructions in front of me. A single error meant I
had to do an Erase and Install. But this was only after the Server
Admin DNS tool "fixed" the error, and "host" and "changeip" on the
command line confirmed all was well. Can you say, "Human interface
from Hell"?
Why would you have to change the IP address immediately after the
install?
changeip -checkhostname
What I want to know is why did "host" and this give an all clear and
then a lookup from a client showed a faulty nameserver entry. It was
still "ns" even though that had been replaced in Server Admin.
I know *how*. That's not the question asked. The question asked is
*why* you
would have to change the IP immediately after the install.
changeip -checkhostname
doesn't change the IP.
Try man changeip ;-)
I have a compact way of expressing myself, but shouldn't someone at
your level immediately grok a verbatim command line?
Read first, think, then respond. It is easy and saves time:
"changeip" on the command line *confirmed* all was well
That's a fairly abnormal situation, and reeks of really bad
preinstall
planning. That's one of the reasons Apple provides a worksheet, so
that you
can have various bits of information, like the correct IP address in
front
of you. Can you say "You're leaving out quite a few pertinent
details
there"?
Note that I am just trying to duplicate a 10.2 configuration that has
been running fine for years.
It is entirely possible to successfully duplicate a functional
configuration
without doing it the way you did, and saving oneself a lot of pain.
Your statement doesn't relate to actual events.
I remember explaining in detail what I did, the network configuration,
etc. etc.
Please reread qualifications in order to avoid foot-in-mouth
disease;-)
I'm not the one unable to successfully set up Mac OS X 10.5 Server.
Please to explain why duplicating an existing configuration would
require
you to immediately use the same IP, when there are a host of rather
obvious
reasons why this is a Very Silly Thing To Do, among them:
Which is why I didn't do it. When I said 'duplicate', that referred to
functionality, not to specific IP numbers, etc. One has the hope that
a 10.5 Server will do everything that a 10.2 Server does, at least.
The point was that extensive planning wasn't necessary, since the
general approach had been used for a long time.
dss
David Stodolsky email@hidden Skype: davidstodolsky
