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?
>
>>>
>>>
>>> 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.
>
>
>
>>>
>>> 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.
As well, I can easily see where this would cause you DNS problems, which is
probably why most people don't do that.
>
>
>>
>> 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.
>
> 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:
It makes you do dumb things like having to change the IP address immediately
after installing.
It makes it harder to revert back to the existing configuration, and
troubleshoot the new one without further silliness involving changeip
--
John C. Welch Writer/Analyst
Bynkii.com Mac and other opinions
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
