Server can't ping anything outside of LAN

[Andrew Brill]

Out of the blue our Win 2003 server has stopped being able to connect to the
internet. pings of domain names time out as do pings of known internet ip
addresses (although pings of local ip's are fine).

Event viewer reports: The dynamic registration of the dns record ... failed
on the following dns server ...

dcdiag reports:
host could not be resolved to an ip address... check dns, dhcp, server
name etc
although guid dns couldn't be resolved server name ... resolved to ip adress
.... and was pingable.
check that ip address is registered correctly with dns server



The strange thing is one of our workstations has its primary dns as the
servers ip address (no secondary dns) and this workstation accesses the
internet fine (except when the server was rebooting)

I've tried simply restarting without success - I don't really know what to
do beyond that!
I'm afraid the person that deals with the server and network setups is on
holiday and I'm not familiar with how to resolve such problems. Can anyone
help? Feel free to ask for more information as long as you tell me how I
can find out that information!

Thanks,
Andrew

 

[Andrew Brill]

Every few minutes it pops up a command prompt window titled svchost which
vanishes a few seconds later. The only services in msconfig are microsoft
ones.
Is it normal for it to do this?

 

[Andrew Brill]

netdiag says:

[warning] dns entries for this dc are not registered correctly on dns server
.... please wait 30 minutes for dns server replication
[fatal] no dns servers have the dns records for this dc registered

dns test: [warning] cannot find a primary authoratative dns server for name
.... [rcode refused]
name ... may not be registered in dns

query for dc dns entry ... on dns server ... failed
dns error code: dns_error_rcode_refused

 

[Kevin D. Goodknecht]

In

Out of the blue our Win 2003 server has stopped being able to connect
to the internet. pings of domain names time out as do pings of known
internet ip addresses (although pings of local ip's are fine).

Event viewer reports: The dynamic registration of the dns record ...
failed on the following dns server ...

dcdiag reports:
host could not be resolved to an ip address... check dns, dhcp,
server name etc
although guid dns couldn't be resolved server name ... resolved to ip
adress ... and was pingable.
check that ip address is registered correctly with dns server



The strange thing is one of our workstations has its primary dns as
the servers ip address (no secondary dns) and this workstation
accesses the internet fine (except when the server was rebooting)

I've tried simply restarting without success - I don't really know
what to do beyond that!
I'm afraid the person that deals with the server and network setups
is on holiday and I'm not familiar with how to resolve such problems.
Can anyone help? Feel free to ask for more information as long as
you tell me how I can find out that information!

Thanks,
Andrew

All machines including the DC must use the IP of the DC for DNS, that is
required for AD to funtion properly.
AN ipconfig /all and the domain name from ADU&C will help diagnose this, as
it could be a disjointed name space.
You should also verify the Full computer name from the system control panel.

 

[Andrew Brill]

Thanks a lot. I set the dns to point to itself and internet now works on
it! Just gotta sort out exchange now which I'll take to the exchange groups
if i need to.

 

[Andrew Brill]

Net and dc diag run successfully too now