How to set routing and remot access?

[GoroSama]

I have 120 Days W2k Server version and I set it as AD Controller.
This server has DNS and DHCP enable as well as routing & remot access.
I have two more PCs all of them connected via lan to server (thru TCP/IP)
Server has internet access thru dial up networking.

Well, I want this server to be able to be a NAT so others PCs can access to
internet thru it. I was using Help to know how to set up and it states I
can't use "share dial up networking" because I've one of the following
services into my network: DNS, DHCP, AD PC,...
So, it shows another way to get same result as using sharing.
It's about setting Routing and NAT.

Followig help again I set server as router (using wizard and setting it as
internet router to share conecction) and enabled name resolution.

I set clients as help states (IP by DHCP, DNS=W2k server ip, GateWay=W2k
server ip)

Well, I connected server to Internet using routing interfaces. My clients
get ip automatically by DHCP and ....can't exit to Inet. Clients only can
access to internet using ip (instead of using url as usual).
If I check ip config by "ipconfig /all" I notice DNS server ip isn't set
(empty). So DHCP doesn't asign me my DNS ip. DHCP is managed by routing &
remot access.

I tried other ways as setting manually DNS ip in my clients and gateway, or
set DNS ip as my ISP DNS servers. Any of them works well.

Tired to try I downloaded wingate 3.0 and winproxy 3.0 to test them and use
instead of using W2k tools. I got suprised when I noticed they didn't work
either.

I decided to format server and install it again as independent server
instead of AD controller, .... works.

I need it to be AD controller to create domain, but with AD I can't use
"proxy" feature (not really proxy).

There is someone who knows how to get Internet shared connection using a W2k
server into a Active Directory (as primary controller)?

That's all

Thank to all of you.

From Spain
Goro Sama
gor...@hotmail.com

[Jerry and Tina Ray]

Instead of using routing and remote access as your internet gateway (which
requires you to have public ip addresses on the workstations, requires
static or RIP routes, and doesn't use NAT), install internet connection
sharing into windows 2000. This is a nat connection. You still will use
routing and remote access to handle the dial-up connection for the isp, just
not to handle the routing aspect to the other machines. The two programs
are going to work together.
--
Jerry P. Ray - Hard at Work
Computer Discount Center
Home of The Computer Doctors
email: je...@cdcaug.com -or- jr...@aug.com
Ph: (904) 823-9669 Fax: (904) 823-9677
GoroSama <gor...@hotmail.com> wrote in message
news:8fjjjl$bb...@news.airtel.net...