Re: Problem configuring NAT to share Internet Connection




I would check the NAT settings first. For more and other information, go to http://howtonetworking.com.

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
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Hi robert,

This is the routing table of the server:

Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     200.74.186.1   200.74.186.222      1
         10.0.0.0        255.0.0.0         10.0.0.1         10.0.0.1     10
         10.0.0.1  255.255.255.255        127.0.0.1        127.0.0.1     10
   10.255.255.255  255.255.255.255         10.0.0.1         10.0.0.1     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.0.0    255.255.255.0      192.168.0.1      192.168.0.1     20
      192.168.0.1  255.255.255.255        127.0.0.1        127.0.0.1     20
    192.168.0.255  255.255.255.255      192.168.0.1      192.168.0.1     20
     200.74.186.1  255.255.255.255   200.74.186.222   200.74.186.222      1
   200.74.186.222  255.255.255.255        127.0.0.1        127.0.0.1     50
   200.74.186.255  255.255.255.255   200.74.186.222   200.74.186.222     50
        224.0.0.0        240.0.0.0         10.0.0.1         10.0.0.1     10
        224.0.0.0        240.0.0.0      192.168.0.1      192.168.0.1     20
        224.0.0.0        240.0.0.0   200.74.186.222   200.74.186.222      1
  255.255.255.255  255.255.255.255         10.0.0.1         10.0.0.1      1
  255.255.255.255  255.255.255.255      192.168.0.1      192.168.0.1      1
  255.255.255.255  255.255.255.255   200.74.186.222   200.74.186.222      1
Default Gateway:      200.74.186.1

This is the IPCONFIG information of the server (where you can see Internet
interface, that connects to the DSL modem, LAN interface, that connects to
the LAN and the Manquehue interface that is the DSL modem itself):

Windows IP Configuration

   Host Name . . . . . . . . . . . . : srv-dev
   Primary Dns Suffix  . . . . . . . : DESYTEC.North
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : DESYTEC.North

Ethernet adapter Internet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-11-43-2F-69-26
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.0.0.1
   Subnet Mask . . . . . . . . . . . : 255.0.0.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 127.0.0.1

Ethernet adapter LAN:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : D-Link DFE-530TX PCI Fast Ethernet
Adapte
r (rev.C)
   Physical Address. . . . . . . . . : 00-0D-88-CA-8F-CC
   DHCP Enabled. . . . . . .. . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 127.0.0.1

PPP adapter Manquehue:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
   Physical Address. . . . . . . . . : 00-53-45-00-00-00
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 200.74.186.222
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 0.0.0.0
   DNS Servers . . . . . . . . . . . : 200.74.160.103
                                       200.74.160.104
   NetBIOS over Tcpip. . . . . . . . : Disabled

As another fact, I tell you that DNS is working properly. For example, this
is the TRACERT response from the client:

C:\Documents and Settings\Administrator>tracert www.google.cl

Tracing route to www.l.google.com [64.233.161.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.

And finally, this is the PathPing response from the client:

C:\Documents and Settings\Administrator>PathPing www.google.cl

Tracing route to www.l.google.com [64.233.161.104]
over a maximum of 30 hops:
  0  carolina.DESYTEC.North [192.168.0.2]
  1  192.168.0.1
  2     *        *        *
Computing statistics for 50 seconds...


As you see, packets reach 192.168.0.1 (LAN interface in the server) but it
isn't redirected to the 10.0.0.1 interface.

Additionally, I tell you that in RRAS console I have these "strange" things:

1.- Network Interaces:
    a.- Manquehue Interface, type: Demand-dial, status: Enabled, Connection
State: Unreachable
    b.- Loopback Interface (looks correct)
    c.- LAN Interface (looks correct)
    d.- Internet Interface (looks correct)
    e.- Internal Interface, type: Internal, status: Enabled, Connection
state: Connected (what is this interface?)
2.- Ports: Status of all ports appear Inactive
3.- IP routing:
    a.- General: Manquehue IP address appears "Not available" and
Unreachable. Internal IP address also appears "Not available", Unknown
administrative status and non-operational.
    b.- Static routes: Dest->0.0.0.0, Network mask->0.0.0.0, Gateway->none,
Interface->Manquehue, Metric->1, View->Both (I have added this entry manually)
    c.- IGMP: Manquehue protocol is Proxy and state is down. Querier address
is 0.0.0.0. Internet protocol is Router V3 and state is Querier. Querier
address is 10.0.0.1
    d.- NAT/Basic Firewall: Manquehue , Internet and Internal. All of them
never show numbers different from 0 in Mappings and Packets traslated and
rejected columns.
4.- Remote Access Policies, I kept default policies (2 policies)


I hope that with all this antecedents you can guide me to solve the problem.

Thanks a million in advance
Jaime


"Robert L [MS-MVP]" wrote:

> assuming you can access the Internet from the server but not from the clients, you may have a routing issue. posting the result of routing tables of both server and client ay help, For more and other information, go to http://howtonetworking.com.
>
> 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
> How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
> I recommend Brinkster for web hosting!
>
>   "Jaime Stuardo" <JaimeStuardo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:72B5E074-0408-4F11-94AE-D59DF59EE690@xxxxxxxxxxxxx...
>   Hi all...
>
>   I spent too much time trying to configure NAT in Windows Server 2003 to let
>   other LAN PC's to connect to Internet through the server without success.
>
>   This is the scenario:
>
>   1.- Window Server 2003 machine with 2 NIC's, NIC A and NIC B.
>   2.- NIC A is connected by mean of a UTP cable to a DSL modem. I have
>   assigned NIC A this IP address: 10.0.0.1
>   3.- NIC B is connected to a hub. I have assigned NIC B this IP address:
>   192.168.0.1
>   4.- 2 PC's connected to the hub. Their IP addresses are: 192.168.0.2 and
>   192.168.0.3
>   5.- Server is a domain controller and all LAN PC's are joined to the domain.
>   6.- LAN works perfect.
>   7.- To connect server to Internet, I create a new network connection. So,
>   finally I have 3 network connections, 2 corresponding with NIC A and NIC B
>   that were configured automatically when I installed operating system. The
>   3rd. connection corresponds the connection to my ISP, that assigns a dynamic
>   IP each time I dial it.
>
>   This was what I did:
>
>   1.- Installed RRAS/VPN server role.
>   2.- In MMC console, under network connections node I can see some
>   connections. 2 corresponds to the NICs A and B and other, named Internal, I
>   think corresponds to the DSL modem.
>   3.- Since I need RRAS to demand dial my ISP, I created there a new network
>   interface using the same name as in Network Connections in control panel.
>   4.- When the new interface appears in the list, it says that it is
>   unreachable. I try to connect but it says that modem is being used.
>   5.- I was already connected to Internet so I disconnected
>   6.- I tried to connect that interface again using RRAS console and it cannot
>   due to time out.
>   7. I tried several ways, using all the wizards and manually, but I cannot
>   make it to work. Only server could browse internet, but not client computers.
>
>   Any help will be greatly appreciated. My main problem is that I connect one
>   NIC to a DSL modem that assigns a dynamic IP.
>
>   Thanks a lot in advance,
>   Jaime
>


Relevant Pages

  • Re: Cant stay on line long enough
    ... then click Network Connections. ... internet security package, such as: ... Norton Internet Security 2003 ...
    (microsoft.public.windowsxp.security_admin)
  • Re: NT AUTHORITYSYSTEM shutdown
    ... The first thing you should do is enable Windows XP's built-in Firewall: ... then click Network Connections. ... I can't use the internet nor e-mails | for my business at all. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: blaster worm
    ... The first thing you should do is enable Windows XP's built-in Firewall: ... then click Network Connections. ... internet security package, such as: ...
    (microsoft.public.windowsxp.security_admin)
  • Re: w.32blaster.worm
    ... The first thing you should do is enable Windows XP's built-in Firewall: ... then click Network Connections. ... internet security package, such as: ...
    (microsoft.public.windowsxp.security_admin)
  • Re: NT4 Naming Probs
    ... I'm no network expert but isn't the domain search list going to look at "ourdomn1.co.uk" FIRST to resolve and then go up the network? ... And isn't the IP addresses part of the public Internet range? ... Always try the MS KB first before posting. ...
    (microsoft.public.windows.server.networking)