> All machines on the remote LAN can talk to each other and to the
> NT server. The NT server can talk to all machines on the local LAN
> and access the internet via the router (gateway: .1 of the CLASS C)
Huh? The machines on the remote LAN can talk to the .1 router?
>
> The card on the local side of the NT is xxx.xxx.xxx.70 and is part
> of the local CLASS C. The card on the remote side of the NT is
> yyy.yyy.yyy.17 and is part of a subnet of a _different_ CLASS C.
> However, I want users of the machines on the remote LAN to be able
> to access the Internet across the ADSL link and subsequently out
> the router at .1
Didn't you say above that the remote LAN can access the .1 router?
>
> I have the remote card in the NT set up with gateway =
> yyy.yyy.yyy.70 and I have IP forwarding turned on for both cards.
That's a good start.
>
> I have the local card in the NT set up with gateway = yyy.yyy.yyy.1
> and I have tried adding a second gateway of xxx.xxx.xxx.17 (the
> other card!) but there is no difference either way.
>
I think you need a static route put into the NT machine.
> Is it even possible to bridge/route across these two cards with NT
> 4.0 server or do I need some other software? Is there something I
> need to do in DNS tables? Any help would be appreciated.
>
NT 4 will route between 2 subnets, but I don't think it supports VLSM.
It may now, I haven't played with it for a few months. You may also need
a static route in the NT machine. Does your xxx.xxx.xxx.1 router see the
yyy.yyy.yyy.16 network in it's route table?
-- Kyle Platts Network Engineer !NTERPRISE Networking Services - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.