Goal: to have Windows 2003 AD configured for the internal network AND to host a websites accessible from the internet over the DMZ.
Topology ( you can look at the network diagram) Windows 2003 has to interfaces, the internal IP is 172.31.0.35 and the other interface is connected to the DMZ port on the firewall with IP 192.168.10.35.
I have a block of public IPs and the public domain is registered to one of the public IP addresses.
DNS is running on the domain controller
I created NAT rules according the fw instructions to allow site to be hosted over the DMZ
The internal domain name is the same as the external domain name
1. It worked before introducing the fw. I used a regular home router with port forwarding.
2. I am able to ping the dmz interface of the server from a pc in the other network.
3. I am able to get to the site (internally) when typing the internal ip of the server -172.16.31.35
4. I am not able to get to the site from a computer in the internal network (172.31.16.0) when typing the DMZ ip of the server.- 192.168.10.35
For 3 and 4 I went to the site properties and changed the IP bound to it.
5. When I do nslookup the domain name resolves to the internal interface 172.31.16.35
Right now I don’t know where the problem is, IIS, DNS, FW?
”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
-Mike Kapnisakis, Warner Bros
With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. You'll also be able to connect with highly specified Experts to get personalized solutions to your troubleshooting & research questions. It’s like crowd-sourced consulting.
We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need.
Our certified Experts are CTOs, CISOs, and Technical Architects who answer questions, write articles, and produce videos on Experts Exchange. 99% of them have full time tech jobs - they volunteer their time to help other people in the technology industry learn and succeed.
We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.