Running RRAS and IIS on same 2008 server?

OK, I made a post about this back in january, but never did get it figured
out. Maybe I'll get some new info this time, or suggestions on who can
better help me here...

I have a server that, admittedly runs a lot of services, but I cant afford
more computers to do these tasks, and its more of a hobby server than
anything... Anyways, it's a windows 2008 server, configured as a domain
controller, dns server, dhcp server, rras server, and iis server. the
server has 2 NICs, one for the public IP interface, and one connected to my
private lan. RRAS is configured for NAT.

So here's the deal:
All the computers on my LAN can access the internet with to problem
whatsoever.
Computers on the internet can access my web server no problem.
Computers on my LAN cannot (to be explained in a minute) access my web
server by typing the domain name, or public IP address.
Computers on my LAN can connect to my web server by using the private IP of
the server.

I know everything used to work properly with the same setup when I used to
use 2003 server. I have set this server up twice, and have encountered the
same problem. When I try to type in http://www.myserver.com from my LAN, it
will load a very small page with no problem (if I make a test page with one
line of text). It wont load a larger page at all. Just seems to timeout.
If I have the default IIS welcome site enabled, IE will display the title of
the page, but not the IIS graphic. I am pulling my hair out here! Since
everything works fine if I use the private IP of the server, I have to
assume there is something RRAS is doing trying to connect the LAN side to
the WAN IP?

I tried to turn off compression in IIS, thinking since file size seems to
have something to do with the problem that it may be a compression issue,
but I still have the same problem.

I know I could setup separate DNS names to direct to the LAN ip, but that's
a bit of a pain, and I don't want to tell people they have to use a
different address when they are connected here vs. at home.

Any help, or possible ways I could somehow figure out where the error is
coming from would be great. I don't really know how to troubleshoot http
connections...

Thanks in advance!
Chris

"Christopher M. Casey" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OK, I made a post about this back in january, but never did get it figured
> out. Maybe I'll get some new info this time, or suggestions on who can
> better help me here...
>
> I have a server that, admittedly runs a lot of services, but I cant afford
> more computers to do these tasks, and its more of a hobby server than
> anything... Anyways, it's a windows 2008 server, configured as a domain
> controller, dns server, dhcp server, rras server, and iis server. the
> server has 2 NICs, one for the public IP interface, and one connected to
> my private lan. RRAS is configured for NAT.
>
> So here's the deal:
> All the computers on my LAN can access the internet with to problem
> whatsoever.
> Computers on the internet can access my web server no problem.
> Computers on my LAN cannot (to be explained in a minute) access my web
> server by typing the domain name, or public IP address.
> Computers on my LAN can connect to my web server by using the private IP
> of the server.
>
> I know everything used to work properly with the same setup when I used to
> use 2003 server. I have set this server up twice, and have encountered
> the same problem. When I try to type in http://www.myserver.com from my
> LAN, it will load a very small page with no problem (if I make a test page
> with one line of text). It wont load a larger page at all. Just seems to
> timeout. If I have the default IIS welcome site enabled, IE will display
> the title of the page, but not the IIS graphic. I am pulling my hair out
> here! Since everything works fine if I use the private IP of the server,
> I have to assume there is something RRAS is doing trying to connect the
> LAN side to the WAN IP?
>
> I tried to turn off compression in IIS, thinking since file size seems to
> have something to do with the problem that it may be a compression issue,
> but I still have the same problem.
>
> I know I could setup separate DNS names to direct to the LAN ip, but
> that's a bit of a pain, and I don't want to tell people they have to use a
> different address when they are connected here vs. at home.
>
> Any help, or possible ways I could somehow figure out where the error is
> coming from would be great. I don't really know how to troubleshoot http
> connections...
>
> Thanks in advance!
> Chris


Sounds like a DNS issue. Normally I would highly recommend to NOT multihome
a DC or install RRAS on it because of the complications that occur with AD,
but being under a budget, I can understand. However, Linksys does sell
routers that can handle NAT for internet access so it will relieve you and
the server from handling this task for a mere USD $50.

Read my following blog on multihoming a DC, why not to do it, what it does
to AD, and how to manipulate it to work. I haven't tested the reg entries
yet on 2008, but I assume they are similar.

================================================== ================
================================================== ================
Multihomed DCs, DNS, RRAS servers.
By Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA
First published: January, 2003, updated July, 2006
==============================================

Multihomed DCs WILL cause numerous issues. It's highly recommended to single
home all DCs and use a non-DC for the multihoming purposes. If it is the
internet gateway, it is recommended to purchase an inexpensive, or cable/DLS
router, or even better, a Cisco or similar firewall to perform the task,
which if it is compromised by an internet attacker remotely, can further
compromise the rest of the internal network.

Also if attempting to use ICS on a DC, this further complicates matters with
DC functionality, and cannot be fixed with the following steps outlined in
this article.

To explain why will require a little background on AD and DNS:

First, just to get this out of the way, if you have your ISP's DNS addresses
in your IP configuration (DCs and clients), they need to be REMOVED. If the
ISP's DNS is in there, this will cause additional problems. I usually see
errors (GPOs not working, can't find the domain, RPC issues, etc), when the
ISP's DNS servers are listed on a client, DCs and/or member servers, or with
multihomed DCs. If you have an ISP's (or some other outside DNS server or
even using your router as a DNS server) DNS addresses in your IP
configuration (all DCs, member servers and clients), they need to be REMOVED
and ONLY use the internal DNS server(s). This can be very problematic.

Basically, AD requires DNS. DNS stores AD's resource and service locations
in the form of SRV records, hence how everything that is part of the domain
will find resources in the domain. If the ISP's DNS is configured in the any
of the internal AD member machines' IP properties, (including all client
machines and DCs), the machines will be asking the ISP's DNS 'where is the
domain controller for my domain?", whenever it needs to perform a function,
(such as a logon request, replication request, querying and applying GPOs,
etc). Unfortunately, the ISP's DNS does not have that info and they reply
with an "I dunno know", and things just fail. Unfortunately, the ISP's (or
your router as a DNS server) DNS doesn't have information or records about
your internal private AD domain, and they shouldn't have that sort of
information.

Also, AD registers certain records in DNS in the form of SRV records that
signify AD's resource and service locations. When there are multiple NICs,
each NIC registers. IF a client, or another DC queries DNS for this DC, it
may get the wrong record. One factor controlling this is Round Robin. If a
DC or client on another subnet that the DC is not configured on queries for
it, Round Robin will kick in offering one or the other. If the wrong one
gets offered, it may not have a route to it. On the other hand, Subnetmask
Priortization will ensure a querying client will get an IP that corresponds
to the subnet it's on, which will work. To insure everything works, stick
with one NIC.

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and find
other services and resources such as the Global Catalog, file sharing and
the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
logged, authenticating to shares and printers, logging on takes forever,
among numerous other issues.

But if you like, there are some registry changes to eliminate the
registration of the external NIC or simply use the internal networking
routing to allow access. Here's the whole list of manual steps to follow.

Another problem is the DC now becomes part of two Sites. This is another
issue that can be problematic.

But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. If the both NICs are
internal, I would suggest to pick a subnet, team the NICs and allow your
internal routers handle the traffic between subnets - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP’s DNS servers’ IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC’s GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
“WINS” tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the “Browser service”, provides the
list of machines, workgroup and domain names that you see in “My Network
Places” (or the legacy term “Network Neighborhood”). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It’s sort of a
fingerprint. You can’t have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the “File and Print Service” and disable the “MS Client Service”
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck “Register this connection” under IP properties, Advanced
settings, “DNS” tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC’s IP references for the “LdapIpAddress”. If this is a GC, you will need
to delete the GC IP record as well (the “GcIpAddress”). To do that, in the
DNS console, under the zone name, you will see the _msdcs folder.

Under that, you will see the _gc folder. To the right, you will see the IP
address referencing the GC address. That is called the GcIpAddress. Delete
the IP addresses referencing the outer NIC.
i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in DNS
http://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is
done with this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/tre...o_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with
the IP addresses that you need for the DC. To create the LdapIpAddress,
create a new host under the domain, but leave the “hostname” field blank,
and provide the internal IP of the DC, which results in a record that looks
like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if
this is a GC. That would be under the _msdcs._gc SRV record under the zone.
It is created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the “Interfaces” tab, force it only to listen to the internal NIC’s IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP.
How to set a forwarder? Good question. Depending on your operating
system,choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294


<==*** Some additional reading ***==>
More links to read up and understand what is going on:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg
sameasparent private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's Site [Includes info LdapIpAddress and GcIpAddress information and
the SRV mnemonic values]:
http://support.microsoft.com/kb/306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/kb/825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/?id=291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Rid Pool Errors and other multihomed DC errors, and how to configure a
multihomed DC, Ace Fekay, 24 Feb 2006
http://www.ureader.com/message/3244572.aspx

257623 257623 Domain Controller's Domain Name System Suffix Does Not Match
Domain Name
http://support.microsoft.com/?id=257623
================================================== ================

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

I do know about the issues with DNS and the AD, and I have already taken
care of all that. The problem I'm having seems to be something wrong with
either IIS or RRAS. DNS works perfectly, and I don’t have any problems with
AD that I know of. The public IP isn't listed in my active directory dns at
all.

The issue I have is just trying to access my own website from my lan. Like
I said, some pages will load (if they are very small), and some like the IIS
start page will load the title, but not the .png image. If there was a DNS
issue, nothing would work at all, as far as I know.

I guess I need to see if I can find a contact for the rras team or iis team
at microsoft..

-Chris

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Christopher M. Casey" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> OK, I made a post about this back in january, but never did get it
>> figured out. Maybe I'll get some new info this time, or suggestions on
>> who can better help me here...
>>
>> I have a server that, admittedly runs a lot of services, but I cant
>> afford more computers to do these tasks, and its more of a hobby server
>> than anything... Anyways, it's a windows 2008 server, configured as a
>> domain controller, dns server, dhcp server, rras server, and iis server.
>> the server has 2 NICs, one for the public IP interface, and one connected
>> to my private lan. RRAS is configured for NAT.
>>
>> So here's the deal:
>> All the computers on my LAN can access the internet with to problem
>> whatsoever.
>> Computers on the internet can access my web server no problem.
>> Computers on my LAN cannot (to be explained in a minute) access my web
>> server by typing the domain name, or public IP address.
>> Computers on my LAN can connect to my web server by using the private IP
>> of the server.
>>
>> I know everything used to work properly with the same setup when I used
>> to use 2003 server. I have set this server up twice, and have
>> encountered the same problem. When I try to type in
>> http://www.myserver.com from my LAN, it will load a very small page with
>> no problem (if I make a test page with one line of text). It wont load a
>> larger page at all. Just seems to timeout. If I have the default IIS
>> welcome site enabled, IE will display the title of the page, but not the
>> IIS graphic. I am pulling my hair out here! Since everything works fine
>> if I use the private IP of the server, I have to assume there is
>> something RRAS is doing trying to connect the LAN side to the WAN IP?
>>
>> I tried to turn off compression in IIS, thinking since file size seems to
>> have something to do with the problem that it may be a compression issue,
>> but I still have the same problem.
>>
>> I know I could setup separate DNS names to direct to the LAN ip, but
>> that's a bit of a pain, and I don't want to tell people they have to use
>> a different address when they are connected here vs. at home.
>>
>> Any help, or possible ways I could somehow figure out where the error is
>> coming from would be great. I don't really know how to troubleshoot http
>> connections...
>>
>> Thanks in advance!
>> Chris
>
>
> Sounds like a DNS issue. Normally I would highly recommend to NOT
> multihome a DC or install RRAS on it because of the complications that
> occur with AD, but being under a budget, I can understand. However,
> Linksys does sell routers that can handle NAT for internet access so it
> will relieve you and the server from handling this task for a mere USD
> $50.
>
> Read my following blog on multihoming a DC, why not to do it, what it does
> to AD, and how to manipulate it to work. I haven't tested the reg entries
> yet on 2008, but I assume they are similar.
>
> ================================================== ================
> ================================================== ================
> Multihomed DCs, DNS, RRAS servers.
> By Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA
> First published: January, 2003, updated July, 2006
> ==============================================
>
> Multihomed DCs WILL cause numerous issues. It's highly recommended to
> single home all DCs and use a non-DC for the multihoming purposes. If it
> is the internet gateway, it is recommended to purchase an inexpensive, or
> cable/DLS router, or even better, a Cisco or similar firewall to perform
> the task, which if it is compromised by an internet attacker remotely, can
> further compromise the rest of the internal network.
>
> Also if attempting to use ICS on a DC, this further complicates matters
> with DC functionality, and cannot be fixed with the following steps
> outlined in this article.
>
> To explain why will require a little background on AD and DNS:
>
> First, just to get this out of the way, if you have your ISP's DNS
> addresses in your IP configuration (DCs and clients), they need to be
> REMOVED. If the ISP's DNS is in there, this will cause additional
> problems. I usually see errors (GPOs not working, can't find the domain,
> RPC issues, etc), when the ISP's DNS servers are listed on a client, DCs
> and/or member servers, or with multihomed DCs. If you have an ISP's (or
> some other outside DNS server or even using your router as a DNS server)
> DNS addresses in your IP configuration (all DCs, member servers and
> clients), they need to be REMOVED and ONLY use the internal DNS server(s).
> This can be very problematic.
>
> Basically, AD requires DNS. DNS stores AD's resource and service locations
> in the form of SRV records, hence how everything that is part of the
> domain will find resources in the domain. If the ISP's DNS is configured
> in the any of the internal AD member machines' IP properties, (including
> all client machines and DCs), the machines will be asking the ISP's DNS
> 'where is the domain controller for my domain?", whenever it needs to
> perform a function, (such as a logon request, replication request,
> querying and applying GPOs, etc). Unfortunately, the ISP's DNS does not
> have that info and they reply with an "I dunno know", and things just
> fail. Unfortunately, the ISP's (or your router as a DNS server) DNS
> doesn't have information or records about your internal private AD domain,
> and they shouldn't have that sort of information.
>
> Also, AD registers certain records in DNS in the form of SRV records that
> signify AD's resource and service locations. When there are multiple NICs,
> each NIC registers. IF a client, or another DC queries DNS for this DC, it
> may get the wrong record. One factor controlling this is Round Robin. If a
> DC or client on another subnet that the DC is not configured on queries
> for it, Round Robin will kick in offering one or the other. If the wrong
> one gets offered, it may not have a route to it. On the other hand,
> Subnetmask Priortization will ensure a querying client will get an IP that
> corresponds to the subnet it's on, which will work. To insure everything
> works, stick with one NIC.
>
> Since this DC is multi-homed, it requires additional configuration to
> prevent the public interface addresses from being registered in DNS. This
> creates a problem for internal clients locating AD to authenticate and
> find other services and resources such as the Global Catalog, file sharing
> and the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events
> to be logged, authenticating to shares and printers, logging on takes
> forever, among numerous other issues.
>
> But if you like, there are some registry changes to eliminate the
> registration of the external NIC or simply use the internal networking
> routing to allow access. Here's the whole list of manual steps to follow.
>
> Another problem is the DC now becomes part of two Sites. This is another
> issue that can be problematic.
>
> But believe me, it's much easier to just get a separate NAT device or
> multihome a non-DC then having to alter the DC. If the both NICs are
> internal, I would suggest to pick a subnet, team the NICs and allow your
> internal routers handle the traffic between subnets - Good luck!
>
> 1. Insure that all the NICS only point to your internal DNS server(s) only
> and none others, such as your ISP’s DNS servers’ IP addresses.
>
> 2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
> move the internal NIC (the network that AD is on) to the top of the
> binding order (top of the list).
>
> 3. Disable the ability for the outer NIC to register. The procedure, as
> mentioned, involves identifying the outer NIC’s GUID number. This link
> will show you how:
> 246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
> NIC too):
> http://support.microsoft.com/?id=246804
>
> 4. Disable NetBIOS on the outside NIC. That is performed by choosing to
> disable NetBIOS in IP Properties, Advanced, and you will find that under
> the “WINS” tab. You may want to look at step #3 in the article to show you
> how to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> Note: A standard Windows service, called the “Browser service”, provides
> the list of machines, workgroup and domain names that you see in “My
> Network Places” (or the legacy term “Network Neighborhood”). The Browser
> service relies on the NetBIOS service. One major requirement of NetBIOS
> service is a machine can only have one name to one IP address. It’s sort
> of a fingerprint. You can’t have two brothers named Darrell. A multihomed
> machine will cause duplicate name errors on itself because Windows sees
> itself with the same name in the Browse List (My Network Places), but with
> different IPs. You can only have one, hence the error generated.
>
> 5. Disable the “File and Print Service” and disable the “MS Client
> Service” on the outer NIC. That is done in NIC properties by unchecking
> the respective service under the general properties page. If you need
> these services on the outside NIC (which is unlikely), which allow other
> machines to connect to your machine for accessing resource on your machine
> (shared folders, printers, etc.), then you will probably need to keep them
> enabled.
>
> 6. Uncheck “Register this connection” under IP properties, Advanced
> settings, “DNS” tab.
>
> 7. Delete the outer NIC IP address, disable Netlogon registration, and
> manually create the required records
>
> a. In DNS under the zone name, (your DNS domain name), delete the
> outer NIC’s IP references for the “LdapIpAddress”. If this is a GC, you
> will need to delete the GC IP record as well (the “GcIpAddress”). To do
> that, in the DNS console, under the zone name, you will see the _msdcs
> folder.
>
> Under that, you will see the _gc folder. To the right, you will see the IP
> address referencing the GC address. That is called the GcIpAddress. Delete
> the IP addresses referencing the outer NIC.
> i. To stop these two records from registering that information,
> use the steps provided in the links below:
> Private Network Interfaces on a Domain Controller Are Registered in DNS
> http://support.microsoft.com/?id=295328
>
> ii. The one section of the article that disables these records is
> done with this registry entry:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
> (Create this Multi-String Value under it):
> Registry value: DnsAvoidRegisterRecords
> Data type: REG_MULTI_SZ
> Values: LdapIpAddress
> GcIpAddress
>
> iii. Here is more information on these and other Netlogon Service records:
> Restrict the DNS SRV resource records updated by the Netlogon service
> [including GC]:
> http://www.microsoft.com/technet/tre...o_rr_in_ad.asp
>
> b. Then you will need to manually create these two records in DNS with
> the IP addresses that you need for the DC. To create the LdapIpAddress,
> create a new host under the domain, but leave the “hostname” field blank,
> and provide the internal IP of the DC, which results in a record that
> looks like:
> (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
> purposes)
>
> i. You need to also manually create the GcIpAddress as well, if
> this is a GC. That would be under the _msdcs._gc SRV record under the
> zone. It is created in the same fashion as the LdapIpAddress mentioned
> above.
>
> 8. In the DNS console, right click the server name, choose properties,
> then under the “Interfaces” tab, force it only to listen to the internal
> NIC’s IP address, and not the IP address of the outer NIC.
>
> 9. Since this is also a DNS server, the IPs from all NICs will register,
> even if you tell it not to in the NIC properties. See this to show you how
> to stop that behavior (this procedure is for Windows 2000, but will also
> work for Windows 2003):
> 275554 - The Host's A Record Is Registered in DNS After You Choose Not to
> Register the Connection's Address:
> http://support.microsoft.com/?id=275554
>
> 10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
> not sure which DNS to forward to until you've got the DNS address of your
> ISP.
> How to set a forwarder? Good question. Depending on your operating
> system,choose one of the following articles:
>
> 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
> http://support.microsoft.com/?id=300202
>
> 323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
> (How to configure a forwarder):
> http://support.microsoft.com/d/id?=323380
>
> Active Directory communication fails on multihomed domain controllers
> http://support.microsoft.com/kb/272294
>
>
> <==*** Some additional reading ***==>
> More links to read up and understand what is going on:
>
> 292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
> Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
> unwanted IPs registering]:
> http://support.microsoft.com/?id=292822
>
> Active Directory communication fails on multihomed domain controllers
> http://support.microsoft.com/kb/272294
>
> 246804 - How to enable or disable DNS updates in Windows 2000 and in
> Windows Server 2003
> http://support.microsoft.com/?id=246804
>
> 295328 - Private Network Interfaces on a Domain Controller Are Registered
> in DNS [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg
> sameasparent private IP]:
> http://support.microsoft.com/?id=295328
>
> 306602 - How to Optimize the Location of a DC or GC That Resides Outside
> of a Client's Site [Includes info LdapIpAddress and GcIpAddress
> information and the SRV mnemonic values]:
> http://support.microsoft.com/kb/306602
>
> 825036 - Best practices for DNS client settings in Windows 2000 Server and
> in Windows Server 2003 (including how-to configure a forwarder):
> http://support.microsoft.com/kb/825036
>
> 291382 - Frequently asked questions about Windows 2000 DNS and Windows
> Server 2003 DNS
> http://support.microsoft.com/?id=291382
>
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> Rid Pool Errors and other multihomed DC errors, and how to configure a
> multihomed DC, Ace Fekay, 24 Feb 2006
> http://www.ureader.com/message/3244572.aspx
>
> 257623 257623 Domain Controller's Domain Name System Suffix Does Not Match
> Domain Name
> http://support.microsoft.com/?id=257623
> ================================================== ================
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum to benefit from collaboration
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>

"Christopher M. Casey" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I do know about the issues with DNS and the AD, and I have already taken
>care of all that. The problem I'm having seems to be something wrong with
>either IIS or RRAS. DNS works perfectly, and I don’t have any problems
>with AD that I know of. The public IP isn't listed in my active directory
>dns at all.
>
> The issue I have is just trying to access my own website from my lan.
> Like I said, some pages will load (if they are very small), and some like
> the IIS start page will load the title, but not the .png image. If there
> was a DNS issue, nothing would work at all, as far as I know.
>
> I guess I need to see if I can find a contact for the rras team or iis
> team at microsoft..
>


Chris,

I apologize, I misunderstood the problem. So if you are able to resolve and
connect, then it definitely not a DNS issue. I think it comes down to either
IIS on Windows 2008 (which is very different than 2003), or IE (v 8?), and
is where I would look at. Not sure which version of IE, but have you tried
it from different IE versions. If so, does the same thing occurs? If it
does, then it sounds like an IIS issue.

Is the local firewall on the 2008 and the client you're testing from,
running? Is there a 3rd party AV, security app, or firewall on the clients
you're testing it from?

I would suggest to post this to the IIS group. I've cross-posted it for your
convenience to the following group. Just check back here for responses.

x-posted to microsoft.public.inetserver.iis
F/ups set to both microsoft.public.inetserver.iis and
microsoft.public.windows.server.networking.

Ace

"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Christopher M. Casey" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I do know about the issues with DNS and the AD, and I have already taken
>>care of all that. The problem I'm having seems to be something wrong with
>>either IIS or RRAS. DNS works perfectly, and I don’t have any problems
>>with AD that I know of. The public IP isn't listed in my active directory
>>dns at all.
>>
>> The issue I have is just trying to access my own website from my lan.
>> Like I said, some pages will load (if they are very small), and some like
>> the IIS start page will load the title, but not the .png image. If there
>> was a DNS issue, nothing would work at all, as far as I know.
>>
>> I guess I need to see if I can find a contact for the rras team or iis
>> team at microsoft..
>>
>
>
> Chris,
>
> I apologize, I misunderstood the problem. So if you are able to resolve
> and connect, then it definitely not a DNS issue. I think it comes down to
> either IIS on Windows 2008 (which is very different than 2003), or IE (v
> 8?), and is where I would look at. Not sure which version of IE, but have
> you tried it from different IE versions. If so, does the same thing
> occurs? If it does, then it sounds like an IIS issue.
>
> Is the local firewall on the 2008 and the client you're testing from,
> running? Is there a 3rd party AV, security app, or firewall on the clients
> you're testing it from?
>
> I would suggest to post this to the IIS group. I've cross-posted it for
> your convenience to the following group. Just check back here for
> responses.
>
> x-posted to microsoft.public.inetserver.iis
> F/ups set to both microsoft.public.inetserver.iis and
> microsoft.public.windows.server.networking.
>
> Ace

On the 2008 server, I have the firewall disabled. Right now, I don’t have
any security software installed (just to rule out the possibility that
symantec was causing the issue). The issue happens regardless of which
browser I use (tried in IE and firefox). I installed an HTTP browser diag
tool I found through google, and it just seems to say the LAN compurers
never get a reply back from the server for things that don’t load, the
connections just timeout.. I'm still thinking its RRAS not re-routing the
packets back to the local network, but it could also be something to do with
IIS.

Thanks for posting it in the IIS group too, maybe someone there will have
some ideas for me to try as well.

-Chris

"Christopher M. Casey" <(E-Mail Removed)> wrote in message
news:OjetJ%(E-Mail Removed)...
>
>
> On the 2008 server, I have the firewall disabled. Right now, I don’t have
> any security software installed (just to rule out the possibility that
> symantec was causing the issue). The issue happens regardless of which
> browser I use (tried in IE and firefox). I installed an HTTP browser diag
> tool I found through google, and it just seems to say the LAN compurers
> never get a reply back from the server for things that don’t load, the
> connections just timeout.. I'm still thinking its RRAS not re-routing the
> packets back to the local network, but it could also be something to do
> with IIS.
>
> Thanks for posting it in the IIS group too, maybe someone there will have
> some ideas for me to try as well.
>
> Chris

One way to determing if IIS is truly not responding is to sniff the traffic
on both interfaces on the 2008 server. The diag tool is just listenting to
what the cient is receiving.

Also, if you believe it's RRAS, check the interface binding order in Network
and Saring center, Manage Network Connections, Advanced Menu, Advanced
Settings. Make sure that the internal LAN interface is at the top of the
binding order. This makes it the default interface.

And no problem for cross-posting it. :-)

Ace

I run RRAS and IIS on the same machine for years (both w2k3 and w2k8) with
no problems, and it's a DC. Look in IIS and see what bindings are
displayed. If it's all unassigned. then it's not an IIS issue.

Go to the command prompt and see if port 80 is listening. netstat -an

0.0.0.0:80

I looked on my server and here are the settings.

Under the NAT location
I have the External interface

Nothing under IGMP

Under the DHCP interface
I have the Internal interface

Nothing under Static Routes

Under General tabl
Right click properties
General Tab, Inbound and Outbound filters (any / any) and Drop all
packets except (any / any) both interfaces.

Hope this helps.

Windows firewall is enabled on the external interface, disabled on the
internal interface.

Steve Schofield
Microsoft MVP - IIS



"Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Christopher M. Casey" <(E-Mail Removed)> wrote in message
> news:OjetJ%(E-Mail Removed)...
>>
>>
>> On the 2008 server, I have the firewall disabled. Right now, I don’t
>> have any security software installed (just to rule out the possibility
>> that symantec was causing the issue). The issue happens regardless of
>> which browser I use (tried in IE and firefox). I installed an HTTP
>> browser diag tool I found through google, and it just seems to say the
>> LAN compurers never get a reply back from the server for things that don’t
>> load, the connections just timeout.. I'm still thinking its RRAS not
>> re-routing the packets back to the local network, but it could also be
>> something to do with IIS.
>>
>> Thanks for posting it in the IIS group too, maybe someone there will have
>> some ideas for me to try as well.
>>
>> Chris
>
> One way to determing if IIS is truly not responding is to sniff the
> traffic on both interfaces on the 2008 server. The diag tool is just
> listenting to what the cient is receiving.
>
> Also, if you believe it's RRAS, check the interface binding order in
> Network and Saring center, Manage Network Connections, Advanced Menu,
> Advanced Settings. Make sure that the internal LAN interface is at the top
> of the binding order. This makes it the default interface.
>
> And no problem for cross-posting it. :-)
>
> Ace

OK, I checked my config again, made rras exactly like yours (except for the
dhcp part, since I have the actual dhcp server installed too). I have the
same problem as ive been having still... I'm pulling my hair out over here
trying to figure out what I'm doing wrong.

I did notice, in IIS, when I go to the bindings, I can select all (as I have
it now), or my local IP address. my public IP address isn't listed there
for some reason. But people on the internet can still get to my site just
fine with the public ip address as long as I leave it to all unassigned.

I personally don't think its an IIS bug, but rather something with RRAS,
since small pages seem to work fine, but anything more than a couple
kilobytes seems to be where things start failing.

Can someone recommend some kind of packet sniffer or tracer or something
that I could use to try and figure this out and perhaps contact someone from
Microsoft?

Oh, and steve, one question for you... Since this seems to be all working
for you and everything, can you tell em what order you install things when
you setup your server? When I installed this, I did Active
Directory/Domains, which setup dns server for me, then did dhcp, and
authorized in in AD, then did RRAS, then did IIS. perhaps the order they
are installed matters (even though it shouldn't really I don't think)

Thanks again for trying to help!
-Chris


"Steve Schofield" <(E-Mail Removed)> wrote in message
news:uFq$(E-Mail Removed)...
> I run RRAS and IIS on the same machine for years (both w2k3 and w2k8) with
> no problems, and it's a DC. Look in IIS and see what bindings are
> displayed. If it's all unassigned. then it's not an IIS issue.
>
> Go to the command prompt and see if port 80 is listening. netstat -an
>
> 0.0.0.0:80
>
> I looked on my server and here are the settings.
>
> Under the NAT location
> I have the External interface
>
> Nothing under IGMP
>
> Under the DHCP interface
> I have the Internal interface
>
> Nothing under Static Routes
>
> Under General tabl
> Right click properties
> General Tab, Inbound and Outbound filters (any / any) and Drop all
> packets except (any / any) both interfaces.
>
> Hope this helps.
>
> Windows firewall is enabled on the external interface, disabled on the
> internal interface.
>
> Steve Schofield
> Microsoft MVP - IIS
>
>
>
> "Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> "Christopher M. Casey" <(E-Mail Removed)> wrote in message
>> news:OjetJ%(E-Mail Removed)...
>>>
>>>
>>> On the 2008 server, I have the firewall disabled. Right now, I don't
>>> have any security software installed (just to rule out the possibility
>>> that symantec was causing the issue). The issue happens regardless of
>>> which browser I use (tried in IE and firefox). I installed an HTTP
>>> browser diag tool I found through google, and it just seems to say the
>>> LAN compurers never get a reply back from the server for things that don't
>>> load, the connections just timeout.. I'm still thinking its RRAS not
>>> re-routing the packets back to the local network, but it could also be
>>> something to do with IIS.
>>>
>>> Thanks for posting it in the IIS group too, maybe someone there will
>>> have some ideas for me to try as well.
>>>
>>> Chris
>>
>> One way to determing if IIS is truly not responding is to sniff the
>> traffic on both interfaces on the 2008 server. The diag tool is just
>> listenting to what the cient is receiving.
>>
>> Also, if you believe it's RRAS, check the interface binding order in
>> Network and Saring center, Manage Network Connections, Advanced Menu,
>> Advanced Settings. Make sure that the internal LAN interface is at the
>> top of the binding order. This makes it the default interface.
>>
>> And no problem for cross-posting it. :-)
>>
>> Ace
>
>

It's been a while since I did the install, but I had IIS installed first if
I recall (Since I'm an IIS MVP), then made a DC, then RRAS and DHCP. I
found a few other things, here are the settings. HTH

Right click on the machine name, properties.
General
LAN and demand dialing
IP v4 remote access server checked
Security
Windows Authentication
Windows Accounting
IPv4
Enabled IPv4 forwarding Checked
DHCP radio checked

Under the IPv4 section (has public address)
NAT
Public Address connected to internet
Enable NAT on this interface
Service and Ports
I have port 80, 443 and others.

Steve Schofield
(E-Mail Removed)

Microsoft MVP - IIS

"Christopher M. Casey" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OK, I checked my config again, made rras exactly like yours (except for
> the dhcp part, since I have the actual dhcp server installed too). I have
> the same problem as ive been having still... I'm pulling my hair out over
> here trying to figure out what I'm doing wrong.
>
> I did notice, in IIS, when I go to the bindings, I can select all (as I
> have it now), or my local IP address. my public IP address isn't listed
> there for some reason. But people on the internet can still get to my
> site just fine with the public ip address as long as I leave it to all
> unassigned.
>
> I personally don't think its an IIS bug, but rather something with RRAS,
> since small pages seem to work fine, but anything more than a couple
> kilobytes seems to be where things start failing.
>
> Can someone recommend some kind of packet sniffer or tracer or something
> that I could use to try and figure this out and perhaps contact someone
> from Microsoft?
>
> Oh, and steve, one question for you... Since this seems to be all working
> for you and everything, can you tell em what order you install things when
> you setup your server? When I installed this, I did Active
> Directory/Domains, which setup dns server for me, then did dhcp, and
> authorized in in AD, then did RRAS, then did IIS. perhaps the order they
> are installed matters (even though it shouldn't really I don't think)
>
> Thanks again for trying to help!
> -Chris
>
>
> "Steve Schofield" <(E-Mail Removed)> wrote in message
> news:uFq$(E-Mail Removed)...
>> I run RRAS and IIS on the same machine for years (both w2k3 and w2k8)
>> with no problems, and it's a DC. Look in IIS and see what bindings are
>> displayed. If it's all unassigned. then it's not an IIS issue.
>>
>> Go to the command prompt and see if port 80 is listening. netstat -an
>>
>> 0.0.0.0:80
>>
>> I looked on my server and here are the settings.
>>
>> Under the NAT location
>> I have the External interface
>>
>> Nothing under IGMP
>>
>> Under the DHCP interface
>> I have the Internal interface
>>
>> Nothing under Static Routes
>>
>> Under General tabl
>> Right click properties
>> General Tab, Inbound and Outbound filters (any / any) and Drop all
>> packets except (any / any) both interfaces.
>>
>> Hope this helps.
>>
>> Windows firewall is enabled on the external interface, disabled on the
>> internal interface.
>>
>> Steve Schofield
>> Microsoft MVP - IIS
>>
>>
>>
>> "Ace Fekay [MCT]" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> "Christopher M. Casey" <(E-Mail Removed)> wrote in message
>>> news:OjetJ%(E-Mail Removed)...
>>>>
>>>>
>>>> On the 2008 server, I have the firewall disabled. Right now, I don't
>>>> have any security software installed (just to rule out the possibility
>>>> that symantec was causing the issue). The issue happens regardless of
>>>> which browser I use (tried in IE and firefox). I installed an HTTP
>>>> browser diag tool I found through google, and it just seems to say the
>>>> LAN compurers never get a reply back from the server for things that
>>>> don't load, the connections just timeout.. I'm still thinking its RRAS
>>>> not re-routing the packets back to the local network, but it could also
>>>> be something to do with IIS.
>>>>
>>>> Thanks for posting it in the IIS group too, maybe someone there will
>>>> have some ideas for me to try as well.
>>>>
>>>> Chris
>>>
>>> One way to determing if IIS is truly not responding is to sniff the
>>> traffic on both interfaces on the 2008 server. The diag tool is just
>>> listenting to what the cient is receiving.
>>>
>>> Also, if you believe it's RRAS, check the interface binding order in
>>> Network and Saring center, Manage Network Connections, Advanced Menu,
>>> Advanced Settings. Make sure that the internal LAN interface is at the
>>> top of the binding order. This makes it the default interface.
>>>
>>> And no problem for cross-posting it. :-)
>>>
>>> Ace
>>
>>