Re: domain access across a gateway
- From: "Bill Grant" <not.available@online>
- Date: Tue, 15 Aug 2006 10:43:11 +1000
If you are running Active Directory you should not be using ICS. ICS is
a very limited application and is not compatible with AD and the way that
DNS works with AD.
If you want the "new" subnet to interact with the AD, forget about ICS.
Set the two subnets up to use normal IP routing. If possible, don't use the
server as a router (as this may interfere with browsing on the LAN). Set all
machines to use the DNS server for the domain (I assume that this is on the
W2k DC) and use the NAT router on the 172. subnet. With your current setup
you are doing NAT twice from the 192.168 subnet.
Mike Ryan wrote:
"Mike Ryan" wrote:
"Joshua Bolton" wrote:
Is routing thru the server working ie. can you ping from theyes they can
192.x.x.x to the 172.x.x.x network?
no static ip's
Do the 192.x.x.x workstations get their ip from the 2003 server?
Does your MS DNS contain host and ptr records for the 2003 server?
I do not know how do I check and add these? The 2003 server is a
member of the domain.
You may need to add the 192.x.x.x network to AD sites and services.How do I do that?
I did some more checking and found out that the windows 2003 server
shows up in the active directory on the windows 2000 server but not
in the network neighborhood of the windows 2000 server. The windows
2003 server also just shows the 192.168.0 network in its network
neighborhood none of the computers on the 172.18.40 network
.
- Prev by Date: Static gateway address changes without user input
- Next by Date: Re: NAT without DHCP? (w2k3)
- Previous by thread: Static gateway address changes without user input
- Next by thread: Permissions
- Index(es):
Relevant Pages
|
