dcdiag errors
in [Active Directory]
|
Prev: active directory problems"naming information cannot be located because the logon attempt failed "
Next: Domain membership test: Failed
From: Ace Fekay [MVP] on 19 May 2008 23:48 In news:uxFRSXduIHA.2068(a)TK2MSFTNGP05.phx.gbl, Phil Loper <phil(a)nospam-gracelivingcenters.com> typed: > Should dc2 be setup as active directory like dc1 or should it be set > up as a secondary? Yes, I believe that is your better bet. Promoted it to a DC. You should have at least two DCs anyway for fault tolerance. With AD, there are numerous advantageous using a DC for DNS server, one of which is AD integrated zones. Member servers don't have the ability for this feature because it means the zone data is stored in the actual AD database. Ace
From: Ace Fekay [MVP] on 19 May 2008 23:49 In news:OrX8jYduIHA.2068(a)TK2MSFTNGP05.phx.gbl, Phil Loper <phil(a)nospam-gracelivingcenters.com> typed: > Finally got the other rras server working. We tried using the pix for > vpn, but there were problems with the cisco client not working with > the exchange owa. It has been a long time since we tried that, so > cisco may have fixed the client by now, so I will look into it. Thanks! What kind of problems with OWA? I haven't heard of any, at least until now. Do you mean when people are outside VPN'd in and then try to use OWA? If so, how are they connecting? With the external name or the internal private name of the OWA site? Ace
From: Phil Loper on 20 May 2008 13:32 Ace Fekay [MVP] wrote: > In news:OrX8jYduIHA.2068(a)TK2MSFTNGP05.phx.gbl, > Phil Loper <phil(a)nospam-gracelivingcenters.com> typed: > >> Finally got the other rras server working. We tried using the pix for >> vpn, but there were problems with the cisco client not working with >> the exchange owa. It has been a long time since we tried that, so >> cisco may have fixed the client by now, so I will look into it. Thanks! > > What kind of problems with OWA? I haven't heard of any, at least until now. > Do you mean when people are outside VPN'd in and then try to use OWA? If so, > how are they connecting? With the external name or the internal private name > of the OWA site? > > Ace > > > > Sorry, I meant to say Outlook. They would not be using OWA over the VPN. They just never could connect to the Exchange server when using the Cisco client. I think there were also problems connecting to SQL databases.
From: Phil Loper on 20 May 2008 13:36 Ace Fekay [MVP] wrote: > In news:uxFRSXduIHA.2068(a)TK2MSFTNGP05.phx.gbl, > Phil Loper <phil(a)nospam-gracelivingcenters.com> typed: > >> Should dc2 be setup as active directory like dc1 or should it be set >> up as a secondary? > > Yes, I believe that is your better bet. Promoted it to a DC. You should have > at least two DCs anyway for fault tolerance. With AD, there are numerous > advantageous using a DC for DNS server, one of which is AD integrated zones. > Member servers don't have the ability for this feature because it means the > zone data is stored in the actual AD database. > > Ace > So the DNS on both domain controllers should be set to Active Directory Integrated, right? Thant is how I have them now and just wanted to make absolutely sure before I turn off DNS on the member server, which is set up as secondary DNS server. Thanks again for all your help.
From: Ace Fekay [MVP] on 21 May 2008 07:43
In news:%23Vqb69puIHA.5268(a)TK2MSFTNGP06.phx.gbl, Phil Loper <phil(a)nospam-gracelivingcenters.com> typed: > Sorry, I meant to say Outlook. They would not be using OWA over the > VPN. They just never could connect to the Exchange server when using > the Cisco client. I think there were also problems connecting to SQL > databases. IOutlook and SQL connectivity issues? Believe it or not, it sounds simply enought like a name resolution problem such as a WINS issue or lack of WINS, or split tunneling not configured. Do me a favor, when the Cisco Client is connected, post an ipconfig /all of the client. Ace |