Why is our Domain Controller attempting to communicate with this IP address?
It appears that 198.6.1.3 is a nameserver belonging to UUNet.
We use Verizon (UUNET --> MCI --> Verizon) so I understand that Verizon may have simply not renamed every nameserver. But in that case, should our system be failing communication with it? I'm not sure why DCOM is attempting this in the first place.
We use Verizon (UUNET --> MCI --> Verizon) so I understand that Verizon may have simply not renamed every nameserver. But in that case, should our system be failing communication with it? I'm not sure why DCOM is attempting this in the first place.
DCOM was unable to communicate with the computer 198.6.1.3 using any of the configured protocols.
DCOM was unable to communicate with the computer 198.6.1.2 using any of the configured protocols.
DCOM was unable to communicate with the computer 198.6.1.1 using any of the configured protocols.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The problem went away, but this wasn't the solution. Thanks for your help.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER