Re: Newbie: 2DC's error 4004

Thank you for replying Kevin,

I was unable to attach to the newsgroup over the weekend: "temporarily
Unavailable"...too bad that is when i try to do most of the work when it is
not "live".

Currently, on the Main server, I have DNS forward looking to delta-1 the
remote server.
On the remote server, DNS is not configured.
Having said that, the remote server does recognize some addresses on both
subnets. (forward and reverse lookup zones).

I went to DNS--> Action--> Configure New --> and then I came here and typed
what I was doing.
I think the cheeky little thing went and configure itself while I was out!

On the remote server it shows under forward lookup zone:
megastream.local and under type it says "Active Directory Integrated Primary"

Is this correct?
Arrgh....

Liam



"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Liam <Liam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Greetings,
> >
> > I am new to DNS issues and would greatly appreciate any help.
> >
> > SITUATION
> > *********
> > We have one domain over two locations connected by a VPN persistent
> > tunnel. For 1 year we only used SBS2003 that hosted all data and
> > Sharepoint.
> >
> > 1 month ago I added a Server 2003 box to the remote location to act
> > as local data store.
> >
> > Now we have some crazy errors happening. Some people cannot connect
> > their laptops to the internet from home?? weird
> >
> > The main server SBS2003 has error logs that are full of 4004 and 4015
> > errors. As well as many, many 6702.
> > The new box in the remote location has NO error messages. It was
> > promoted to DC by DCPROMO.
> >
> > CHALLENEGE
> > *********
> > I suspect that I need to create a forward lookup zone but I am not
> > sure of the process or the logic behind this and therefore am
> > reluctant to implement. Also I would hazard a guess that DNS has not
> > been setup on the new Server 2003.
>
> All you really need to do is install DNS on the remote DC, the zone will
> replicate through Active Directory to the remote DC, without further action
> from you. (Provided zones are stored in Active Directory) Once the zone has
> replicated then you should add trhe remote DCs address for DNS on both DCs.
> (And members for that fact)
>
> >
> > One users' PC has two IP addresses listed in the nslookup. One for
> > each subnet.
>
> Two IP addresses?
> Can you clarify this, because you should only have one, then your router
> will take care of the routing, provided you have set up static routes .
>
> >
> > INFORMATION
> > ***********
> > SBS Server 2003
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : corporate
> > Primary Dns Suffix . . . . . . . : Megastream.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : Megastream.local
> >
> > Ethernet adapter Server Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> > Connection Physical Address. . . . . . . . . : 00-11-43-32-58-83
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.10.13
> > Subnet Mask . . . . . . . . . . . : 255.255.254.0
> > Default Gateway . . . . . . . . . : 192.168.10.15
> > DNS Servers . . . . . . . . . . . : 192.168.10.13
> > Primary WINS Server . . . . . . . : 192.168.10.13
> >
> > The Remote Serever 2003
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : delta-1
> > Primary Dns Suffix . . . . . . . : Megastream.local
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : Megastream.local
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
> > Physical Address. . . . . . . . . : 00-02-A5-08-C1-B4
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.190
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.0.1
> > DNS Servers . . . . . . . . . . . : 192.168.10.13
> >
> > Any help would be just splendid!
> >
> > Liam
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
.

Relevant Pages

  • Re: dynamic DNS
    ... My main server has a static IP and remote server with dynamic IP. ... it isn't safe to do this unless the DNS server is behind a firewall ... Find the Forward lookup zone for which your server is PRIMARY and ...
    (microsoft.public.win2000.dns)
  • Re: Virtual LAN Problem
    ... Gateway device and MANUAL DNS settings to get it to work. ... connectivity with the remote LAN and from the remote LAN. ... Confirm a decent tunnel by pinging the remote site internal clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be expensive, and I can't see a benefit at the moment. ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • RE: vpn and joining remote computers
    ... Windows XP is not configured to use a local DNS server. ... Use remote Small Business Server as DNS of this client: ...
    (microsoft.public.windows.server.sbs)