Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  • Users: McEve
  • Order by date
  1. McEve

    svchost hogs CPU

    Ok, I thought I'd let you know what caused the problem. It was a policy. Auditing Directory service Access was enabled, and XP didn't like that one bit. This was a hard one to find.... :)
  2. McEve

    svchost hogs CPU

    Hi Pete, Yes there is a regular time between occurances - 12 seconds, around the clock. You might be right that it is a browsing issue - reinstalling the NIC drivers on the client makes it quiet for about 20 sec, then it starts all over again. But if I try browsing the network before the 20...
  3. McEve

    svchost hogs CPU

    Hi, We have a mixed AD domain with about 200 computers, Win2000, win98 and WinXP. We are now excperiencing a great deal of trouble with the WinXP computers. Ever 12 seconds the CPU reaches 100% utilization - (svchost is hogging the CPU). The eventlog is full of Log Off events, category 3...
  4. McEve

    nslookup defaults to 127.0.0.1

    I'm not so sure that was the case here. We installed SP3 immediately when it was released, and the server has worked perfectly since. We did have one server where we had to uninstall SP3, this server had SQL server installed, and SQL didn't like SP3 one bit.... Part from that, we have...
  5. McEve

    nslookup defaults to 127.0.0.1

    ok - did a repair install and back in business. Still like to know what happened though.. Terminal services are unhappy, and we have a mix of IE5 and IE6 - but that's no big fuzz compared to what we had... Thanks for taking the time to help out on this one!
  6. McEve

    nslookup defaults to 127.0.0.1

    The drivers for the NIC is updated (didn't think about that one :P) but no change. We moved the NIC to a different slot to force a new connection, but no change. There's only one NIC on the server, and yes, the domain suffux was a typo, it says qdomain in ipconfig. Onlu Tcp/Ip is installed and...
  7. McEve

    nslookup defaults to 127.0.0.1

    hmmm... here's a ipconfig /all from a healthy computer: Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : <hostname> Primary DNS Suffix . . . . . . . : qdomain.questus.no Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . ...
  8. McEve

    nslookup defaults to 127.0.0.1

    Forgot to mention. I have Event ID 5782 Source Netlogon in the event log: Dynamic registration or deregistration of one or more DNS records failed with the following error: No DNS servers configured for local system.
  9. McEve

    nslookup defaults to 127.0.0.1

    one weird problem for sure :) 1: Servicepack3. The problem started after a reboot. (Forgot about last good known config :P) no programs installed 2: dcdiag DC Diagnosis Performing initial setup: Done gathering initial info. Doing initial non skippeable tests Testing server...
  10. McEve

    nslookup defaults to 127.0.0.1

    I should have included this info as well, I'm sorry. Here it is: ipconfig /all Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : <hostname> Primary DNS Suffix . . . . . . . : domain.questus.no Node Type . . . . . . . . . . . . : Broadcast IP...
  11. McEve

    nslookup defaults to 127.0.0.1

    I have a win2000 server, one of 2 DC's. The KBarticle Q172060 describes my problem, but we do have a DNS server configured for the computer.... ping localhost returns 127.0.0.1 - fine.. ping <hostname> returns 127.0.0.1 - not so fine nslookup: *** Default servers are not available Default...

Part and Inventory Search

Back
Top