Re: User Login Time on windows 2000 profesional on Domain

Okay,

Let's summarize what is going on here:

You had it such that the secondary DNS information was the IP Address of
your ISP's DNS Server. This was on both the Domain Controller and on all
client workstations. This information is set statically. You changed the
ISP information (is there another Domain Controller in your environment?).
Now, by changing it does that mean that you removed it or that you entered
in the IP Address of another DNS Server? The name in your forward lookup
zone matches exactly the name of your internal domain.

You have rebooted all of the systems. Another way would have been to do the
following at a command prompt on each system:

net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon

This has not resolved anything?

What happens if you use nslookup? What does that tell you?

Are you able to get to the Internet once you do finally connect?

Do you have all of the subfolders in the FLZ? Those would be _sites, _tcp,
_udp and _msdcs. And all of the records are there?
What happens if you install the Support Tools and use dcdaig /v and netdiag
/v? What is the output from each of those?

--
Cary W. Shultz
Roanoke, VA 24012

"Chetan" <chetan.kamra@xxxxxxxxx> wrote in message
news:1139573042.480745.241460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks
I done that too but it doesnt work



.

Relevant Pages

  • Re: User Login Time on windows 2000 profesional on Domain
    ... dual-homed situation (where the Domain Controller has two working network ... in the IP Address of another DNS Server? ... ipconfig /registerdns ... net start netlogon ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... that can replicate the directory partition over this ... either fixup the alpha site dns or point it to use the SBS dns server and allow replication to complete before pointing it back to using itself for DNS. ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Demoting a DC in W2003
    ... >> roles) and DC3 is a plain DC. ... >> was configured to use itself as it's primary DNS server, ... >> object from the following source domain controller. ... > DC3 due to replication problems that have been happening longer than 60 ...
    (microsoft.public.win2000.active_directory)
  • Re: DNS and main domain controller is not working
    ... Now you have to create a new forward lookup zone for your domain, make it primary AD integrated zone. ... Then you have to reconfigure all domain machines to use the new DNS server on the NIC, either with DHCP scope options or manual on any machine. ... alternatice dc at other brach. ... i had additonal domain controller in other brach city. ...
    (microsoft.public.windows.server.dns)
  • Re: Netdiag kerberos failure
    ... important for kerberos. ... keep in time synch with the domain controller that is the pdc fsmo which is the time ... Check the Event Viewer on the domain controller and run first netdiag on it and then ... assigned IP address as it's preferred dns server in tcp/ip properties and W2K/Xp Pro ...
    (microsoft.public.win2000.networking)