I am setting up a Site-to-Site VPN between two SonicWall appliances and have hit a minor road block. The main SonicWall is an NSA 2400 and is located at our corporate office with a Static Public IP. The remote SonicWall is a TZ 100 and is located in a branch office with a Dynamic Public IP. Both devices have been configured in Aggressive Mode.
Here is a summary of the configurations:
Corporate Office NSA 2400
Public IP: 220.127.116.11
Lan IP: 10.10.1.1/24
Our Exchange Server is 10.10.1.2
Branch Office TZ 100
Public IP: Dynamic
Lan IP: 10.10.3.1/24
I have configured the Corporate SonicWall with an Address Object for the Branch Office and vice versa for the Branch SonicWall. I have also made sure the VPN Policies have the correct Device ID's.
The VPN Tunnel shows that it is established on both SonicWall's and I am able to ping any of the corporate computers from the Branch Office using the IP Addresses. However, I am unable to ping any of the Corporate computers from the Branch Office using the computer names and I cannot ping any of the computers in the Branch Office from the Corporate Office. So basically I have one-way connectivity. I think this is the reason why I am unable to connect to Exchange from the Branch Office.
Any clues as to why I cannot ping from the Corporate Office or connect to Exchange?
Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.
In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication. By default, if the time difference between systems is off by more …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …