can't see Domain Controller - need help ASAP!

[Marie (Zionkowski) Gozikowski]

I am ready to kick this server.....

Last night I upgraded AVG to newest version --- went home, all looked fine.
This morning no one can access TAM or internet

Reboot workstations - nothing
Reboot server a few times - nothing

Stop AVG firewall & reboot again - nothing

Our tech set us up with DHCP on the server.... so no server, no
internet.  So to get people running, activated DHCP on router and
removed from server.... now the have internet but still can't access
server.

Computers all have event ID 15:  Automatic Certificate enrollment for
Iddings\Marie (or whomever's computer it is...) failed to contact to Active directory (0X80070546) - The specified domain either does not exist or couldn't be contacted

Also all have:   Event ID 1054:   Windows cannot obtain the domain controller  name for your computer network (The specified domain name either does not exist or couldn't be contacted) Group policy processing aborted.

I totally uninstalled AVG --- nada
I even changed my computer settings from Domain to Workgroup, and
then tried adding back to domain.... now I can't even boot into the
network... error says:  A domain controller for the domain iddings.local could not be conntaced.  Ensure that the domain name is typed in correctly (it is)

I have checked on the server.... the domain iddings.local is listed as active

I also checked the router.... the router can see the server as a connected
device with an assigned IP address, so I don't think it is the network card....

Help!

Thanks!

[Bloody Jack Kidd]

can you ping the domain controller?  either by hostname or ip?

check cabling / switches for starters.

on the domain controller
Start -> Run -> cmd

Code Select Expand

c:\>dcdiag

see if the tests are good.


also find an old computer and setup a 2nd DC... and split your DHCP scope across the two.

[admin]

@Marie:  FYI - moved the topic from helpline to here and removed the duplicate.

[Marie (Zionkowski) Gozikowski]

dcdiag does not work on either a workstation or on the server where the domain controller is located - says it is not recognized as a command?

the rest.... sorry, you lost me.    
I know next to nothing about domain controllers

This is a windows SBS 2003 server, BTW

[Bloody Jack Kidd]

OK - on the DC

START -> RUN -> cmd

Code Select Expand

c:\>ping www.yahoo.com

you could also try to ping the ip address of your router.

[Marie (Zionkowski) Gozikowski]

yahoo it could not find (odd because internet works for all others on internet, but not on the server...) but the router it found just fine...

[Bloody Jack Kidd]

try

Code Select Expand

c:\>net stop dns
c:\>net start dns

and then

Code Select Expand

c:\>nslookup www.yahoo.com

[Marie (Zionkowski) Gozikowski]

started and stopped fine

>nslookup www.yahoo.com    came back with:

Server:  appsrv02.iddings.local
Address:  192.168.1.104
DNS request timed out - timeout was 2 seconds
*** request to appsrv02.iddings.local timed out

[Jeff Zylstra]

I'm not as smart as Rick is, but I'll throw out some random thoughts here.

Have you checked the network settings on the server and workstations?  The server should have a static IP address, and each workstation must point to that static IP address as the domain name server.  Nothing internet related can happen if the DNS settings aren't correct.  

Right click on "my computer" or "computer" on the server and choose properties.  It should tell you the computer name, full computer name, and the domain name.  If it doesn't, that's a problem.

Any other entries in the event viewer - system area on the server?  This should tell you when something started to go wrong, and hopefully what went wrong.

[Bloody Jack Kidd]

did you run nslookup on the DC itself?

is it safe to assume both the hostname and ip address are correct?

[Bloody Jack Kidd]

I'm not as smart as Rick is

you may be surprised...

[Jeff Zylstra]

I'll take luck over skill any day.   I just wish I'd find some. 

[Che Guevara]

Not a techie but some of the virus software will highjack the ip address so the software scans throughput  before it releases to the machine IP itself. This creates a little internal loop that I am sure would not be good on a Domain controller.

Perhaps this is happening - can't remember now which software did that and on a workstation represents no problem but when I installed it on my Mdaemon server it created this loop and email was interupted

Also is the software you loaded specifically designed for a server ?

Rick
perhaps the virus software interuppted or change the internal routing tables of the server ?


 

[Marie (Zionkowski) Gozikowski]

both are correct...  

looking at event view on server gives me Event ID 17:
Sourse W32Time --- Timeprovider ntpclient - an error occured during DNS lookup of the manually configured peer "time.windows.com 0x1"  ntpclient will try again in 30 min

also have a bunch of Event ID 5774 & Event ID 5775 errors --- looking them up now

[Bloody Jack Kidd]

There's definitely a DNS issue. 

do you think you could do the following from the command line on the DC and paste the results in here:

Code Select Expand

c:\>ipconfig /all