Re: Another companyweb cannot be displayed

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I hadn't considered that about Enterprise admin-folk. Thanks for the
perspective!!

SuperGumby [SBS MVP] wrote:
For others (and Bobby, I suppose).
There is a not minor complication involved here, the question of the
'big domain'. It seems the site was once part of this 'big domain' and was
only partly 'seperated' from it. I _suspect_ that the 'big domain' boys (and
gals) are 'Enterprise' admin type people and that SBS was implemented by a
similar mentality sort of person. It is easier for an SBSer to move to
'Enterprise' after learning well than it is for 'Enterprise' to come to SBS
space (or for a camel to walk through the eye of a needle).

"Bobby" <robert.gomez-reino@xxxxxxx> wrote in message
news:1162859345.593554.233110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Super, now I see what you mean. Since I was connecting via ssh tunnel
through a linux machine I didnt realize the IP was visible from
outside...at least it seems to have all ports blocked. I will tell them
to be more carefull with that!
Thanks.

SuperGumby [SBS MVP] wrote:
Though mostly correct this makes some assumptions (mostly OK from
previous
items in the thread).

My jury would be out on whether I would point each DC in an AD to itself
for
DNS or each to whichever I considered 'primary' with itself or the one I
considered 'secondary' as alternate. I consider it a bit 'moot point', if
SBS' DNS is unavailable there is something wrong with SBS, everything
else
should be shut down :-)

"Justin Brown - SYNACS" <jcbrown@xxxxxxxxx> wrote in message
news:1162857697.134157.311440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
As a DNS client, SBS should point to itself only. The only machines
that should use the Server 2003 SE for DNS are workstations, which
should point first to 2003 SBS, then 2003 SE.

The same applies to your SE (server01). This server should use itself
for lookups only, otherwise you lose the only reason to run two DNS
servers, which is failover redundancy.

Changing these values will reset the TCP/IP properties so expect to
lose your TS or RWW connection and make absolutely sure you have it
right so that when the adapters come back you can reconnect remotely.


Bobby wrote:
Justin Brown - SYNACS wrote:
Thanks. That information was a necessary prerequisite (next
time!!!!!).
The assumptions at this point will be that this network was
configured
in this order:

-Server02 is deployed as the root of dom.local
-Server01 joins dom.local and is then promoted to Domain Controller.

Server02 should be using itself to resolve names. That should be
fixed.
Justin the prefered DNS server in server02 is the replica (server01)
you say I should change it to server02 so it resolves itself the
names?
May this cause somehow that i loose the remote connection?
Bobby



.

Relevant Pages

  • Re: SBS2003 - Cannot restore GPO following Article 888943
    ... As to the second DNS setting, the system worked quite well prior to ... forwarders on the SBS server DNS. ... >another installation of SBS 2003? ... >This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Go back to pointing the external NIC DNS Servers to the SBS server IP ... make sure the DHCP Client Service is running on the server. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: Help! w/ Upgrade-Installation problems with OMA/ActiveSync and
    ... Am I misinterpreting the summary doc from CEICW re: dhcp and dns settings ... under the SBS DNS forwarder tab. ... DNS server addresses I assume from the DSL modem. ...
    (microsoft.public.windows.server.sbs)
  • RE: ICW Problem Error 0x80072581 Deleting the DNS record external NIC
    ... Make sure your SBS internal and external network interface DNS is ... Do you have any site hosted in the SBS server other than the four ... Check if the PUBLISHING record in DNS is an A record. ... check to see if there is a name record 'publishing'. ...
    (microsoft.public.windows.server.sbs)