HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Active Directory Replication over Firewalls
Windows Server 2003
1833491
Members
2695
Online
110052
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2006 03:53 AM
08-17-2006 03:53 AM
Active Directory Replication over Firewalls
We're trying to enable Active Directory replication between 2 sites divided by 2 separate firewalls using NAT.
The Setup
Private: 192.168.255.#
Public: 62.49.#.#
Domain Controller (Windows 2003)
|
|
|
3Com OfficeConnect VPN firewall (3CR870-95)
1-to-1 NAT Enabled
|
|
[Internet]
|
|
Cisco PIX 515E
1-to-1 NAT Enabled
|
|
|
Private: 192.168.84.#
Public: 212.78.#.#
Domain Controller (Windows 2003)
The question
Can we utilise IPSec for Active Directory replication (using Kerberos for authentication). If yes, could someone point me in the direction of documentation that explains how to achieve this or provide some pointers. I've followed several Microsoft articles including the well written one by Steve Riley (Active Directory Replication over Firewalls) but so far I've been unable to get replication working. When doing a ping it continuously responds with "Negotiating IP security". When setting up the IPSec IP filter, do I specify the private IP address of the destination server or the public IP address?
The Setup
Private: 192.168.255.#
Public: 62.49.#.#
Domain Controller (Windows 2003)
|
|
|
3Com OfficeConnect VPN firewall (3CR870-95)
1-to-1 NAT Enabled
|
|
[Internet]
|
|
Cisco PIX 515E
1-to-1 NAT Enabled
|
|
|
Private: 192.168.84.#
Public: 212.78.#.#
Domain Controller (Windows 2003)
The question
Can we utilise IPSec for Active Directory replication (using Kerberos for authentication). If yes, could someone point me in the direction of documentation that explains how to achieve this or provide some pointers. I've followed several Microsoft articles including the well written one by Steve Riley (Active Directory Replication over Firewalls) but so far I've been unable to get replication working. When doing a ping it continuously responds with "Negotiating IP security". When setting up the IPSec IP filter, do I specify the private IP address of the destination server or the public IP address?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2006 07:00 AM
08-17-2006 07:00 AM
Re: Active Directory Replication over Firewalls
IPSec protected traffic will not work with Network Address Translation (NAT). NAT needs to modify packets in transit, but IPSec is designed to be tamper resistant, preventing packet modification. The IETF is currently working toward specifying a NAT and IPSec interoperability standard.
A new technology known as IPsec NAT Traversal (NAT-T) has been standardized by the IP Security Protocol Working Group of the Internet Engineering Task Force (IETF) and is defined in Requests for Comments (RFCs) 3947 and 3948. IPsec NAT-T defines both changes in the negotiation process and different methods of sending IPsec-protected data.
Information about NAT-T can be found here:
http://www.microsoft.com/technet/community/columns/cableguy/cg0802.mspx
Another good document for AD with IPSEC and protected networks:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c2ef3846-43f0-4caf-9767-a9166368434e&DisplayLang=en
A new technology known as IPsec NAT Traversal (NAT-T) has been standardized by the IP Security Protocol Working Group of the Internet Engineering Task Force (IETF) and is defined in Requests for Comments (RFCs) 3947 and 3948. IPsec NAT-T defines both changes in the negotiation process and different methods of sending IPsec-protected data.
Information about NAT-T can be found here:
http://www.microsoft.com/technet/community/columns/cableguy/cg0802.mspx
Another good document for AD with IPSEC and protected networks:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c2ef3846-43f0-4caf-9767-a9166368434e&DisplayLang=en
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP