Routing in Windows XP

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Setup is Server & clients connected via 802.11G network.

Problem is a paradox database needs to be stored on a CLIENT, with access
from another CLIENT over a cross-over cable.

Reason being is the 802.11g just isn't cutting the mustard with the big
database (too slow), and we know it works well over 100/1000Mbps.

I thought I could simply connect the two nics with cross-over and any
traffic destined from Client1 to Client2 I could simply be re-route over the
faster wired link.

After an hour I've come no closer. What is the correct way to do this? Both
PCs are in the same workgroup already, so this could be a problem? Is this
even possible?

Ive tried unused addresses on the same subnet - this causes traffic to go
over the wireless link, ignoring the wired, and I've tried putting both
client nics on a different but then they can't even ping each other -
destination unreachable.

I've tried playing with the route command but have to admit I don't
understand enough about routes.

Can somebody help me?

Regards,
Ed.
 
Setup is Server & clients connected via 802.11G network.

Problem is a paradox database needs to be stored on a CLIENT, with access
from another CLIENT over a cross-over cable.

Reason being is the 802.11g just isn't cutting the mustard with the big
database (too slow), and we know it works well over 100/1000Mbps.

I thought I could simply connect the two nics with cross-over and any
traffic destined from Client1 to Client2 I could simply be re-route over the
faster wired link.

After an hour I've come no closer. What is the correct way to do this? Both
PCs are in the same workgroup already, so this could be a problem? Is this
even possible?

Ive tried unused addresses on the same subnet - this causes traffic to go
over the wireless link, ignoring the wired, and I've tried putting both
client nics on a different but then they can't even ping each other -
destination unreachable.

I've tried playing with the route command but have to admit I don't
understand enough about routes.

Can somebody help me?

Regards,
Ed.
Click to expand...

The wired network has to use a different subnet than the wireless one.

Here's how I've set up my network, where three of the computers
communicate with each other using FireWire for faster speed than
Ethernet:

1. The Ethernet network uses the 192.168.123.x range, assigned by a
DHCP server.

1. I assign static private IP addresses, in a subnet used only for
FireWire, to each computer's FireWire connection: 10.0.0.2, 10.0.0.3,
and 10.0.0.4, with subnet mask 255.0.0.0.

2. To be sure that a connection between computers uses FireWire
instead of Ethernet, I reference the other computer using its FireWire
IP address, not its computer name. Examples:

\\10.0.0.2 - access computer directly
net use x: \\10.0.0.2\data - map a network drive
--
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
 
Back
Top