• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 478
  • Last Modified:

new domain controller seems to not be resolving properly in DNS Windows 2008r2

We have a Windows 2008r2 environment with several offices joined together via MPLS. We recentlly moved the office and in the process added an extra Domain Controller and several new users to the location. I have had some complaints that an otherwise normally functioning printer is printing very slow. In trouble shooting, I realized that the new print server is also the new DC that we added. I work in a different location but I tried to RDP to the DC/Print server from our locaiton and it would not connect. I tried to PING the FQDN and got a response "PING REQUEST COULD NOT FIND HOST". If I do a PING -a 192.168.5.x, I get a normal reply with the proper FQDN. Some name resolution is happening, but not a direct PING of the FQDN. If I RDP to the other DC in that office, on the same subnet, I can PING and connect to the new DC/Print server fine. I know that is probably related to DNS. Any advice on trouble shooting is welcome
0
Thor2923
Asked:
Thor2923
1 Solution
 
CincyItSolutionsCommented:
Have you gone in and created the reverse lookup in DNS?

In the network adapter properties of your LAN connection do you have the loop back address listed as the primary DNS server? If so try changing it to the IP address of the server.

In the DNS zone, did you add your ISP DNS server in the list of forwards? If not try that.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now