Weird DNS resolution issue?


good afternoon,

i upgraded backup dc server 2008 2012 r2. located on secondary campus hour away , has direct time warner link primary dc (aka runs straight off main campus feed). working great on secondary dc except can no longer rdp or access file shares on backup dc remote computers on main campus. however, can access backup dc main server, terminal server, , our exchange server located on main campus computers located on secondary campus.

this led me believe maybe firewall issue, disabled firewalls temporarily no luck. checked of dns forward , reverse zones , seem fine. cleared arp cache no luck , re-added server manually no luck.

the problem works in both directions. cannot access of main campus pcs/laptops secondary campus server either.

if ping server hostname computer on main campus resolve ip address of secondary server gives destination host unreachable message.

is there maybe simple overlooking?


was in-place upgrade or did install scratch (the preferred way upgrade dc)?  if new system, plugged same port on router old system?  use vlans?  if so, router trunked?

. : | : . : | : . tim



Windows Server  >  Windows Server 2012 General



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS