Re: Remotely Managing DNS

Tech-Archive recommends: Fix windows errors by optimizing your registry



In news:1189637603.445380.38340@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
MarineGeek <slrobb@xxxxxxxxx> typed:

Yes, I am running as my domain admin account. My workstation is
joined to our domain.

What DNS address is the workstation using? (Asked previously but didn't see
a reply) Please provide an ipconfig /all of the client and of one of your
DCs. This will greatly help us.

Are there any Event log errors on either the client or the DC(s)?

Ace



.



Relevant Pages

  • Re: Name resolution issues on W2K Pro
    ... Workstation 1 can not resolve any names on the internet. ... > able to ping the router and the ISP's 2 DNS servers. ... > the windows client fixed this. ... Which Windows client are you talking about here? ...
    (microsoft.public.win2000.dns)
  • Re: XP Client Connection Problem
    ... I'm not the most knowledgable about DNS but I ... > now consists of a single server and single workstation. ... > The server is Windows 2003 and is set up for DNS, ... This first client is also an XP ...
    (microsoft.public.windows.server.dns)
  • Re: Adding XP computer to Domain - access denied
    ... In your NIC configuration on the XP client make sure that the primary DNS ... client is looking to join it, then it must find the server that is hosting ... > The XP workstation and server 2003 computer can communicate, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Slow Desktop loading
    ... DC with one workstation? ... secondary dns on the TCP/IP settings. ... I can add a new host to one DNS server and it propagates to the ... as it measures ANY client, while Windows Netmon take into account itself ...
    (microsoft.public.windows.server.general)
  • Re: NT4 -> W2K3 client cant fallback...
    ... In the lab I duplicated DNS from the live DNS server, ... >> fine until I tried to test fallback for client workstations. ... >> new AD Domain,I can get a sample client workstation to ... >> moved it back to the unchanched live NT4 domain where it has it's original ...
    (microsoft.public.windows.server.setup)