The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    IP over Firewire on XP

    Discussion in 'Networking and Wireless' started by csr, Oct 22, 2004.

  1. csr

    csr Notebook Enthusiast

    Reputations:
    0
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    5
    I am trying to share files between two notebook computers with Firewire.

    Through a local router over ethernet, Windows file sharing works fine.

    When I just connect the two computers using only Firewire, they seem to recognize the port connection and the both system port status show packets tx and rx. Each side assigns an automatic local private IP address.

    However, the windows file sharing does not work. I've tried assigning a static local IP address and nothing seems to happen.

    Does anyone been able to file share on XP (SP2) using Firewire direct connection? Can you share your set up?

    Thanks
     
  2. csr

    csr Notebook Enthusiast

    Reputations:
    0
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    5
    Ok, Just figured it out. The connection will work fine with automatic private IP address.

    The trick is to turn off both machines and boot up both with Firewire already attached with no other LAN cables active.

    Once the system boots up, now you have 400MHz connection between the two to transfer files. Once the connection is made, you can connect other LAN cables for internet connection.
     
  3. jchastain

    jchastain Notebook Consultant

    Reputations:
    3
    Messages:
    177
    Likes Received:
    0
    Trophy Points:
    30
    Yep. You figured it out. The other option would have been far more complex - manually configuring your route table (with the route command).