domain access across a gateway

I hope I can make this clear as to what we are doing if not ask me questions

I have a network with a windows 2000 server as the domain controller. the
ipaddress for this controller is 172.18.40.21

On the network I have a windows 2003 std. server with a ipaddress on this
network of 172.18.40.182. I also have internet connection sharing on the
computer and a ip network address of 192.168.0.1

On the 192.168.0 network I have about 20 computers that are accessing
primarily the windows 2003 std server and software. However, I need to try
and map a drive on the windows 2000 server but am not able to find the server
or the drive.

Is there a way that you can think of to map and find the shared devices on
the 172.18.40 network from the 192.168.0 network??? Can I also get logged
into the domain from the 192.168.0.network??


The windows 2000 server only has one network card I could add one if it
would help.

Is routing thru the server working ie. can you ping from the 192.x.x.x to
the 172.x.x.x network?

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?
You may need to add the 192.x.x.x network to AD sites and services.

"Joshua Bolton" wrote:

> Is routing thru the server working ie. can you ping from the 192.x.x.x to
> the 172.x.x.x network?
yes they can
>
> Do the 192.x.x.x workstations get their ip from the 2003 server?
>
no static ip's

> 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?

"Mike Ryan" wrote:

>
>
> "Joshua Bolton" wrote:
>
> > Is routing thru the server working ie. can you ping from the 192.x.x.x to
> > the 172.x.x.x network?
> yes they can
> >
> > Do the 192.x.x.x workstations get their ip from the 2003 server?
> >
> no static ip's
>
> > 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

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 the
>>> 192.x.x.x to the 172.x.x.x network?
>> yes they can
>>>
>>> Do the 192.x.x.x workstations get their ip from the 2003 server?
>>>
>> no static ip's
>>
>>> 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