In
the server that i am referring to only has one nic int
it....but does have a firewall on the net that it resides
on using NAT......
I'm sorry, I don't understand the second part of your post.
Does this say you have an entry point firewall or you have a NAT or you have
a NAT device that has a built in firewall?
If you only have one NIC on the server with mulitple IPs, then they should
both be registering, needless to say may cause problems with the mutliple
addresses. But what is confusing, is that with the one NIC with two totally
separate IP's of different subnets assigned to it, that can cause confusion
with accessing this server when a client queries DNS for an AD service and
it;s subsequent location. This is a KNOWN issue with DC communication and
not recommended to have more than one NIC on a DC.
Things that will keep it from registering:
1. Not pointing to the internal DNS only.
2. File and Print Services disabled
3. Primary DNS Suffix is missing or incorrect and does not match the zone
name.
4. Dynamic updates not enabled
5. IP properties, DNS tab, "register this connection...." is unchecked.
6. As Kevin said, a reg entry disabling registration.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory