After a normal reboot, suddenly we cannot remote desktop into our static IP Exchange 2003 Win2K3 server. No configuration changes were ever made to this server. We also cannot connect our Outlook clients anymore to this server. The event viewer logged the below message.
After trying 'ipconfig /flushdns', 'ipconfig /registerdns', 'net stop netlogon', and 'net start netlogon' this still did not resolve the issue.
What's odd is that we can still access each mailbox via the browser at domain.com/exchange. Thoughts?
**************************
The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:
Adapter Name : {20EB1636-5CFC-41FB-AAF4-5823E533A7AB}
Host Name : exchange
Adapter-specific Domain Suffix : circulent.com
DNS server list :
192.168.1.44
Sent update to server : 192.175.48.1
IP Address : 192.168.1.50
The reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.
You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
After trying 'ipconfig /flushdns', 'ipconfig /registerdns', 'net stop netlogon', and 'net start netlogon' this still did not resolve the issue.
What's odd is that we can still access each mailbox via the browser at domain.com/exchange. Thoughts?
**************************
The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:
Adapter Name : {20EB1636-5CFC-41FB-AAF4-5823E533A7AB}
Host Name : exchange
Adapter-specific Domain Suffix : circulent.com
DNS server list :
192.168.1.44
Sent update to server : 192.175.48.1
IP Address : 192.168.1.50
The reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.
You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.