Windows SBS 2003 Problem Ping any domain names

  Open up a command prompt and type nslookup. The response should be itself. Are you using forwarders on the DNS on the server?

Thanks for the reply.
Please read my post. there is no problem with nslookup queries and the forwarders are correctly set.

  I read your post. I am not sure we are talking the same thing. You post said "if I query the server's DNS it replies properly". I am essentially making sure the server's DNS is pointing to itself. A nslookup with no parameters at the command prompt on the server would reflect that.  I agree it is some kind of name resolution issue.

yes, it's the server itself and it resolves names with the nslookup queries.

Hello justinxie,

can you give an ipconfig /all of the server + one client please?
did you set the forwarders with the CEICW?

Regards,

suppsaws

hi suppasaws,
i have spent more than two days trying to work out what the problem is. on the client pc, everything works fine. all the client pc's dns point to the sbs server and the server's ip configured only one dns address which is its own ip address. when i run netdiag and dcdiag, both indicate dns failed, but i have checked the dns looks has all the records required. there are a lot of netlogon errors id 5774 and dcom errors id 10009 which complains unable to communicate with the forwarder's ip address.
hope the information is enough.

so then I guess you've already read:
http://eventid.net/display.asp?eventid=5774&eventno=353&source=NETLOGON&phase=1
So can you ping your ISP dns servers (the forwarders)?
and have you reran the CEICW, doesn't it give you an error?

i have no problem pinging any ip addresses and have run ceicw twice with no error.

i have checked all my other sbs 2003 servers using secure updates and there is no problem at all. anyway, i have tried change from secure only to nonsecure and secure, but still no luck.

So I guess you've already tried resetting the IE on the server?
even tried with firefox?
because, when you can resolve the domainnames you should be able to surf on the server.
also sure this isn't a firewall/antivirus issue?

no, i didn't say it can resolve the domain names. i can only ping by ip address, not the domain names.

the strange thing is the server's dns resolves domain names for the workstations, but not for itself.

here is the dns diagnostic result:
DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.company.local.'. [WSAENOPROTOOPT             ]
            The name 'server.company.local.' may not be registered in DNS
.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.company.local.'. [ERROR_TIMEOUT]
            The name 'server.company.local.' may not be registered in DNS
.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.company.local.'. [WSAENOPROTOOPT             ]
            The name 'server.company.local.' may not be registered in DNS
.
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.company.local.'. [ERROR_TIMEOUT]
            The name 'server.company.local.' may not be registered in DNS
.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '0.0.0.0'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.
The command completed successfully

Can you verify that the proper SRV Resource Records are in your zone?

http://support.microsoft.com/Default.aspx?kbid=241515

If they are there - check the values for anything that looks out of place/incorrect. Then restart the DNS server service.

-Eric

Maybe this can sound not too bright, but...

Have you tried to change the primary DNS entry on IP settings of the server to an external DNS? If your browser doesn't display pages after that, you could exclude your local DNS as the source of the problems...

Hi acroment,
i have checked the dns manager and all the srv resource records are there. but if i query _ldap._tcp.dc._msdcs.domainname from nslookup, i got error message. it's certainly dns problem.

i have tried external dns server  and it wouldn't resolve name either.