Re: "Routing and Remote Access" in Windows Server 2003

From: aaron (aaron_at_fake.net)
Date: 01/07/05 

Date: Fri, 7 Jan 2005 09:40:50 -0600

Set the default gateway of NIC B to NIC A. 

-- 
aaron
A+,NET+,MCSE 2K/2K3,CNA,CCNA
"Jaime Stuardo" <JaimeStuardo@discussions.microsoft.com> wrote in message 
news:1AEE987E-31F6-46A5-A814-21046EC72C19@microsoft.com...
> Hi Robert,
>
> Can you please give me a more specific answer? is it clear that is a
> configuration problem and that I have to enable IP routing or whatever. 
> You
> say that I have to make sure no filtering blocks internet address, but.. 
> how
> can I make sure of that? I have found several dialog boxes where I can
> configure Inbound and Outbound filters (all different among themselves)
>
> You also say that I have to check NAT settings if I configure it, but, 
> there
> are a lot of settings, so, what specific setting do I have to check?
>
> Additionally I tell you that I have read a lot of documents on Internet,
> specially technical white papers in Microsoft Web Site. I have done all 
> the
> documents say, I have followed all step-by-step instructions but I could
> never make my LAN clients to connect to Internet through the Windows 2003
> Server computer. That's why, as a last resource, I posted the question 
> here.
>
> I have told that I have 2 NIC's in the server, I assigned to the one that
> connects to the DSL modem the static IP 10.0.0.1 and to the one that 
> connects
> to the LAN the IP 192.168.1.1. Is that correct? I can think that I have 2
> different networks so the only problem I think I have to resolve is how to
> make the LAN NIC to send the packets it receives from the LAN to the DSL 
> NIC
> so that it can send them to the DSL modem.
>
> In "Routing and Remote Access" I have added both NICS. How can I configure
> filters (or routing) in this case? Do I need to have a Routing Policy? the
> wizard has added one by default (I used VPN and NAT option when the wizard
> asked me), is this suficient?
>
> One of the document I have read says that when I have configured a VPN
> network, LAN clients computers can connect to other computers in the LAN 
> or
> to the Internet, but not to both. Is that true? When I run the wizard, the
> VPN and NAT option label says that it is for connecting LAN client 
> computers
> to Internet, but after the wizard finished, the LAN work perfectly, but it
> cannot connect to Internet.
>
> Any further help will be greatly appreciated
>
> Thanks
> Jaime
>
> "Robert L [MS-MVP]" wrote:
>
>> make sure no filtering block the internet access. also check the NAT
>> settings if you enable it.
>>
>> -- 
>> For more and other information, go to  http://www.ChicagoTech.net
>>
>> Don't send e-mail or reply to me except you need consulting services.
>> Posting on MS newsgroup will benefit all readers and you may get more 
>> help.
>>
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
>> http://www.ChicagoTech.net
>> Networking Solutions, http://www.chicagotech.net/networksolutions.htm
>> VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
>> VPN Process and Error Analysis, 
>> http://www.chicagotech.net/VPN%20process.htm
>> VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
>> This posting is provided "AS IS" with no warranties.
>> "Jaime Stuardo" <JaimeStuardo@discussions.microsoft.com> wrote in message
>> news:D413375F-29FF-41C5-8018-18960BEBC895@microsoft.com...
>> > Hi all....
>> >
>> > I configured a Windows 2003 Server machine with "Routing and Remote
>> > Access"
>> > but client computers cannot connect to Internet.
>> >
>> > Ths is a simplified scenario:
>> > .- Windows Server 2003 configured as Domain Controller, DNS, Active
>> > Directory and DHCP Server. This server has 2 NIC's. One connects to a 
>> > DSL
>> > modem (let's say NIC A from now on) and the other to a hub (let's say 
>> > NIC
>> > B
>> > from now on).
>> > .- One client computer with Windows 2000 Professional with 1 NIC 
>> > connected
>> > to the hub.
>> >
>> > The configuration I set for each PC is as follows:
>> >
>> > 1) Server
>> >
>> > - Name: WEBSERVER
>> > - Windows 2003 Server, Standard Edition acting as DC, DNS, DHCP Server 
>> > and
>> > Active Directory
>> > - Software Installed: Exchange server
>> > - NIC A (that connects to the DSL modem) is assigned static IP 
>> > 10.0.0.1,
>> > automatic DNS and no gateway
>> > - NIC B (that connects to the hub) is assigned static IP 192.168.1.1,
>> > automatic DNS and no gateway.
>> > - Internet connection correctly established. That network connection is
>> > set
>> > to have automatic addressing, automatic DNS and no gateway. When I run
>> > IPCONFIG, it shows that IP, gateway and DNS are assigned correctly by 
>> > my
>> > ISP.
>> > - I used the "Routing and Remote Access" wizard to configure the 
>> > server. I
>> > chose NAT radio button, and then I chose NIC A adapter
>> > - In DNS console, I added my ISP DNS in the forwarder, so that when an
>> > address is not resolved by this server, it will be redirected to my ISP
>> > DNS
>> > servers
>> >
>> > 2) Client computer
>> >
>> > - Name: CAROLINA
>> > - Windows 2000 professional
>> > - NIC connected to the hub and automatic IP addressing, automatic DNS 
>> > and
>> > no
>> > gateway.
>> > - When I ping WEBSERVER, it delays some time to resolve the IP but it
>> > finally resolves to the correct one: 192.168.1.1 and PING is 
>> > successful.
>> > - When I ping an Internet site, for example, www.google.cl, it cannot
>> > resolve the name.
>> >
>> > In conclusion, LAN works but it cannot connect to Internet through the
>> > server.
>> >
>> > What may be wrong with this configuration?
>> >
>> > Thanks a lot in advance
>> > Jaime
>>
>>
>>