Re: Domain Controllers

From: Candace Sparks (consultants1_at_comcast.net)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 14:53:10 -0800

The configuration shows an alternate DNS address of 4.2.2.2. They have DSL
through Verizon. What is with that address?

The client showed me that the mapped drive was no longer there, of course
when they reboot it is active again. As far as the autodisconnect feature,
that could be the reason why they can't access the software database when
they get to work in the morning. So, if that is the reason, is there a
solution for that? The computers that have the problem are the ones that do
not shut their computers ofat night.

Candace Sparks

"ptwilliams" <ptw2001@hotmail.com> wrote in message
news:u0WmIfcCFHA.3436@TK2MSFTNGP12.phx.gbl...
> That configuration is fine. There's no real need to change that.
> Although...you should point to another DNS server for redundancy. So you
> might want to have each DC point to themselves as the second DNS server
> option in TCP/IP.
>
> When you say their drives don't stay mapped, are you referring to the
> auto-disconnect feature whereby after a period of time, the connection is
> severed and the drive has a little red cross on it? If so,
double-clicking
> the drive should reactivate the connection. Or are you saying the mapped
> drive is not there next day?
>
> Have you disabled any services, or are you filtering ports/ connections
> between systems?
>
> Are you seeing any errors and warnings in the logs of the DCs and the
> computers that are exhibiting this behaviour?
>
> --
>
> Paul Williams
>
> http://www.msresource.net/
> http://forums.msresource.net/
>
> "Candace Sparks" <consultants1@comcast.net> wrote in message
> news:xNednX77Pu8gG5zfRVn-vw@comcast.com...
> The ip configuration shows the DC1 pointing to DC2 for DNS, and DC2
pointing
> to DC1. Will having them point to themselves possibly fix the flaky
> connection problem?
> The computers that have the mapping problems are the ones that do not shut
> down their computers at night.
>
> "ptwilliams" <ptw2001@hotmail.com> wrote in message
> news:%230LKLCXCFHA.900@TK2MSFTNGP11.phx.gbl...
> > There's a number of questions here. I'll set this thread off by
tackling
> > the first one. Hopefully, this will help with the other questions, as a
> lot
> > of these type of problems are DNS problems.
> >
> > The PDC/ BDC setup is no more. Windows NT5.x domains are multi-master
> > domains, which means that each DC holds a writeable copy of the domain.
> > There is the need for a single-master setup in some instances, but
> generally
> > all DCs are equal.
> >
> > DNS is all important, as it's used for locating AD services, etc.
> >
> > All domain members need to point to internal DNS servers. These are
> usually
> > your DCs. The DCs should point to themselves (if they are DNS servers),
> and
> > the DNS zones need to be set to automatically accept dynamic updates.
> >
> > --
> >
> > Paul Williams
> >
> > http://www.msresource.net/
> > http://forums.msresource.net/
> >
> > "Candace Sparks" <consultants1@comcast.net> wrote in message
> > news:nLOdnXu5iqhtppzfRVn-1w@comcast.com...
> > I am reviewing the computer set up at a client office. I did not set up
> > their computers or network. They have 2 servers, 1 2003 server and 1
2000
> > server, both are running active directory. I am familiar with the PDC
and
> > the BDC under Window NT 4.0, is this the same thing? It looks like the
> > users are the same on both servers.
> >
> > Each server is looking at the other server for DNS. The 2000 server is
> also
> > the DHCP server and WINS server.
> >
> > Computers on the network are having issues keeping drives mapped. Also,
> > when they attempt to access their main software, they get an error that
> they
> > can't access the database? It seems that part of this might be a timing
> > issue.
> >
> > Any ideas?
> >
> > Thank you for your help in advance!
> >
> > Candace Sparks
> >
> >
> >
>
>
>

Relevant Pages

  • Re: No DC in Active Directory
    ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS. ... The second server ... the first server now shows no DCs in the Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client computer internet connection problems
    ... subnet, Default Gateway, correct DNS entry/ies). ... his TCP/IP Configuration settings then he is not going to be able to join ... O*N*L*Y the internal DNS Server IP Address..... ... join the computers to my server domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Replacing Win2000 Domain controllers
    ... Normally you can rename a computer in the domain without any problem, maybe the account did not have the correct rights in AD. ... If you remove it give time for replication and also check that all entries from the DNS management console are deleted and also from the DNS zone properties under the Name server tabs, if it was a DNS server. ... I've tried renaming computers in the domain before and ...
    (microsoft.public.windows.server.migration)
  • Re: Sharing a drive on my computer with others
    ... SBS 2003 needs to manage DNS and really likes to manage DHCP, ... You need to use the wizards on the SBS server to get it all working properly. ... I can't ping any of the computers within the domain. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Error adding computers to domain
    ... > add Windows 2000 computers to a domain. ... > all because that function isn't necessary on that server. ... While not required by the server, the clients would certainly see a benefit. ... ever use an ISP's DNS server. ...
    (microsoft.public.win2000.advanced_server)