Keep routing table

G

Guest

Hi as requested in a previous post, i've a multi-homed server with 3 public
lan and 1 private nic.

I've found a routing table that work fine but it never remain after restart.
The routing table work executing 2 command that delete the route (but i
suppose that there some problems) of range for 2 nics.

There's a way to set as persistant this configuration?

Thanks in advance.

Massimo Artini
 
J

Jud

Massimo Artini said:
Hi as requested in a previous post, i've a multi-homed server with 3 public
lan and 1 private nic.

I've found a routing table that work fine but it never remain after restart.
The routing table work executing 2 command that delete the route (but i
suppose that there some problems) of range for 2 nics.

There's a way to set as persistant this configuration?

Thanks in advance.

Massimo Artini

Add /persistent yes when adding the routes.

Jud
 
B

barry

Massimo Artini said:
Hi as requested in a previous post, i've a multi-homed server with 3
public
lan and 1 private nic.

I've found a routing table that work fine but it never remain after
restart.
The routing table work executing 2 command that delete the route (but i
suppose that there some problems) of range for 2 nics.

There's a way to set as persistant this configuration?

Thanks in advance.

Massimo Artini

C:\WINDOWS>route

Manipulates network routing tables.

ROUTE [-f] [-p] [command [destination]
[MASK netmask] [gateway] [METRIC metric] [IF interface]

-f Clears the routing tables of all gateway entries. If this is
used in conjunction with one of the commands, the tables are
cleared prior to running the command.
-p When used with the ADD command, makes a route persistent
across
boots of the system. By default, routes are not preserved
when the system is restarted. Ignored for all other commands,
which always affect the appropriate persistent routes. This
option is not supported in Windows 95.
command One of these:
PRINT Prints a route
ADD Adds a route
DELETE Deletes a route
CHANGE Modifies an existing route
destination Specifies the host.
MASK Specifies that the next parameter is the 'netmask' value.
netmask Specifies a subnet mask value for this route entry.
If not specified, it defaults to 255.255.255.255.
gateway Specifies gateway.
interface the interface number for the specified route.
METRIC specifies the metric, ie. cost for the destination.

All symbolic names used for destination are looked up in the network
database
file NETWORKS. The symbolic names for gateway are looked up in the host name
database file HOSTS.

If the command is PRINT or DELETE. Destination or gateway can be a wildcard,
(wildcard is specified as a star '*'), or the gateway argument may be
omitted.

If Dest contains a * or ?, it is treated as a shell pattern, and only
matching destination routes are printed. The '*' matches any string,
and '?' matches any one char. Examples: 157.*.1, 157.*, 127.*, *224*.
Diagnostic Notes:
Invalid MASK generates an error, that is when (DEST & MASK) != DEST.
Example> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1 IF 1
The route addition failed: The specified mask parameter is
invalid.
(Destination & Mask) != Destination.

Examples:
route PRINT
route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
destination^ ^mask ^gateway metric^ ^
Interface^
If IF is not given, it tries to find the best interface for a given
gateway.
route PRINT
route PRINT 157* .... Only prints those matching 157*
route CHANGE 157.0.0.0 MASK 255.0.0.0 157.55.80.5 METRIC 2 IF 2

CHANGE is used to modify gateway and/or metric only.
 
G

Guest

Thanks for your reply,

well...

I don't need to add a route. I know the /persistent switch of command
route.exe. But i need to set as persistent a "route delete" command (that not
support the /persistent).

I think to create a script that remove at startup this configuration but i
don't like this way.

You know other way to manually create a route table without automatic
construction from windows?

Thanks

Massimo Artini
 
D

David Carlsson

Why do you need to delete any routes?
The only routes in the table by default is to the nic:s own net, broadcast nets, mylticast nets, localhost net and other nets (default gateway).
If you have default gateway set on all nic:s you might have some problems if only one is connected to the outside world. But then you just have to leave it empty in the nics configuration for the ones that isn't.

/D
 
G

Guest

Hi,

yes i know... :) But is the only way i found to solve the problem that i
explain in a previous post... :)

So you know a way to set 3 different public network on a single pc with no
routing problems.

Thanks in advance...
 
P

Phillip Windell

Massimo Artini said:
So you know a way to set 3 different public network on a single pc with no
routing problems.

The very fact that you are doing that to begin with is the problem. You
should avoid such a situation to begin with. Maybe if you decribe
(accuartely) the situation that leads you to do this someone is very likely
to suggest a better way to approach the whole thing, assuming you are
willing to do the right thing.
 
G

Guest

Yes. Well the situation is the following:

I need to implement a Multi Homed configuration with NIC as follow:

1 LAN
3 xDSL Disjoint Public Networks

I try to configure each public NIC with Default Gateway but in most cases a
NIC reply to remote response than the TCP packet route to default gateway.

I need to solve this problem because:

- 1 xDSL is a 2 Mbps but i pay per use (in byte)
- 1 xDSL is a 800 Kbps guarantee flat
- 1 xDSL is a 512 Kbps not guarantee flat (only for internal use)

You can understand that i want that each NIC must route on itself default
gateway.

the actual table routing is:

===========================================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 02 44 0f 90 24 ...... SURECOM EP-320X-S 100/10M Ethern
0x1000005 ...00 10 a7 0f c8 de ...... NDIS 5.0 driver

0x3000004 ...00 60 08 ae 42 ea ...... 3Com 3C90x Ethernet Adapter
0x4000006 ...00 02 44 30 0c 6a ...... SURECOM EP-320X-S 100/10M Ethern
===========================================================================
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfac. Metric
0.0.0.0 0.0.0.0 62.110.203.201 62.110.203.202 1
0.0.0.0 0.0.0.0 81.75.35.238 81.75.35.236 1
0.0.0.0 0.0.0.0 85.35.149.105 85.35.149.108 1

62.110.203.202 255.255.255.255 127.0.0.1 127.0.0.1 1
62.110.203.200 255.255.255248 62.110.203.202 62.110.203.202
62.255.255.255 255.255.255.255 62.110.203.202 62.110.203.202 1
81.75.35.232 255.255.255.248 81.75.35.238 81.75.35.236 1
81.75.35.236 255.255.255.255 127.0.0.1 127.0.0.1 1
81.75.35.237 255.255.255.255 127.0.0.1 127.0.0.1 1
81.255.255.255 255.255.255.255 81.75.35.236 81.75.35.236 1
85.35.149.104 255.255.255.248 85.35.149.108 85.35.149.108
85.35.149.108 255.255.255.255 127.0.0.1 127.0.0.1 1
85.35.149.109 255.255.255.255 127.0.0.1 127.0.0.1 1
85.255.255.255 255.255.255.255 85.35.149.108 85.35.149.108 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 1
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 1
224.0.0.0 224.0.0.0 62.110.203.202 62.110.203.202 1
224.0.0.0 224.0.0.0 81.75.35.236 81.75.35.236 1
224.0.0.0 224.0.0.0 85.35.149.108 85.35.149.108 1
224.0.0.0 224.0.0.0 192.168.1.2 192.168.1.2 1
255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
Gateway predefinito: 81.75.35.238
===========================================================================
Route persistenti:
Nessuno


the actual ipconfig /all is

Configurazione IP di Windows 2000

Nome host . . . . . . . . . . . : critone
Suffisso DNS primario . . . . . : chatwithme.it
Tipo nodo . . . . . . . . . . . : Ibrido
IP Routing abilitato. . . . . . : No
WINS Proxy abilitato. . . . . . : No
Elenco di ricerca suffisso DNS . : chatwithme.it

- Scheda Ethernet Connessione alla rete locale (LAN):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter
Indirizzo fisico. . . . . . . . : 00-02-44-0F-90-24
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3

- Scheda Ethernet Connessione alla rete Internet (HDSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : Scheda Fast Ethernet Bus PCI
ND010 E
thernet/ #2
Indirizzo fisico. . . . . . . . : 00-10-A7-0F-C8-DE
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 62.110.203.202
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 62.110.203.201
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 192.168.1.1
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Intranet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter #2
Indirizzo fisico. . . . . . . . : 00-02-44-30-0C-6A
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 85.35.149.109
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 85.35.149.108
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Internet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
(3C
905-TX)
Indirizzo fisico. . . . . . . . : 00-60-08-AE-42-EA
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 81.75.35.237
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 81.75.35.236
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 81.75.35.238
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 81.75.35.233
NetBIOS su Tcpip. . . . . . . . : Disabilitata
 
P

Phillip Windell

You can only have *one* Default Gateway (other nics must remain blank). The
other two remaining external Nic must depend on Static routes to *specific*
networks.

The internal Nic does not need anyting unless there is more than one
internal subnet,...in which case it needs a Static Route to cover any
internal "pathes".
 
G

Guest

Hi,

Well right. I've just tryied with this configuration. And i try to add this
persist route

Suppose that 81.75.35.238 is the default gateway so

i add this 2 route (as readed in a previous post)

- route add 85.35.149.104 mask 255.255.255.248 85.35.149.105
- route add 62.110.203.200 mask 255.255.255.248 62.110.203.201

but the packet get the "wrong way". I mean: a ping call on 62.110.203.202
reply on 81.75.35.236...

I think... may a solve creating a RRAS with NAT that publish all 3 public
network?

Thanks for your help

and it doesn't work...

Phillip Windell said:
You can only have *one* Default Gateway (other nics must remain blank). The
other two remaining external Nic must depend on Static routes to *specific*
networks.

The internal Nic does not need anyting unless there is more than one
internal subnet,...in which case it needs a Static Route to cover any
internal "pathes".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Massimo Artini said:
Yes. Well the situation is the following:

I need to implement a Multi Homed configuration with NIC as follow:

1 LAN
3 xDSL Disjoint Public Networks

I try to configure each public NIC with Default Gateway but in most cases a
NIC reply to remote response than the TCP packet route to default gateway.

I need to solve this problem because:

- 1 xDSL is a 2 Mbps but i pay per use (in byte)
- 1 xDSL is a 800 Kbps guarantee flat
- 1 xDSL is a 512 Kbps not guarantee flat (only for internal use)

You can understand that i want that each NIC must route on itself default
gateway.

the actual table routing is:

===========================================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 02 44 0f 90 24 ...... SURECOM EP-320X-S 100/10M Ethern
0x1000005 ...00 10 a7 0f c8 de ...... NDIS 5.0 driver

0x3000004 ...00 60 08 ae 42 ea ...... 3Com 3C90x Ethernet Adapter
0x4000006 ...00 02 44 30 0c 6a ...... SURECOM EP-320X-S 100/10M Ethern
===========================================================================
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfac. Metric
0.0.0.0 0.0.0.0 62.110.203.201 62.110.203.202 1
0.0.0.0 0.0.0.0 81.75.35.238 81.75.35.236 1
0.0.0.0 0.0.0.0 85.35.149.105 85.35.149.108 1

62.110.203.202 255.255.255.255 127.0.0.1 127.0.0.1 1
62.110.203.200 255.255.255248 62.110.203.202 62.110.203.202
62.255.255.255 255.255.255.255 62.110.203.202 62.110.203.202 1
81.75.35.232 255.255.255.248 81.75.35.238 81.75.35.236 1
81.75.35.236 255.255.255.255 127.0.0.1 127.0.0.1 1
81.75.35.237 255.255.255.255 127.0.0.1 127.0.0.1 1
81.255.255.255 255.255.255.255 81.75.35.236 81.75.35.236 1
85.35.149.104 255.255.255.248 85.35.149.108 85.35.149.108
85.35.149.108 255.255.255.255 127.0.0.1 127.0.0.1 1
85.35.149.109 255.255.255.255 127.0.0.1 127.0.0.1 1
85.255.255.255 255.255.255.255 85.35.149.108 85.35.149.108 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 1
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 1
224.0.0.0 224.0.0.0 62.110.203.202 62.110.203.202 1
224.0.0.0 224.0.0.0 81.75.35.236 81.75.35.236 1
224.0.0.0 224.0.0.0 85.35.149.108 85.35.149.108 1
224.0.0.0 224.0.0.0 192.168.1.2 192.168.1.2 1
255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
Gateway predefinito: 81.75.35.238
===========================================================================
Route persistenti:
Nessuno


the actual ipconfig /all is

Configurazione IP di Windows 2000

Nome host . . . . . . . . . . . : critone
Suffisso DNS primario . . . . . : chatwithme.it
Tipo nodo . . . . . . . . . . . : Ibrido
IP Routing abilitato. . . . . . : No
WINS Proxy abilitato. . . . . . : No
Elenco di ricerca suffisso DNS . : chatwithme.it

- Scheda Ethernet Connessione alla rete locale (LAN):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter
Indirizzo fisico. . . . . . . . : 00-02-44-0F-90-24
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3

- Scheda Ethernet Connessione alla rete Internet (HDSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : Scheda Fast Ethernet Bus PCI
ND010 E
thernet/ #2
Indirizzo fisico. . . . . . . . : 00-10-A7-0F-C8-DE
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 62.110.203.202
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 62.110.203.201
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 192.168.1.1
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Intranet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter #2
Indirizzo fisico. . . . . . . . : 00-02-44-30-0C-6A
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 85.35.149.109
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 85.35.149.108
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Internet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
(3C
905-TX)
Indirizzo fisico. . . . . . . . : 00-60-08-AE-42-EA
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 81.75.35.237
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 81.75.35.236
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 81.75.35.238
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 81.75.35.233
NetBIOS su Tcpip. . . . . . . . : Disabilitata
 
P

Phillip Windell

but the packet get the "wrong way". I mean: a ping call on 62.110.203.202
reply on 81.75.35.236...

How do you know that?
I think... may a solve creating a RRAS with NAT that publish all 3 public
network?

No. That is not a solution.
 
G

Guest

Hi,

well i use nektwork monitor to view trafic on the 81.75.35.236 NIC and
the 62.110.203.202 NIC. So i can see a request on 62.110.203.202 and the
reply on 81.75.35.236.

Have you ever seen a problem like this one?

Thanks for your help

Massimo Artini


Massimo Artini said:
Hi,

Well right. I've just tryied with this configuration. And i try to add this
persist route

Suppose that 81.75.35.238 is the default gateway so

i add this 2 route (as readed in a previous post)

- route add 85.35.149.104 mask 255.255.255.248 85.35.149.105
- route add 62.110.203.200 mask 255.255.255.248 62.110.203.201

but the packet get the "wrong way". I mean: a ping call on 62.110.203.202
reply on 81.75.35.236...

I think... may a solve creating a RRAS with NAT that publish all 3 public
network?

Thanks for your help

and it doesn't work...

Phillip Windell said:
You can only have *one* Default Gateway (other nics must remain blank). The
other two remaining external Nic must depend on Static routes to *specific*
networks.

The internal Nic does not need anyting unless there is more than one
internal subnet,...in which case it needs a Static Route to cover any
internal "pathes".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Massimo Artini said:
Yes. Well the situation is the following:

I need to implement a Multi Homed configuration with NIC as follow:

1 LAN
3 xDSL Disjoint Public Networks

I try to configure each public NIC with Default Gateway but in most cases a
NIC reply to remote response than the TCP packet route to default gateway.

I need to solve this problem because:

- 1 xDSL is a 2 Mbps but i pay per use (in byte)
- 1 xDSL is a 800 Kbps guarantee flat
- 1 xDSL is a 512 Kbps not guarantee flat (only for internal use)

You can understand that i want that each NIC must route on itself default
gateway.

the actual table routing is:

===========================================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 02 44 0f 90 24 ...... SURECOM EP-320X-S 100/10M Ethern
0x1000005 ...00 10 a7 0f c8 de ...... NDIS 5.0 driver

0x3000004 ...00 60 08 ae 42 ea ...... 3Com 3C90x Ethernet Adapter
0x4000006 ...00 02 44 30 0c 6a ...... SURECOM EP-320X-S 100/10M Ethern
===========================================================================
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfac. Metric
0.0.0.0 0.0.0.0 62.110.203.201 62.110.203.202 1
0.0.0.0 0.0.0.0 81.75.35.238 81.75.35.236 1
0.0.0.0 0.0.0.0 85.35.149.105 85.35.149.108 1

62.110.203.202 255.255.255.255 127.0.0.1 127.0.0.1 1
62.110.203.200 255.255.255248 62.110.203.202 62.110.203.202
62.255.255.255 255.255.255.255 62.110.203.202 62.110.203.202 1
81.75.35.232 255.255.255.248 81.75.35.238 81.75.35.236 1
81.75.35.236 255.255.255.255 127.0.0.1 127.0.0.1 1
81.75.35.237 255.255.255.255 127.0.0.1 127.0.0.1 1
81.255.255.255 255.255.255.255 81.75.35.236 81.75.35.236 1
85.35.149.104 255.255.255.248 85.35.149.108 85.35.149.108
85.35.149.108 255.255.255.255 127.0.0.1 127.0.0.1 1
85.35.149.109 255.255.255.255 127.0.0.1 127.0.0.1 1
85.255.255.255 255.255.255.255 85.35.149.108 85.35.149.108 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 1
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 1
224.0.0.0 224.0.0.0 62.110.203.202 62.110.203.202 1
224.0.0.0 224.0.0.0 81.75.35.236 81.75.35.236 1
224.0.0.0 224.0.0.0 85.35.149.108 85.35.149.108 1
224.0.0.0 224.0.0.0 192.168.1.2 192.168.1.2 1
255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
Gateway predefinito: 81.75.35.238
===========================================================================
Route persistenti:
Nessuno


the actual ipconfig /all is

Configurazione IP di Windows 2000

Nome host . . . . . . . . . . . : critone
Suffisso DNS primario . . . . . : chatwithme.it
Tipo nodo . . . . . . . . . . . : Ibrido
IP Routing abilitato. . . . . . : No
WINS Proxy abilitato. . . . . . : No
Elenco di ricerca suffisso DNS . : chatwithme.it

- Scheda Ethernet Connessione alla rete locale (LAN):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter
Indirizzo fisico. . . . . . . . : 00-02-44-0F-90-24
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3

- Scheda Ethernet Connessione alla rete Internet (HDSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : Scheda Fast Ethernet Bus PCI
ND010 E
thernet/ #2
Indirizzo fisico. . . . . . . . : 00-10-A7-0F-C8-DE
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 62.110.203.202
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 62.110.203.201
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 192.168.1.1
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Intranet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : SURECOM EP-320X-S 100/10M
Ethernet P
CI Adapter #2
Indirizzo fisico. . . . . . . . : 00-02-44-30-0C-6A
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 85.35.149.109
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 85.35.149.108
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . :
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
NetBIOS su Tcpip. . . . . . . . : Disabilitata

- Scheda Ethernet Connessione alla rete Internet (ADSL):

Suffisso DNS specifico connessione:
Descrizione . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
(3C
905-TX)
Indirizzo fisico. . . . . . . . : 00-60-08-AE-42-EA
DHCP abilitato . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . : 81.75.35.237
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Indirizzo IP. . . . . . . . . . . : 81.75.35.236
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Gateway predefinito . . . . . . . : 81.75.35.238
Server DNS. . . . . . . . . . . : 192.168.1.1
192.168.1.3
Server WINS primario . . . . . . : 81.75.35.233
NetBIOS su Tcpip. . . . . . . . : Disabilitata



:

So you know a way to set 3 different public network on a single pc with no
routing problems.

The very fact that you are doing that to begin with is the problem. You
should avoid such a situation to begin with. Maybe if you decribe
(accuartely) the situation that leads you to do this someone is very likely
to suggest a better way to approach the whole thing, assuming you are
willing to do the right thing.
 
P

Phillip Windell

well i use nektwork monitor to view trafic on the 81.75.35.236 NIC and
the 62.110.203.202 NIC. So i can see a request on 62.110.203.202 and the
reply on 81.75.35.236.

That isn't your problem and is actually not a problem,...it is normal. The
path taken is not "stateful", only the packets internally are statefull and
the packets don't care how they got there, only that they got there. In
otherwords the path taken in the return direction has no relationship to the
path taken on the outbound side. Each path is determined independently based
on the routing scheme at the Source. This means you have no control over
the route taken for the return path, you only control the outbound path.

Your big problem is that you are running 4 nics in the ISA with three
Default Gateways. Of the three Default Gateways,...2 are done in the GUI and
one is manually entered in the Routing Table.

You can only have *one* Default Gateway. By the very definition of the
term, you can only have one. Since the inbound traffic seems to return to
the 81.75.35.236-237 Interface then that is the one where the Default
Gateway goes.

All other Interfaces *must* leave the Default Gateway blank. Any "paths"
you require must be entered into the Routing Table manually and they must be
*specified* paths,...you can not use "0.0.0.0" as the Destination in the
route.

1. Correct the Default Gateway problem in the GUI of the Nics.
2. Clear the Route Table by using "Route /f" from a command prompt.
3. Reboot the machine to let the Route Table rebuild correctly.
4. Enter any required Static Routes into the Routing Table. "0.0.0.0" is
not allowed in the Static routes you create
 
P

Phillip Windell

Phillip Windell said:
Your big problem is that you are running 4 nics in the ISA with three

It doens't matter if it is ISA or not,...the same principles apply.
 
G

Guest

that's it... thanks. I suppose that i can't control the packet... but... in a
configuration a found, every nic reply to their own router...

well... so

Thanks a lot. i proceed with the steps you send me.

Thanks.

Massimo Artini
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top