Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2008 Enterprise DNS question

Status
Not open for further replies.

1Drisnil

MIS
Mar 29, 2003
131
US
Xocoatl (MIS) 27 Aug 08 20:46
I have 2 windows 2008 servers, one enterprise which is an AD DC, and the other is a Web server with Share point 2007 server. The webserver is a member of the domain, which we we call room301.local .

The IPv4 address schema used for the 2008 servers is 192.168.60.x . The servers have two nics each. The AD is .7 & .8 and the web is only using .3 as I have not enable the 2nd nic.

These two servers are behind a WRT300N wireless gateway which has the wireless feature turned off, the NAT feature turned on, as well as the following ports allowed to pass-thru the firewall listed as both TCP & UDP:

21,25,53,80,110,123,135,137,138,139,161,162,389,443,445,464,636,1433,3389.

The WRT300N device has the WAN IP address as 10.4.185.19 as the building this small LAN sits in uses the 10.x.x.x IP Schema. It has 2 DNS servers defined as well as a gateway.

The 1st NIC on the AD server whose IP address is 192.168.60.7 is directed connect to the 10.x.x.x network, whereas the 2nd NIC is connected thru a small 16 port switch and then connected to the 10.x.x.x network.

The DNS is set up to forward to the same DNS servers as defined in the WRT300N.

The problem I am having is I can reach the webserver by name or IP from any PC sitting on the 10.x.x.x network, but I can't connect to the AD server. If I switch the PC to a static IP address in the 192.168.60.x network, I still see the webserver, but can't access the Internet, nor the AD server.

I can offer a symptom, I get some DNA errors from the zone _msdcs.x.x.x stating something about not be able to load this zone.

Any suggestions, ideas, or thoughts as to why this might be occurring?

[sadeyes]
 
as well as the following ports allowed to pass-thru the firewall listed as both TCP & UDP:

21,25,53,80,110,123,135,137,138,139,161,162,389,443,445,464,636,1433,3389."
Letting all these port open to the public realm is begging to be hacked, why have a firewall if this many ports are open, of these 2-3 likely need to be open. If the website is accessible from the public side, the webserver should be in a DMZ

Your server is multi-homed, this is asking for AD problems, search google for "domain controller multi-homed"

Suggest you look into Mark Minasi's Master Windows Server series of book, by Sybex



........................................
Chernobyl disaster..a must see pictorial
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top