Problem configuring NAT to share Internet Connection

Guest · Apr 21, 2005

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

Robert L [MS-MVP] · Apr 21, 2005

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!

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

Guest · Apr 22, 2005

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] · Apr 22, 2005

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.
I recommend Brinkster for web hosting!

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

Guest · Apr 23, 2005

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:
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.
I recommend Brinkster for web hosting!

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 said:

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!

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

Click to expand...

Guest · Apr 23, 2005

This is the client routing table:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 6e 2f cf f9 ...... SiS 900-Based PCI Fast Ethernet Adapter
- Pa
cket Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 20
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.3 192.168.0.3 20
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 20
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 20
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

Other question: do you know what "Internal" interface is?
In RRAS MMC, NAT/Basic firewall node, appear 3 interfaces (automatically
added by the wizard): LAN, Internet and Internal. LAN and Internet correspond
with both NICS in the server. What about "Internal"? I could think that is is
the DSL modem, but, why the name is Internal and not something more
meaningful, such as "external"? why cannot I delete it?

Thanks
Jaime

Robert L said:
the routing table you posted look good. but i wish you posted the client routing table too.
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!

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:

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.
I recommend Brinkster for web hosting!

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 said:

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!

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

Click to expand...

Click to expand...

Robert L [MS-MVP] · Apr 23, 2005

the routing table you posted look good. but i wish you posted the client routing table too.
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!

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:
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.
I recommend Brinkster for web hosting!

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 said:

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!

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

Click to expand...

Guest · Apr 23, 2005

Robert, since if I ping an internet site from a client computer getting its
IP, is it mean that I can reach Internet?

Moreover, examining the first line of the server routing table:

0.0.0.0 0.0.0.0 200.119.229.120 200.119.229.120 1

I can interpret that all addresses not matched by the other table entries
(for example, Internet addresses) are routed to 200.119.229.120 through the
Interface 200.119.229.120. And that address is the ISP assigned address so
that, can I be certain that internet packets reach 200.119.229.120? how can I
monitor the network so that I can know the route for a packet?

If routing is correct. Could it be a firewall problem? I tried opening the
web port in the interface named "Internet" but it didn't work either.

Jaime

Robert L said:
the routing table you posted look good. but i wish you posted the client routing table too.
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!

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:

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.
I recommend Brinkster for web hosting!

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 said:

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!

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

Click to expand...

Click to expand...

Robert L [MS-MVP] · Apr 24, 2005

The client routing table looks good too. you may want to re-setup RRAS and make sure no filtering blocking the traffic. I just worked on a similar case. although the resolution is not for your case, it may give you some tips. quoted from http://www.howtonetworking.com/casestudy.htm

Case Study - Can't access the Internet through Windows Server 2003 as a router
Situation: A law firm IT department supports three attorney offices. Recently, they decided to separated the LAN into three subnets by adding a Windows Server 2003 with four network cards as a router.

The Windows 2003 Standard Server was configured with RRAS and DHCP capabilities. The 4 NICs were installed and configured (192.168.0.1 connecting to a Sonicwall firewall, 192.168.1.0/24 for the LAN1, 192.168.2.0/24 for LAN2 and 192.168.3.0/24 for the LAN3). RRAS was installed using the custom configuration option with just LAN Routing. DHCP was installed and configured.

Problem: The router server can ping all LAN and access the Internet. But no computers in three LANs can access the Internet. They can ping the inside IP of the server but not the outside NIC's IP, 192.168.0.1. So, they called chicagoTech.net for help.

Troubleshooting:

1. Ipconfig /all on the server displayed correct settings and IP routing was enabled.

2. Re-configured the RRAS.

3. No ISA, NAT or oother security software running.

4. No filtering blocked the traffic.

5. Client ipconfig /all displayed uncorrected default gateway which was assigned by DHCP, for example, a computer in the LAN1 had default IP 192.168.0.1 instead of 192.168.1.1. Note: default gateway must in the same subnet.

Resolution: modified the DHCP Scope Options and assigned the router accordingly.

Related Topics

Routing Issues

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!

This is the client routing table:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 6e 2f cf f9 ...... SiS 900-Based PCI Fast Ethernet Adapter
- Pa
cket Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 20
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.3 192.168.0.3 20
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 20
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 20
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

Other question: do you know what "Internal" interface is?
In RRAS MMC, NAT/Basic firewall node, appear 3 interfaces (automatically
added by the wizard): LAN, Internet and Internal. LAN and Internet correspond
with both NICS in the server. What about "Internal"? I could think that is is
the DSL modem, but, why the name is Internal and not something more
meaningful, such as "external"? why cannot I delete it?

Thanks
Jaime

Robert L said:
the routing table you posted look good. but i wish you posted the client routing table too.
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!

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:

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.
I recommend Brinkster for web hosting!

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 said:

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!

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

Click to expand...

Click to expand...

Guest · Apr 25, 2005

Hi Robert,

I have tried configuring the default gateway but it didn't work either.

I tell you that I have discovered on the weekend that I don't have a DSL
modem, but a DSL router, so that it has it's own IP address, 192.168.1.1.
That's why the NIC connected to it needs to be assigned a static IP.

Finally, the configuration of the NIC's was as follows:

1.- DSL router -> 192.168.1.1
2.- NIC A connected to the DSL router -> 192.168.1.2
3.- NIC B connected to the LAN -> 192.168.1.3
4.- Client computer 1 -> 192.168.1.4
5.- Client computer 2 -> 192.168.1.5

That way, in the server I need to create a broadband connection, as always.
And after connected I think I can treat the connection as if it is always on.

I have reconfigured RRAS to be NIC B the NIC with IP routing, and I have
configured DHCP scope to assign default gateway 19.168.1.1 but it didn't
work. And If I configure the default gateway of NIC A to be also 192.168.1.1,
server cannot browse Internet.

Finally, I continue only to resolve well the host names from the clients,
but not to connect.

I'm wondering why using ICS/ICF all is configured good automatically, at
first try. What does it do internally? I followed a lot of microsoft pages
that shows what it is configured by ICS and I tried to imitate it, but
without success.

The problem I have now is that I cannot configure ICS/ICF again, because
that option isn't appear in the broadband network connection advanced tab
properties, as before.

Jaime

Robert L said:
The client routing table looks good too. you may want to re-setup RRAS and make sure no filtering blocking the traffic. I just worked on a similar case. although the resolution is not for your case, it may give you some tips. quoted from http://www.howtonetworking.com/casestudy.htm

Case Study - Can't access the Internet through Windows Server 2003 as a router
Situation: A law firm IT department supports three attorney offices. Recently, they decided to separated the LAN into three subnets by adding a Windows Server 2003 with four network cards as a router.

The Windows 2003 Standard Server was configured with RRAS and DHCP capabilities. The 4 NICs were installed and configured (192.168.0.1 connecting to a Sonicwall firewall, 192.168.1.0/24 for the LAN1, 192.168.2.0/24 for LAN2 and 192.168.3.0/24 for the LAN3). RRAS was installed using the custom configuration option with just LAN Routing. DHCP was installed and configured.

Problem: The router server can ping all LAN and access the Internet. But no computers in three LANs can access the Internet. They can ping the inside IP of the server but not the outside NIC's IP, 192.168.0.1. So, they called chicagoTech.net for help.

Troubleshooting:

1. Ipconfig /all on the server displayed correct settings and IP routing was enabled.

2. Re-configured the RRAS.

3. No ISA, NAT or oother security software running.

4. No filtering blocked the traffic.

5. Client ipconfig /all displayed uncorrected default gateway which was assigned by DHCP, for example, a computer in the LAN1 had default IP 192.168.0.1 instead of 192.168.1.1. Note: default gateway must in the same subnet.

Resolution: modified the DHCP Scope Options and assigned the router accordingly.

Related Topics

Routing Issues

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!

This is the client routing table:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 6e 2f cf f9 ...... SiS 900-Based PCI Fast Ethernet Adapter
- Pa
cket Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 20
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.3 192.168.0.3 20
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 20
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 20
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

Other question: do you know what "Internal" interface is?
In RRAS MMC, NAT/Basic firewall node, appear 3 interfaces (automatically
added by the wizard): LAN, Internet and Internal. LAN and Internet correspond
with both NICS in the server. What about "Internal"? I could think that is is
the DSL modem, but, why the name is Internal and not something more
meaningful, such as "external"? why cannot I delete it?

Thanks
Jaime

Robert L said:

the routing table you posted look good. but i wish you posted the client routing table too.
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!

I have checked NAT configuration and all seems OK and the site you gave
doesn't help too much.

But can you say something about the information I posted? does it look right?

The main problem I have, that isn't treated in any site I visited, is
concerning the hardware I have. One of my NICs in the server connect to a DSL
modem and it connects to internet. How can I manage that case in RRAS console?

Thanks
Jaime

Robert L said:

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.
I recommend Brinkster for web hosting!

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

:

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!

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

Click to expand...

Click to expand...

jamal montazerolghaem · Jan 10, 2006

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: 11.11.11.11
3.- NIC B is connected to a hub. I have assigned NIC B this IP address:
10.10.0.40
4.- 2 PC's connected to the hub. Their IP addresses are: 10.10.0.41 and 10.
10.0.42
5.- 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

Robert L [MS-MVP] · Jan 10, 2006

I am not sure the issue, but posting the result of ipconfig /all may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
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: 11.11.11.11
3.- NIC B is connected to a hub. I have assigned NIC B this IP address:
10.10.0.40
4.- 2 PC's connected to the hub. Their IP addresses are: 10.10.0.41 and 10.
10.0.42
5.- 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

Bill Grant · Jan 10, 2006

It really depends on how you connect to the Internet. If it is PPPoE you
should use the PPPoE interface in RRAS. If it isn't, you need to correctly
configure your external interface to dial up your ISP.

The RRAS internal interface has nothing to do with this. It is only used
by remote access clients (ie RAS or VPN).

Bill Grant · Jan 13, 2006

I should have pointed out that because your server can connect to the
Internet doesn't automatically mean that you can share the connection.
Before you can share a connection using RRAS/NAT, the Internet connection
must appear in RRAS as an interface. Only then can you configure NAT. The
PPPoE interface is OK, or a demand-dial interface.

Problem configuring NAT to share Internet Connection

Guest

Robert L [MS-MVP]

Guest

Robert L [MS-MVP]

Guest

Guest

Robert L [MS-MVP]

Guest

Robert L [MS-MVP]

Guest

jamal montazerolghaem

Robert L [MS-MVP]

Bill Grant

Bill Grant