asked on

Cannot Join Domain from remote office? - The Network path was not found

OK, raising the white flag here! :)
We recently opened a new office and we have a brand new Windows 2008 R2 Server setup there for which I have remote access (RDP). There is a site to site VPN between that office and our HQ. I have setup DNS to point to our HQ DC/DNS servers. I can ping the DC/DNS servers and the FQDN by name from this new remote server, i.e. ping mydomain.rootdomain.com. However, when I attempt to join the domain, I am initially prompted as normal for username/pass of authorized user, but after a minute it times out with the following error. "The following error occurred attempting to join the domain "mydomain.rootdomain.com": The network path was not found.

I've tried everything... any ideas?

ASKER CERTIFIED SOLUTION

thiagotietze

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Darius Ghassem

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Adam Brown

In order to join remotely, you have to have a lot of ports open. RDP and ICMP are not among those ports :D
This site has a list of the ports you'll need to make sure are getting through the VPN: http://www.howtonetworking.com/casestudy/dcfirewallissue.htm

dkraut

ASKER

I should add that the network team confirmed that the connection between HQ and this office is wide open, no firewall. OS Firewall is also turned off. The netstat showed activity from the server to the DC via ports 445 and 139, but oddly the source IP flapping/changing. This server has dual NIC's. I've asked the local tech to pull the cable from "Local Area Connection 2" and disable it in the OS. I'll try again after that... Will let you know what happens.

Adam Brown

You may also want to make sure the IP scheme at the remote site doesn't overlap with the one on the corporate LAN. That can cause a ton of problems.

SOLUTION

Adam Brown

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

thiagotietze

You said that:
"The netstat showed activity from the server to the DC via ports 445 and 139"

So, if you've wrote the command as I mentioned in my post, you for sure have Firewall problems and need to open those ports between the networks.

Since you open it, you'll be able to proceed with the join domain.

Verify too if you have some personal firewall (even Windows Firewall) enabled on you machine, ou some antivirus with Threat response (Mcafee, Symantec...) These can be blocking "Site-External" connections

dkraut

ASKER

You guys were right, after determining that I could not telnet to the DC's via port 445 and 139 from this remote server, but could from my desktop, I called the network guys on this one and they suddenly lost their amnesia and remembered that did indeed have some ports blocked. :|
Once they removed the block, all was well. Wow, what a waste of time and effort, but I appreciate the assistance!!