That be you.

I remember because I was floundering not knowing what the strange looking
domain name meant

Don't think I remember the resolution though. FandR (Flatten and Reinstall)
comes to mind.

--
Larry

Please post the resolution to
your issue so that all can benefit.


"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:%23lb2JYcmIHA.4684@TK2MSFTNGP06.phx.gbl...
> Was I 'the AU MVP' that picked up on that error?
>
> The basic premise is that the OP did a silly thing, named his AD in
> relation to his public DNS name space. There is no reason, and some good
> reasons not, to do so. If the installation is new and not yet fully
> committed to I'd start with 'format C:' and rectify the error by putting
> the server into its own namespace. If the install has been committed to I
> would discuss the pros and cons with the owner and _most probably_ 'format
> C:' but maybe 'work around' the problem.
>
> BTW: This is not an 'SBS' thing, it is 'pure AD + DNS'. There is _no
> reason_ for your AD DNS name to reflect public records and anyone who
> wants to argue this point should 1st consider that I have had this
> argument with the highest levels of MS AD design. The argument was not
> 'conclusive' in that 'we agreed to disagree' on a couple of things which
> can be done under either model, naturally working in one and easily worked
> around in the other.
>
> The problem occurs because people approach it a$$backwards. They ask
> themselves 'Why should I create a new DNS domain when I have one which
> already exists publicly', the question they should be asking is 'I am
> implementing a DNS zone for my own personal use, is there any reason why
> this should in any way relate to public records'. The answer is almost
> always 'NO'.
>
> The problem won't exist in Cougar. SBS Dev have recognised the need to
> address this and without special effort it will be impossible to name your
> AD in relation to public DNS. People wishing to do so will _have to_ edit
> a file in order to allow it. SBS Dev are smarter than MS Dev.
>
> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
> news:u$o87XbmIHA.6064@TK2MSFTNGP03.phx.gbl...
>> The last time we saw this the poster had added the country extension to
>> the domain controller name as in:
>>
>> myserver.com.au
>>
>> instead of myserver.local or myserver.lan
>>
>> Made quite a mess, and only one of our AU MVP's could figure it out.
>>
>> Please post the results of the following command:
>>
>> ipconfig /all > c:\iptest.txt
>>
>> from both the server and a workstation. Please tell us which is which,
>> and there is no need to change anything if you really want assistance
>> with this, but you could add some random characters to the server/domain
>> name if you are worried about bots or zombies picking it up.
>>
>> as in M*I*C*R*0*S*TdotC*O*M
>>
>> --
>> Larry
>>
>> Please post the resolution to
>> your issue so that all can benefit.
>>
>>
>> "Anthony" <qwer@awwewe.com> wrote in message
>> news:uD%23oCqamIHA.4480@TK2MSFTNGP03.phx.gbl...
>>> Hello. I hope someone can help with the issues I have.
>>> Im having problems with machines taking up to 20 minutes to logon to the
>>> network, this does not affect all machines just random ones.(most
>>> machines)
>>> We have used a network sniffer to look at the traffic from the client
>>> machines and for some reason the client authenticates fine with the
>>> local
>>> domain controller, and know which site it is in, but then goes off
>>> talking to
>>> other domain controllers around the world in other sites. Im not sure if
>>> this
>>> is when it is trying to pull down the group policy, does anyone know why
>>> this
>>> would happen?
>>> Also if I ping my domain name the reply changes every so often, and its
>>> always from a DC in another country site, if we add a host entry for the
>>> local DC to the domain name it fixes the issues on some machines.
>>> Also on almost all machine I get the error in the event log "The
>>> Security
>>> System could not establish a secured connection with the server
>>> DNS/blah.blah.blah.com. No authentication protocol was available."
>>> What does this mean?
>>>
>>> I know that's all a bit random so any help would be appreciated.
>>>
>>> Thanks
>>
>>
>
>