Re: Domain Controllers
From: ptwilliams (ptw2001_at_hotmail.com)
Date: 02/04/05
- Next message: ptwilliams: "Re: AD"
- Previous message: ptwilliams: "Re: HOw to set password policy"
- In reply to: Candace Sparks: "Re: Domain Controllers"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Feb 2005 09:01:23 -0000
> The configuration shows an alternate DNS address of 4.2.2.2. They have
> DSL through Verizon. What is with that address?
That's a valid address - that's an old one - a big class A range.
However, it's a public address. That address is for vnsc-bak.sys.gtei.net,
which I would assume (we can easily find out if you want) belongs to
Verizon.
That address shouldn't be referenced by any of the internal domain members.
They should all be pointing to the internal DNS servers. The internal DNS
servers should the forward DNS requests to public DNS servers, a proxy
server, whatever...but nothing inside should reference this (other than,
perhaps you proxy server).
> 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.
Here's some info. on Auto Disconnect:
-- http://support.microsoft.com/?id=138365
This is more than likely a DNS issue. With the DNS address, they probably
can't contact a DC/ KDC, which will cause authentication problems and
timeouts, etc.
-- Paul Williams http://www.msresource.net/ http://forums.msresource.net/ "Candace Sparks" <consultants1@comcast.net> wrote in message news:zOqdnXHBn-A0N5_fRVn-jA@comcast.com... 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 > > > > > > > > >
- Next message: ptwilliams: "Re: AD"
- Previous message: ptwilliams: "Re: HOw to set password policy"
- In reply to: Candace Sparks: "Re: Domain Controllers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
