Configuring WinXP as Gateway router

Hello...
I've WinXP Pro SP3 PC
It have 2 LAN cards and one "internal pci" aDSL modem (a WAN
connection)

I want to share that connection with these 2 LAN "outputs", and, if I
can, be able set which of these outputs gets more traffic priority...

How can I do that?

On Wed, 20 Aug 2008 23:24:03 -0700 (PDT), david2tm
<david2tm@gmail.com> wrote:

>Hello...
>I've WinXP Pro SP3 PC
>It have 2 LAN cards and one "internal pci" aDSL modem (a WAN
>connection)
>
>I want to share that connection with these 2 LAN "outputs", and, if I
>can, be able set which of these outputs gets more traffic priority...
>
>How can I do that?

Create a network bridge between the network connections for the two
LAN cards. Enable ICS on the aDSL modem connection. If it asks what
to use for the home network connection, tell it to use the network
bridge. I've written a web site with details:

Windows XP Internet Connection Sharing
http://www.practicallynetworked.com/sharing/xp_ics

I don't know of a way to set traffic priority.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Steve,

I've run into a similar problem (quoting your article):

WARNING #1: When you enable ICS, the network adapter connected to the local
area network is assigned a static IP address of 192.168.0.1. The client
computers are assigned other IP addresses in the 192.168.0.x range. These
addresses may not be compatible with an existing network

What seems to be happening is that enabling ICS wants to assign the
192.168.0.1 address to the wireless card connected to the DSL gateway, which
already has that address.

Do you know of any way to make this work?

I have networked a W2K Pro machine with my XP machine (the host) using a
crossover Ethernet cable (this actually seems to work better without the
crossover cable???), but have so far failed with static addresses on both
machines, bridging, etc.

Also thinking about trying to network with a router, but it would have to
have RJ45 ports and a way to connect to the DSL gateway wirelessly.

Let me know what you think.

Regards,
Larry Marquardt






--
PB


"Steve Winograd" wrote:

> On Wed, 20 Aug 2008 23:24:03 -0700 (PDT), david2tm
> <david2tm@gmail.com> wrote:
>
> >Hello...
> >I've WinXP Pro SP3 PC
> >It have 2 LAN cards and one "internal pci" aDSL modem (a WAN
> >connection)
> >
> >I want to share that connection with these 2 LAN "outputs", and, if I
> >can, be able set which of these outputs gets more traffic priority...
> >
> >How can I do that?
>
> Create a network bridge between the network connections for the two
> LAN cards. Enable ICS on the aDSL modem connection. If it asks what
> to use for the home network connection, tell it to use the network
> bridge. I've written a web site with details:
>
> Windows XP Internet Connection Sharing
> http://www.practicallynetworked.com/sharing/xp_ics
>
> I don't know of a way to set traffic priority.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

On Sat, 15 Nov 2008 11:43:01 -0800, Psycho-billy
<Psychobilly@discussions.microsoft.com> wrote:

>
>What seems to be happening is that enabling ICS wants to assign the
>192.168.0.1 address to the wireless card connected to the DSL gateway, which
>already has that address.
>
>Do you know of any way to make this work?
>
>I have networked a W2K Pro machine with my XP machine (the host) using a
>crossover Ethernet cable (this actually seems to work better without the
>crossover cable???), but have so far failed with static addresses on both
>machines, bridging, etc.
>


Is the "dsl gateway" a nat device? If so, uninstall ics because it
isn't required. If for some reason bridging doesn't work after this,
put the wired and wireless adaptors on different subnets and enable
routing between the wired and wireless interfaces as follows

System Key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
Value Name: IPEnableRouter
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled)

The crossover cable isn't always required if the network adaptors are
capable of auto sensing transmission and reception.



Jim.

James,

Thanks, I did read that my network card could sense a crossover cable, but
apparently the one on the W2K machine can't.

At any rate, it looks like I don't have ICS installed to begin with, not
sure why, but eventually, I'll try this with all that installed.

Also have been reading about TCP/IP binding to the two adapters, and my
system information is telling me that it too is not set up. The odd thing is
that the documentation is supposed to apply to W'98 & ME, yet it's in my Help
and Support App.

Not sure I should be in the Expert forum, because I need to read up on
subnets and masking too.

If I work this out, I'll post my solution.

Regards,
Larry Marquardt
--
PB


"James Egan" wrote:

>
> On Sat, 15 Nov 2008 11:43:01 -0800, Psycho-billy
> <Psychobilly@discussions.microsoft.com> wrote:
>
> >
> >What seems to be happening is that enabling ICS wants to assign the
> >192.168.0.1 address to the wireless card connected to the DSL gateway, which
> >already has that address.
> >
> >Do you know of any way to make this work?
> >
> >I have networked a W2K Pro machine with my XP machine (the host) using a
> >crossover Ethernet cable (this actually seems to work better without the
> >crossover cable???), but have so far failed with static addresses on both
> >machines, bridging, etc.
> >
>
>
> Is the "dsl gateway" a nat device? If so, uninstall ics because it
> isn't required. If for some reason bridging doesn't work after this,
> put the wired and wireless adaptors on different subnets and enable
> routing between the wired and wireless interfaces as follows
>
> System Key:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
> Value Name: IPEnableRouter
> Data Type: REG_DWORD (DWORD Value)
> Value Data: (0 = disabled, 1 = enabled)
>
> The crossover cable isn't always required if the network adaptors are
> capable of auto sensing transmission and reception.
>
>
>
> Jim.
>
>
>
>

James,

The DSL gateway is a NAT machine.

A couple of things on the XP machine:

I have the "Allow other network users to connect through this Internet
connection" option in the Advanced tab on my network connections (XP Pro),
but don't see the service???

"Add Remove Windows Components" does not show "Internet Tools" or any
reference to ICS???

The good news is that your key worked fine and I can connect via the LAN to
the W2K machine (no crossover cable this time), and can connect to the
Internet with the XP machine.

I lose connectivity when bridging the LAN and WLAN cards on the XP machine.

I am still not able to reach the internet from the W2K machine through the
XP Pro machine.

I know W2K isn't supported so if the problem is there, I will have to work
it out somehow.

Regards,
Larry Marquardt
--
PB


"James Egan" wrote:

>
> On Sat, 15 Nov 2008 11:43:01 -0800, Psycho-billy
> <Psychobilly@discussions.microsoft.com> wrote:
>
> >
> >What seems to be happening is that enabling ICS wants to assign the
> >192.168.0.1 address to the wireless card connected to the DSL gateway, which
> >already has that address.
> >
> >Do you know of any way to make this work?
> >
> >I have networked a W2K Pro machine with my XP machine (the host) using a
> >crossover Ethernet cable (this actually seems to work better without the
> >crossover cable???), but have so far failed with static addresses on both
> >machines, bridging, etc.
> >
>
>
> Is the "dsl gateway" a nat device? If so, uninstall ics because it
> isn't required. If for some reason bridging doesn't work after this,
> put the wired and wireless adaptors on different subnets and enable
> routing between the wired and wireless interfaces as follows
>
> System Key:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
> Value Name: IPEnableRouter
> Data Type: REG_DWORD (DWORD Value)
> Value Data: (0 = disabled, 1 = enabled)
>
> The crossover cable isn't always required if the network adaptors are
> capable of auto sensing transmission and reception.
>
>
>
> Jim.
>
>
>
>

On Mon, 17 Nov 2008 05:46:01 -0800, Psycho-billy
<Psychobilly@discussions.microsoft.com> wrote:

>I have the "Allow other network users to connect through this Internet
>connection" option in the Advanced tab on my network connections (XP Pro),
>but don't see the service???

This is ICS which needs to be UNCHECKED. You also need to set your
computer so that it connects to the Internet through a residential
gateway (not a direct connection). The network setup wizard might help
you through this bit. Also look here for general details.
http://www.practicallynetworked.com/sharing/xp_ics/

Once you have this successfully uninstalled and the computer is set to
receive its Internet connection via the LAN check that the machine is
set to receive an ip address automatically and also you might have to
re-make the registry change that I mentioned.

If bridging (the easier solution) doesn't work AFTER you have disabled
ICS successfully, post back and I'll give you some instructions for
connecting using routing. It's a little harder to configure because it
entails adding a static route to your dsl gateway.

Bridging is known to be a bit temperamental on occasions so don't
spend too much time on it if it doesn't work.



Jim.

James,

I've done as you suggest, but am unable to connect through a bridged
connection with full LAN connectivity avialable and a good wireless internet
connection.

I seem to be going backwards because I can now only ping from the XP machine
to the W2K machine and not vice verse.

Suspect my jockeying caused the problem, and will continue to troubleshoot.
(I was able to ping both ways at one point and am now waiting on a result
from resetting the duplex mode from auto at both ends to 10/100 on the W2K
and auto on the XP LAN card)

I keep running into the Routing and remote access service which is dependent
on NetBIOSGroup. I'm not sure it's possible to enable NetBIOSGroup and thus
Routing and Remote Access on a W2K workstation (as distinct from a server).

If you will instruct me on the static routing setup, I can hash this out
eventually.

Regards,
Larry
--
PB


"James Egan" wrote:

>
> On Mon, 17 Nov 2008 05:46:01 -0800, Psycho-billy
> <Psychobilly@discussions.microsoft.com> wrote:
>
> >I have the "Allow other network users to connect through this Internet
> >connection" option in the Advanced tab on my network connections (XP Pro),
> >but don't see the service???
>
> This is ICS which needs to be UNCHECKED. You also need to set your
> computer so that it connects to the Internet through a residential
> gateway (not a direct connection). The network setup wizard might help
> you through this bit. Also look here for general details.
> http://www.practicallynetworked.com/sharing/xp_ics/
>
> Once you have this successfully uninstalled and the computer is set to
> receive its Internet connection via the LAN check that the machine is
> set to receive an ip address automatically and also you might have to
> re-make the registry change that I mentioned.
>
> If bridging (the easier solution) doesn't work AFTER you have disabled
> ICS successfully, post back and I'll give you some instructions for
> connecting using routing. It's a little harder to configure because it
> entails adding a static route to your dsl gateway.
>
> Bridging is known to be a bit temperamental on occasions so don't
> spend too much time on it if it doesn't work.
>
>
>
> Jim.
>
>

On Tue, 18 Nov 2008 16:48:01 -0800, Psycho-billy
<Psychobilly@discussions.microsoft.com> wrote:

>
>I've done as you suggest, but am unable to connect through a bridged
>connection with full LAN connectivity avialable and a good wireless internet
>connection.
>
>I seem to be going backwards because I can now only ping from the XP machine
>to the W2K machine and not vice verse.


In all probability a firewall issue.


>
>Suspect my jockeying caused the problem, and will continue to troubleshoot.
>(I was able to ping both ways at one point and am now waiting on a result
>from resetting the duplex mode from auto at both ends to 10/100 on the W2K
>and auto on the XP LAN card)
>
>I keep running into the Routing and remote access service which is dependent
>on NetBIOSGroup. I'm not sure it's possible to enable NetBIOSGroup and thus
>Routing and Remote Access on a W2K workstation (as distinct from a server).
>

I'm not sure what you are trying to do here. From the point of view of
this networking exercise, the w2k machine is a client whose Internet
access depends on the winxp and no routing and remote access is
required from w2k. Perhaps you could clarify.

>If you will instruct me on the static routing setup, I can hash this out
>eventually.

From your first post the dsl gateway nat device is already at
192.168.0.1 and this needs to be on the same subnet as the winxp
wireless adaptor. The xp wired adaptor needs to be on a different
subnet along with with the w2k wired adaptor. So we will use the
existing 192.168.0.0/24 for the first subnet and use (say)
192.168.5.0/24 for this second subnet.

In addition, the xp machine needs to have a fixed ip address because
this will now be the gateway for the w2k to access the Internet. So
configure the computer tcp/ip properties as follows

xp wireless

static ip address 192.168.0.2 mask 255.255.255.0
default gateway 192.168.0.1
dns server 192.168.0.1 or your isp's nameserver address


xp wired

static ip address 192.168.5.1 mask 255.255.255.0
default gateway leave blank


w2k

static ip address 192.168.5.2 mask 255.255.255.0
default gateway 192.168.5.1
dns server 192.168.0.1 or your isp's nameserver address


dsl gateway

set a static route to send traffic for subnet 192.168.5.0 to go via
192.168.0.2


As stated previously you also need to enable routing between the wired
and wireless interfaces on the xp as follows

System Key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
Value Name: IPEnableRouter
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled)



Jim.

James, et al,

It turned out that Winsock was corrupted. Now back to pinging between the
two PC's.

Unable to ping the wireless adapter on the XP machine from the W2K machine
on the local LAN.

Unable to bridge LAN and WLAN on XP machine. Causes loss of internet
connection. Sharing doesn't work because of the DSL gateway (which is a NAT
capable machine - no info on config.)

Wondering whether this can be done more easily through Remote Access? Goal
is to use the XP machine to connect to and download service packs and IE 6
for the W2K machine).

You had mentioned something about static IP addresses?

Regards,
Larry Marquardt

--
PB


"James Egan" wrote:

>
> On Tue, 18 Nov 2008 16:48:01 -0800, Psycho-billy
> <Psychobilly@discussions.microsoft.com> wrote:
>
> >
> >I've done as you suggest, but am unable to connect through a bridged
> >connection with full LAN connectivity avialable and a good wireless internet
> >connection.
> >
> >I seem to be going backwards because I can now only ping from the XP machine
> >to the W2K machine and not vice verse.
>
>
> In all probability a firewall issue.
>
>
> >
> >Suspect my jockeying caused the problem, and will continue to troubleshoot.
> >(I was able to ping both ways at one point and am now waiting on a result
> >from resetting the duplex mode from auto at both ends to 10/100 on the W2K
> >and auto on the XP LAN card)
> >
> >I keep running into the Routing and remote access service which is dependent
> >on NetBIOSGroup. I'm not sure it's possible to enable NetBIOSGroup and thus
> >Routing and Remote Access on a W2K workstation (as distinct from a server).
> >
>
> I'm not sure what you are trying to do here. From the point of view of
> this networking exercise, the w2k machine is a client whose Internet
> access depends on the winxp and no routing and remote access is
> required from w2k. Perhaps you could clarify.
>
> >If you will instruct me on the static routing setup, I can hash this out
> >eventually.
>
> From your first post the dsl gateway nat device is already at
> 192.168.0.1 and this needs to be on the same subnet as the winxp
> wireless adaptor. The xp wired adaptor needs to be on a different
> subnet along with with the w2k wired adaptor. So we will use the
> existing 192.168.0.0/24 for the first subnet and use (say)
> 192.168.5.0/24 for this second subnet.
>
> In addition, the xp machine needs to have a fixed ip address because
> this will now be the gateway for the w2k to access the Internet. So
> configure the computer tcp/ip properties as follows
>
> xp wireless
>
> static ip address 192.168.0.2 mask 255.255.255.0
> default gateway 192.168.0.1
> dns server 192.168.0.1 or your isp's nameserver address
>
>
> xp wired
>
> static ip address 192.168.5.1 mask 255.255.255.0
> default gateway leave blank
>
>
> w2k
>
> static ip address 192.168.5.2 mask 255.255.255.0
> default gateway 192.168.5.1
> dns server 192.168.0.1 or your isp's nameserver address
>
>
> dsl gateway
>
> set a static route to send traffic for subnet 192.168.5.0 to go via
> 192.168.0.2
>
>
> As stated previously you also need to enable routing between the wired
> and wireless interfaces on the xp as follows
>
> System Key:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
> Value Name: IPEnableRouter
> Data Type: REG_DWORD (DWORD Value)
> Value Data: (0 = disabled, 1 = enabled)
>
>
>
> Jim.
>
>