WinXP 3 NICs

Hello,

I do need some answers regarding my network setup and it goes like this:

(A) DSL/LAN Cable (ISP)
V
V
V
(B) DSL Linksys Router/Switch (192.168.0.120 > 192.168.8.1)
V
V
(C) Linksys Switch (192.168.8.0) or (192.168.0.0)
V
V
(D) -----> goes to 1st subnet (primary 192.168.8.0) or (backup 192.168.0.0)
V
V
(E) -----> WinXP (3 NICs)
a. 192.168.8.2 - primary network OR (192.168.0.1 when ICS is ON)
b. 192.168.1.2 - secondary network (connected to 2nd router (F) )
c. VSAT Connection (DHCP) - Serves as failover connection via ICS
V
V
(F) DSL Linksys Router (192.168.0.0 - DHCP > 192.168.1.1)
V
V
(G) goes to 2nd network (public/guest) - 192.168.1.0


Notes
------

On (B) Linksys Router, is pretty straight forward. Having its IP set to
static from ISP and on the other end I used the default setting of the
router (192.168.8.1) as its network for the primary.


On (C), all other clients connected on this end is set to obtain IP from the
router (B)

On (E), I choose WinXP as the common to every network inside the work place.
That is, regardless wether they are on network (C) or (F), I can make
centralize server where all shared and backup files can be.
Also, to save me some troubles, whenever the DSL connection is down I can
easily switch to an ICS from the VSAT connection and enabling the sharing to
NIC (a) - 192.168.8.2. And to do this I need to physically remove the
connection from the DSL/LAN off the Linksys switch (C) so that DHCP of the
WinXP ICS (E) will be used.


My question is, on WinXP ICS (E), I noticed that every query of the modem
driver for the VSAT most of its packets (udp) are being redirected to NIC
(a) thus creating a battle neck on the DSL connection which in short time
freezes its connection. I do need to reset the router (B) switch all the
time. Turning off the modem does not do the trick cause its services are
running. Disabling these services is a daunting task every time you switch
back and forth from either connection. As for me I do not bother, but
problem is for those people who will be left behind and has little knowhow
when I'm away.

Going back to my problem, what I did this time, I block the the two NICs (a
& b) from its corresponding router for not be able to send those packets
from the VSAT driver. It helps and reduces the udp packet query. But
still, I noticed that Internet connection for the DSL sometimes get stuck.

1. When I takeoff the VSAT services from WinXP ICS machine, all outlook
auto send and recieve works fine
2. However, when I switch back ON the VSAT services, some of the clients
outlook get stuck and popup for their user name and password plus having an
intermittent connection when browsing to the Internet (time out from the
client side).

But based on the packet logs from the WinXP ICS machine, udp query is not
that rampant. BTW, i'm using windump (similar to tcpdump on linux) to watch
all those packets that comming and out into the machine.

Woh... this was a long story thou.. my apology folks... I just run out of
ideas how to resolve this.

Any possible solution will be highly appreciated...

Regards

John










JohnT

Seems like it's an binding order issue.
In Network places properties, click on
'Advance' menu and select Advaced Settings.
Move up or do wn the 3 NICs and set the order
properly, by your preferece of binding order.

From what you told, when your VSAT link is up you
may have to adjust the binding order again.

Sharad
"JohnT" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> I do need some answers regarding my network setup and it goes like this:
>
> (A) DSL/LAN Cable (ISP)
> V
> V
> V
> (B) DSL Linksys Router/Switch (192.168.0.120 > 192.168.8.1)
> V
> V
> (C) Linksys Switch (192.168.8.0) or (192.168.0.0)
> V
> V
> (D) -----> goes to 1st subnet (primary 192.168.8.0) or (backup
192.168.0.0)
> V
> V
> (E) -----> WinXP (3 NICs)
> a. 192.168.8.2 - primary network OR (192.168.0.1 when ICS is ON)
> b. 192.168.1.2 - secondary network (connected to 2nd router (F) )
> c. VSAT Connection (DHCP) - Serves as failover connection via ICS
> V
> V
> (F) DSL Linksys Router (192.168.0.0 - DHCP > 192.168.1.1)
> V
> V
> (G) goes to 2nd network (public/guest) - 192.168.1.0
>
>
> Notes
> ------
>
> On (B) Linksys Router, is pretty straight forward. Having its IP set to
> static from ISP and on the other end I used the default setting of the
> router (192.168.8.1) as its network for the primary.
>
>
> On (C), all other clients connected on this end is set to obtain IP from
the
> router (B)
>
> On (E), I choose WinXP as the common to every network inside the work
place.
> That is, regardless wether they are on network (C) or (F), I can make
> centralize server where all shared and backup files can be.
> Also, to save me some troubles, whenever the DSL connection is down I can
> easily switch to an ICS from the VSAT connection and enabling the sharing
to
> NIC (a) - 192.168.8.2. And to do this I need to physically remove the
> connection from the DSL/LAN off the Linksys switch (C) so that DHCP of the
> WinXP ICS (E) will be used.
>
>
> My question is, on WinXP ICS (E), I noticed that every query of the modem
> driver for the VSAT most of its packets (udp) are being redirected to NIC
> (a) thus creating a battle neck on the DSL connection which in short time
> freezes its connection. I do need to reset the router (B) switch all the
> time. Turning off the modem does not do the trick cause its services are
> running. Disabling these services is a daunting task every time you
switch
> back and forth from either connection. As for me I do not bother, but
> problem is for those people who will be left behind and has little knowhow
> when I'm away.
>
> Going back to my problem, what I did this time, I block the the two NICs
(a
> & b) from its corresponding router for not be able to send those packets
> from the VSAT driver. It helps and reduces the udp packet query. But
> still, I noticed that Internet connection for the DSL sometimes get stuck.
>
> 1. When I takeoff the VSAT services from WinXP ICS machine, all outlook
> auto send and recieve works fine
> 2. However, when I switch back ON the VSAT services, some of the clients
> outlook get stuck and popup for their user name and password plus having
an
> intermittent connection when browsing to the Internet (time out from the
> client side).
>
> But based on the packet logs from the WinXP ICS machine, udp query is not
> that rampant. BTW, i'm using windump (similar to tcpdump on linux) to
watch
> all those packets that comming and out into the machine.
>
> Woh... this was a long story thou.. my apology folks... I just run out of
> ideas how to resolve this.
>
> Any possible solution will be highly appreciated...
>
> Regards
>
> John
>
>
>
>
>
>
>
>

Hello Sharad,

I'm not sure what u mean by the binding issue under network places advance
properties....

Anyway, just an added info, with respect to each NIC, under its interface
metrics I set it as follows:

(E) -----> WinXP (3 NICs)
a. 192.168.8.2 - Metric 45
b. 192.168.1.2 - Metric 75
c. VSAT Connection (DHCP) - Metric 1


John

Well, not the metric.
You open network connections from the control Panel.
When it opens, on the menu bar click on 'Advanced' menu and Select Advance
settings.
There on 'Adapter and Bindings' tab, under 'Connections:' you will find the
3 NICs listed by there name (and if any other modem connetions etc. those
will be listed.) The one that appears at the top has highest priority, and
next down to it, 2 nd priority and so on.
You can select one of the adapter and using the right side arrow, can move
them up or down.

Further after reading your post once again, it appears that the binding
order also has to be changed on other clients machines (if they too have
more than one network connection (either NIC or modem). The top one shown on
client machines, will be given first priority for use, if it is down then
only the 2nd priority connection will be used.

Sharad

"JohnT" <(E-Mail Removed)> wrote in message
news:%23e$$c%(E-Mail Removed)...
> Hello Sharad,
>
> I'm not sure what u mean by the binding issue under network places advance
> properties....
>
> Anyway, just an added info, with respect to each NIC, under its interface
> metrics I set it as follows:
>
> (E) -----> WinXP (3 NICs)
> a. 192.168.8.2 - Metric 45
> b. 192.168.1.2 - Metric 75
> c. VSAT Connection (DHCP) - Metric 1
>
>
> John
>
>

Well that's a new one to me... thanks to the info....

Anyway, just an added info... the VSAT connection has a bad latency
connection.

I'm not quite sure about how things work with the binding... Let say I set
everything to obtain the IP automatically from the said machine (WinXP ICS)
and connection from the VSAT is not that good, will the packets redirected
to the one with better connection assuming both connections are working
(VSAT & DSL)?

e.g.
1- Good
10 - Bad

VSAT connection - 7
DSL - 1


????

John

No. If VSAT has higher priority, it will be used,
and if VSAT is not at all connected, then DSL will be
used.

Sharad
"JohnT" <(E-Mail Removed)> wrote in message
news:eZG$(E-Mail Removed)...
> Well that's a new one to me... thanks to the info....
>
> Anyway, just an added info... the VSAT connection has a bad latency
> connection.
>
> I'm not quite sure about how things work with the binding... Let say I set
> everything to obtain the IP automatically from the said machine (WinXP
ICS)
> and connection from the VSAT is not that good, will the packets redirected
> to the one with better connection assuming both connections are working
> (VSAT & DSL)?
>
> e.g.
> 1- Good
> 10 - Bad
>
> VSAT connection - 7
> DSL - 1
>
>
> ????
>
> John
>
>