Implementing firewire network.

D

Deck

I currently have two XP machines networked through a router. I will call
them MCE (XP media center 2005) and XP (professional)for the purpose of this
message. MCE is connected via Wireless-G to the router and XP is connected
via wired ethernet to the router. Currently the router is also the DHCP
server so these machines have all of their IP information assigned to them.

Both of these machines also have a 1394 firewire port which I want to make
use of on a temporary basis to transfer very large files between the
machines (ISO images). The regular network works flawlessly but I need to
know what I need to do to setup the firewire network on a multi-homed
machine.

Currently when I repair the firewire connections it tells me that "TCP/IP is
not enabled on this connection". Going into properties for the 1394
connection I see that the TCP/IP prococal is installed and it say connected.
If I do an Ipconfig /all I don't see any information about the firewire
port.

Do I have to manually setup the IP addresses for the firewire ports? My
router is on 192.168.1.0 with a mask of 255.255.255.0, do I need to setup
the IP addresses for the 1394 connections on a different subnet or just a
different network? Can I use 192.168.2.0 with a mask of 255.255.255.0 for
the 1394 connections? What should I make the default gateway and the DNS
addresses?

I can't seem to get past the message "TCP/IP is not enabled on this
connection".

Any help would be greatly appreciated.

Deck
 
T

Treeman

Deck said:
I currently have two XP machines networked through a router. I will
call
them MCE (XP media center 2005) and XP (professional)for the purpose of
this
message. MCE is connected via Wireless-G to the router and XP is
connected
via wired ethernet to the router. Currently the router is also the
DHCP
server so these machines have all of their IP information assigned to
them.

Both of these machines also have a 1394 firewire port which I want to
make
use of on a temporary basis to transfer very large files between the
machines (ISO images). The regular network works flawlessly but I need
to
know what I need to do to setup the firewire network on a multi-homed
machine.

Currently when I repair the firewire connections it tells me that
"TCP/IP is
not enabled on this connection". Going into properties for the 1394
connection I see that the TCP/IP prococal is installed and it say
connected.
If I do an Ipconfig /all I don't see any information about the
firewire
port.

Do I have to manually setup the IP addresses for the firewire ports?
My
router is on 192.168.1.0 with a mask of 255.255.255.0, do I need to
setup
the IP addresses for the 1394 connections on a different subnet or just
a
different network? Can I use 192.168.2.0 with a mask of 255.255.255.0
for
the 1394 connections? What should I make the default gateway and the
DNS
addresses?

I can't seem to get past the message "TCP/IP is not enabled on this
connection".

Any help would be greatly appreciated.

Deck

Hi Deck,
Consider this a friendly *bump*

Reality #1 SP2 firewire drivers will show o.k. in device manager, but
can't connect. SP1 firewire drivers do work. Before you pull your hair
out, here's a firewire networking primer:
'Network' (http://www.homenethelp.com/network/firewire.asp)

If you can connect with SP2 great! If not, I have had success with
this:

Go to C:\WINDOWS\Driver Cache\i386 & C:\dllcache in SP1 and copy out
the
following files
SBP2port.sys is in C:\Windows\System32\Drivers & \system32\dllcache
1394bus.sys is in C:\Windows\System32\Drivers
arp1394.sys is in C:\Windows\System32\Drivers
nic1394.sys is in c:\Windows\System32\Drivers
ohci1394.sys is in C:\windows\System32\drivers
enum1394.sys is in C:\windows\system32\drivers

Copy out the following files to a new folder you can call
"Firewirefix," (without quotes)

Stop XP Sp2 from re-installing it's drivers again by:
Renaming the XP2.cab file to (e.g. to XP2old.cab)

Replace the SP2 versions of these files with the SP1 versions in
C:\WINDOWS\system32\drivers & C:\WINDOWS\system32\dllcache in safe
mode.

Go to device manager for your ohci firewire card and update SP2 drivers
to the SP1 drivers by pointing to Firewirefix.(warning message normal)
Reboot.

You won't get much help on this forum for firewire. (read; denial of
problems)
It's your fault! Hope the information supplied will be of value.
Your mileage may vary,
Treeman
 
S

Steve Winograd [MVP]

"Deck" said:
I currently have two XP machines networked through a router. I will call
them MCE (XP media center 2005) and XP (professional)for the purpose of this
message. MCE is connected via Wireless-G to the router and XP is connected
via wired ethernet to the router. Currently the router is also the DHCP
server so these machines have all of their IP information assigned to them.

Both of these machines also have a 1394 firewire port which I want to make
use of on a temporary basis to transfer very large files between the
machines (ISO images). The regular network works flawlessly but I need to
know what I need to do to setup the firewire network on a multi-homed
machine.

Currently when I repair the firewire connections it tells me that "TCP/IP is
not enabled on this connection". Going into properties for the 1394
connection I see that the TCP/IP prococal is installed and it say connected.
If I do an Ipconfig /all I don't see any information about the firewire
port.

Do I have to manually setup the IP addresses for the firewire ports? My
router is on 192.168.1.0 with a mask of 255.255.255.0, do I need to setup
the IP addresses for the 1394 connections on a different subnet or just a
different network? Can I use 192.168.2.0 with a mask of 255.255.255.0 for
the 1394 connections? What should I make the default gateway and the DNS
addresses?

I can't seem to get past the message "TCP/IP is not enabled on this
connection".

Any help would be greatly appreciated.

Deck

TCP/IP should be automatically enabled on the Firewire connections.
Since it isn't, I recommend going to Device Manager, un-installing the
"1394 Net Adapter", and clicking "Action" | "Scan for hardware
changes" to re-install it. That will create a new Firewire
connection.

Assign a static private IP address to each connection, using a
different subnet than the router. 192.168.2.x is fine. I use
10.0.0.x for my Firewire network. Since the Firewire connection won't
have Internet access, don't specify a default gateway or DNS address.

To make a file copy use the Firewire connection, access the other
computer using its Firewire IP address, not its computer name. For
example, if you've assigned 192.168.2.1 and 192.168.2.2, access the
first computer by typing this line in the Start | Run box:

\\192.168.2.1
--
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top