Hi,
No there is only one NIC card on the machine. The windows 2003r2 box is running its own DNS, which all the clients are pointing to in their IP settings.
I have no idea where this external DNS IP address is coming from.
THanks
"Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message news:uWORy%(E-Mail Removed)...
Do you have two NICs on the server? It is better to use internal DNS instead of ISP DNS.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Aussie Rules" <(E-Mail Removed)> wrote in message news:OE1U%(E-Mail Removed)...
Hi,
I have a W2003r2 server, and a XP client.
Everything seems fine, can ping the FQDN etc from client to server, client
can login in etc, but can not browse network from the client(can on server).
I have stopped the browser on the XP client, to ensure there is only the one
master browser.
I do however get the folloing in my R2 servers system event log, when
starting the netlogon service.. The DNS server it is trying to update
(209.212.65.15) is no an IP addres of a machine in my network so I assume
for some reason its trying to update a remote DNS server some where.
Also when I run dcdiag I get a error on connectivity (the error is at the
bottom of this post...
Event log message
--------------------------------------
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 23/10/2006
Time: 11:37:47
User: N/A
Computer: SCOOBY
Description:
The dynamic registration of the DNS record '_ldap._tcp.haha.net. 600 IN SRV
0 100 389 scooby.haha.net.' failed on the following DNS server:
DNS server IP address: 209.212.65.15
Returned Response Code (RCODE): 5
Returned Status Code: 9017
For computers and users to locate this domain controller, this record must
be registered in DNS.
USER ACTION
Determine what might have caused this failure, resolve the problem, and
initiate registration of the DNS records by the domain controller. To
determine what might have caused this failure, run DCDiag.exe. You can find
this program on the Windows Server 2003 installation CD in
Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and
Support Center. To initiate registration of the DNS records by this domain
controller, run 'nltest.exe /dsregdns' from the command prompt on the domain
controller or restart Net Logon service. Nltest.exe is available in the
Microsoft Windows Server Resource Kit CD.
Or, you can manually add this record to DNS, but it is not recommended.
ADDITIONAL DATA
Error Value: DNS bad key.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00
DCDIAG Error
---------------------------------------
C:\Program Files\Support Tools>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SCOOBY
Starting test: Connectivity
The host 2d19db0d-6b5a-4453-93b5-29d205595a79._msdcs.haha.net could
not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(2d19db0d-6b5a-4453-93b5-29d205595a79._msdcs.haha.net) couldn't be
resolved, the server name (scooby.haha.net) resolved to the IP
address (192.168.1.50) and was pingable. Check that the IP address
is
registered correctly with the DNS server.
......................... SCOOBY failed test Connectivity
Doing primary tests
(the rest produces no error)
Similar Threads
Linear Mode
