Yes Wayne, but have you ever had two paths to the same host name? This is really the core of the problem IMHO.
No argument. Windows tries to bridge everything together when the Networking Wizard is used.
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.
Once I broke the bridging I had no problems & fwiw I always manually set the ip addys too as I've had problems with addys jumping when using DHCP via routers &/or Winders in the past. Those DHCP problems may have been fixed in XP but once slapped twice shy. ;-)
----------+----------
Wayne D. Johnson
Ashland, OH, USA 44805
<http://www.wavijo.com>
