a domain controller for domain could not be contacted

[xtops]

plz help i have windows 2003 server with active directory and domain name is tsc.tops.co and ip add is 10.100.0.198 sub mask 255.255.240. gway 192.168.2.1 dns 10.100.0.198 then i have a workstation xp pro the ip is 192.168.2.9 submask 255.255.255.0 gway 192.168.2.1 dns 10.100.0.198

when i ping 10.100.0.198 from 192.168.2.9 its ok replay
when i ping 192.168.2.9 from 10.100.0.198 its ok replay
when i want to member the workstation which is the xp pro with ip 192.168.2.9 to domain with ip 10.100.0.198 ive got the error a domain controller could not be found..


firewall is already off


tnx

[dkumar]

Make sure the DNS settings pointing to correct DNS server.

Plz post IPconfig /all result

[Meinolf Weber [MVP-DS]]

Hello xtops,

Please post an unedited ipconfig /all from the DC and the problem client.
Sounds like the DC is multihomed, what is a not good solution, DC's should
be only using one subnet on one NIC. It results in conflicts you have now.

Please describe more detailed the setup of your network, router, switch etc.
and why the DC has 2 ip's.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> plz help i have windows 2003 server with active directory and
> domain name is tsc.tops.co and ip add is 10.100.0.198 sub mask
> 255.255.240. gway 192.168.2.1 dns 10.100.0.198 then i have a
> workstation xp pro the ip is 192.168.2.9 submask 255.255.255.0 gway
> 192.168.2.1 dns 10.100.0.198
>
> when i ping 10.100.0.198 from 192.168.2.9 its ok replay
> when i ping 192.168.2.9 from 10.100.0.198 its ok replay
> when i want to member the workstation which is the xp pro with ip
> 192.168.2.9 to domain with ip 10.100.0.198 ive got the error a domain
> controller could not be found..
> firewall is already off
>
> tnx
>
> http://forums.techarena.in
>

[Paul Bergson [MVP-DS]]

Post ipconfig /all from dns server, dc and client

Also do the following:
Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take into
account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045



--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"xtops" <xtops.3ovk7d@DoNotSpam.com> wrote in message
news:xtops.3ovk7d@DoNotSpam.com...
>
> plz help i have windows 2003 server with active directory and domain
> name is tsc.tops.co and ip add is 10.100.0.198 sub mask 255.255.240.
> gway 192.168.2.1 dns 10.100.0.198 then i have a workstation xp pro the
> ip is 192.168.2.9 submask 255.255.255.0 gway 192.168.2.1 dns
> 10.100.0.198
>
> when i ping 10.100.0.198 from 192.168.2.9 its ok replay
> when i ping 192.168.2.9 from 10.100.0.198 its ok replay
> when i want to member the workstation which is the xp pro with ip
> 192.168.2.9 to domain with ip 10.100.0.198 ive got the error a domain
> controller could not be found..
>
>
> firewall is already off
>
>
> tnx
>
>
> --
> xtops
> ------------------------------------------------------------------------
> xtops's Profile: http://forums.techarena.in/members/xtops.htm
> View this thread: a domain controller for domain could not be contacted
>
> http://forums.techarena.in
>

[oz Casey Dedeal]

Run netdiag /Fix on the domain controller and try to see if this will remedy
the current problem.

--
oz Casey Dedeal
MVP (Exchange)
MCITP (EMA), MCITP (EA),
MCITP (SA),
Security+, Project +, Server +

oz@SMTp25.org
http://smtp25.blogspot.com
http://telnet25.wordpress.com


"Paul Bergson [MVP-DS]" wrote:

> Post ipconfig /all from dns server, dc and client
>
> Also do the following:
> Run diagnostics against your Active Directory domain.
>
> If you don't have the support tools installed, install them from your server
> install disk.
> d:\support\tools\setup.exe
>
> Run dcdiag, netdiag and repadmin in verbose mode.
> -> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
> -> netdiag.exe /v > c:\netdiag.log (On each dc)
> -> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
> -> dnslint /ad /s "ip address of your dc"
>
> **Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
> in the forest. If you have significant numbers of DC's this test could
> generate significant detail and take a long time. You also want to take into
> account slow links to dc's will also add to the testing time.
>
> If you download a gui script I wrote it should be simple to set and run
> (DCDiag and NetDiag). It also has the option to run individual tests without
> having to learn all the switch options. The details will be output in
> notepad text files that pop up automagically.
>
> The script is located on my website at
> http://www.pbbergs.com/windows/downloads.htm
>
> Just select both dcdiag and netdiag make sure verbose is set. (Leave the
> default settings for dcdiag as set when selected)
>
> When complete search for fail, error and warning messages.
>
> Description and download for dnslint
> http://support.microsoft.com/kb/321045
>
>
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "xtops" <xtops.3ovk7d@DoNotSpam.com> wrote in message
> news:xtops.3ovk7d@DoNotSpam.com...
> >
> > plz help i have windows 2003 server with active directory and domain
> > name is tsc.tops.co and ip add is 10.100.0.198 sub mask 255.255.240.
> > gway 192.168.2.1 dns 10.100.0.198 then i have a workstation xp pro the
> > ip is 192.168.2.9 submask 255.255.255.0 gway 192.168.2.1 dns
> > 10.100.0.198
> >
> > when i ping 10.100.0.198 from 192.168.2.9 its ok replay
> > when i ping 192.168.2.9 from 10.100.0.198 its ok replay
> > when i want to member the workstation which is the xp pro with ip
> > 192.168.2.9 to domain with ip 10.100.0.198 ive got the error a domain
> > controller could not be found..
> >
> >
> > firewall is already off
> >
> >
> > tnx
> >
> >
> > --
> > xtops
> > ------------------------------------------------------------------------
> > xtops's Profile: http://forums.techarena.in/members/xtops.htm
> > View this thread: a domain controller for domain could not be contacted
> >
> > http://forums.techarena.in
> >
>