We've got a lan to lan tunnel up and running. We have IP connectivity, remote control software runs between sites, NSLookups, and NBstat are fine. When we try to add a local PC to a remote NT (2000) domain, we time out. Is there a tech doc out there for this, or has someone run into this? Thanks
We are not running WINS locally. The machines in question are in site 1. The WINS, DNS, and DC's are in Site 2. I am routing all requests for site 2 through our VPN concentrator. The L2L tunnel is up and NSLookups and NBstats are working, we can map network drives, and we can ping. However, when we try to add these to the domain in site 2, we get the domain controller cannot be found. The article from the reply above looks like it's for a PC using the VPN client, but it mentions mapping a drive to get the network prompt. I guess this is our next test.
Get a local WINS server is your best bet. A quick hack to get machines on the domain is to give them a lmhosts file, which includes the domain controller's name and ip. look in \winnt\system32\drivers\etc for an example. Edit it, save as lmhosts, do a nbtstat -R from the cmd prompt, and you should be able to add the machine to the domain. Basically, without WINS, pcs in site 1 likely cannot find the domain controller.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...