Remote Office connection

fellow technet’ers – know how sometimes, it’s simple things need can things give brain fade.

i’ve taken on role smallish company – fair, have decent bits of kit , have right ideas etc.  however, have inherited bit of mine field need clear , take them forward. 

one of mines need clear brain fade comes in.  we have main office, 2008 domain.  all there.  we have remote office, connected via vpn link.  each end software fire wall, seems running fine.  at remote office, there several workstations used connect tsg main office.  again, seems well.

going forward – need extend domain include dc @ remote office, along hyper-v box.  just test water, have tried joining machine domain remote office (after network in place) – no luck (domain not found).  from same machine, can connect servers need remote desktop etc.  i’ve configured subnets , sites in sites , services, brain fade has struck me down. 

any ideas?

 

hello

all suggestions received valid suggestions, , of course basic requirements site site link work - if i’m honest - knew beforehand.

what couldn’t work out, why things not working when correct settings applied – brain fade crept in.  so, on weekend, managed book time business take link down, , troubleshoot.

as i’d briefly tried in pass, corrected dns details – things stopped working. now, having time on site – able dig deeper , found route of problem - poor documentation predecessor.

basically, found rule in firewall blocking traffic.  with correct ip addresses in place – , rule removed, sprang life.

however - can work out there reason this, wasn’t documented.  the link isn’t fastest, when attempted authenticate via link, took age login, can assume why traffic blocked , terminal services used.

at least now, can formulate plan going forward

thanks input.

 

Windows Server  >  Directory Services