Yes Wayne, but have you ever had two paths to the same host name? This is really the core of the problem IMHO.

Without trying here I'd have to guess that you would also have to set a lower Metric on the firewire interface or else windows would just assume one or the other path automatically even with Ben's suggestion of using the hosts file.

But assuming that Ethernet is 192.168.0.0/24 and FW was 192.168.1.0/24. Then assigning each machine an alias unique vs. their windows host name would allow resolution (via hosts or DNS) to the FW network's IP and route without confusion about where you are going. Right?

So "MachineA-FW" would give you 192.168.1.x, and "MachineA" would resolve to 192.168.0.y.


Wayne Johnson wrote:
At 03:56 PM 5/18/2005, Ben Ruset typed:

Just give each firewire adapter a non-routable IP address. Put each pc's name and firewire IP in each pc's hosts file. then you should be able to ping/connect via pc name on the firewire network.


While I don't doubt that works I never had to go thru that to get my firewire network to function.



Reply via email to