PDA

View Full Version : Firewire and Ethernet

DG
14-01-2005, 07:16 PM
Both my desktop and laptop have firewire and ethernet but the laptop's is on 10 mb/s

I want to transfer files ebtween the two PC's and want to force the PC's to use the firewire cos it's like 40 time's faster!!

How do I force windows to move data onthe firewire and is there any software that can show me graphically or in any other way how data is flowing, either though the ethernet or firewire?
Mist
14-01-2005, 07:27 PM
Hmm.

First off I assume that you have a firewire interface then, and a firewire cable connecting the two PCs?

If that's the case, disable the nic that is working at 10m/sec and that should leave traffic routed to the other interface, no?
DG
15-01-2005, 02:48 AM
Hmm.

First off I assume that you have a firewire interface then, and a firewire cable connecting the two PCs?

If that's the case, disable the nic that is working at 10m/sec and that should leave traffic routed to the other interface, no?


That would kill my internet though!!

I'm sure it's something to do with metric values??
Mist
15-01-2005, 08:47 AM
That would kill my internet though!!

I'm sure it's something to do with metric values??

Ahh, I see what you mean.

In that case what you need to do is add in a static route for the computer you want to send data to via the firewire interface.

You'll need to open a DOS shell and type

ROUTE ADD dotted.ip.of.otherbox mask 255.255.255.254 IF x

where x is the number of the firewire interface (as listed in ipconfig)

you may also (I'm not sure) have to put a gateway IP before the IF in that, like

ROUTE ADD dotted.ip.of.otherbox mask 255.255.255.254 gateway.ip.address.here IF x

And if you do then the gateway IP is either the IP of the computer that you are trying to connect to OR the address assigned to the firewire nic. (I can't remember which).

You can, if you like, add in a metric for the route but I think it should be unneccessary.

Then, you'd need to do the reverse on the other PC.

This will be easier to achieve if you can have the firewire stuff running as a seperate network (eg 192.168.1.x if your other network is 192.168.0.x with a 255.255.255.0 subnet) that way you wouldn't have to worry about the static route at all I don't think.