3

I'm having trouble doing so. I basically want to transfer files between two PCs and also share the internet connection from one. As you may know Windows XP supports FireWire Network Adapters. What I've done so far:

I've tried setting up "office or home network" without any significant result.

I've tried assigning IPs to the 1394 adapters on both PCs (different of-course) but for some reason I can only ping from PC2 to PC1 (and not the other way around).

I've also tried enabling internet sharing on the 1394 on PC1 (where I have internet connection).

Also for some reason running "ipconfig /all" doesn't show my 1394 connection ips (on both PCs). The same goes if I try looking at the 1394 Connection Status->Support tab. That is strange.

And if I try to repair the connection on PC1 it tells me that "TCP/IP is not enabled for this connection" but I've surely seen it enabled in properties. On the other hand on PC2 when I try the same - the error message is different: "failed to query tcp/ip settings of the connection".

And the strange thing I also mentioned in the comments is that removing/inserting the FireWire cable doesn't affect anything on the OS (no message that there was something connected, no nothing). But the 1394 connection status is always connected.

However as I mentioned earlier I was sure at a moment that PC1 was pingable from PC2 (no longer I think).

Any ideas?

PC1 as connected to internet was updated to its latest version shortly after installation. PC2 on the other hand have never been connected to the internet and so it have never been updated after its initial installation. Though both PCs have the same SP2 (which is the last one for the x64 version of XP).

I tried installing some of the "offline updates" from msdn to PC2 but without much success. However I think they are all secure and not functional patches.

My 1394 adapter seems to be recognized and working fine by what Windows shows. Its exact name is "VIA OHCI Compilant IEEE 1394 Host Controller". I bought the exact same controllers for both of my PCs. Though now I can't exactly tell their model but I will if it could be important.

EDIT: OK - I think I partially fixed the problem. Maybe it was the driver, maybe my 1394 controller - i don't know but I connected to PC2 using the card internal port (inside the box) and now both PCs are recognizable one another and so pingable. However right now I'm struggling to share my internet connection from PC1 to PC2.

WindowsXpUser
  • 149
  • 1
  • 14
  • 1
    Can you show, in detail, what you did. (Commands and there output) – ctrl-alt-delor Jan 01 '16 at 00:32
  • I already explained all I have done. The only commands I've used are the 'ping' one on both computers. In case of pinging the one from the other I get 0% loss and in the other case I get 100% loss. – WindowsXpUser Jan 01 '16 at 19:42
  • Also from some reason my 1394 connection is always 'connected' no-matter that I've not connected anything to my VIA 1394 controller. – WindowsXpUser Jan 01 '16 at 19:56
  • 2
    Windows XP long ago passed its end of life. Have you tried a modern operating system? – ChrisInEdmonton Mar 15 '16 at 18:04
  • @ChrisInEdmonton And this is the reason for your down-vote - like seriously? I obviously have some reasons to use it. Quick example - compatibility (specifically VC++ 6.0). I need working with such older VS version because of RE (reverse-engineering) purposes. – WindowsXpUser Mar 15 '16 at 18:05
  • 1
    Well, in all fairness, modern operating systems have much, much better network stacks and often, much better driver support. It's a legit question; a modern operating system might well 'just work' for this. Plus, you won't be connecting a known-vulnerable system to the Internet. – ChrisInEdmonton Mar 15 '16 at 18:08
  • @ChrisInEdmonton Plus I want to know the answer of my exact question. And your 'preference' of what is better and what not can't be a reason for down-vote. Also I already explained you my reasons above. – WindowsXpUser Mar 15 '16 at 18:13
  • Plus on the one Windows XP x64 machine - I don't have ethernet port but only 1394 one. – WindowsXpUser Mar 15 '16 at 18:33
  • 1
    Your description of the problem is spotty - too many "on one computer" and "on the other" - try to better organize it and call the computers by name (eg. PC1 & PC2). Questions: (a) Are you on XP SP3 and all available patches installed? (b) Which 1394 adapters? Things to try : (1) Ensure that *both computers* have defined network shares, (2) Ensure the user of PC1 is known on PC2, (3) Check in Control Panel / Devices that Firewire is there on both computers without any yellow icons, (4) Try another Firewire cable. Last remark: XP 64-bit was always a bit of a lame duck. – harrymc Mar 15 '16 at 19:16
  • What are those network shares? Isn't it enough just to assign IPs to both 1394 Net adapters? – WindowsXpUser Mar 16 '16 at 12:04
  • Also is it normal the 1394 adapter to be always connected even if I remove the cable? And when I re-insert it - to have not a single notification on any of the PCs? – WindowsXpUser Mar 16 '16 at 12:26
  • 1
    I would honestly recommend just using XP in a VM if you really & truly need an XP device for something. Microsoft ended public *support* for that OS *seven* years ago (and extended support ended two years ago). This is a 15-year-old OS. But 10/100/1000 ethernet cards are about $20 these days; why don't you buy one of those and install it on your XP 64-bit machine? That way you can just set up a LAN. – TylerH Mar 16 '16 at 14:54
  • If one must use 1394 networking, then a later Windows than 2003 is precluded. Microsoft dropped 1394 networking with Vista and later. I'm actually a little surprised to learn that it's still working in 2003 SP1 (XP 64-bit edition is the same bits as 2003 SP1 x64). But, yeah, I would just buy a cheap Ethernet card and be done with it. – Jamie Hanrahan Mar 16 '16 at 18:35
  • @harrymc Server 2003 SP1 x64 was not a lame duck, and XP x64 is the same build. And FISOCPP is right in that it doesn't matter if shares are set up if the machines can't ping each other. You don't need shares set up for pings to work. – Jamie Hanrahan Mar 16 '16 at 18:37
  • @JamieHanrahan: Server 2003 was OK as a server, but XP 64-bit application and driver support weren't as good as in XP 32-bit. Adding network shares: This helps with some arcane problems. – harrymc Mar 16 '16 at 18:54
  • Ok. I thought you were referring to the OS and the stuff that came with the OS, which would include the tcp/ip stack. – Jamie Hanrahan Mar 16 '16 at 19:17

2 Answers2

1

The best way is to create an IP connection over Firewire. If you do this it would be like connecting a cross-over UTP cable fromone computer to another and then you can use FTP server and clinet to transfer files or other applications that run over normal TCP/IP networks.

Also Firewire is much faster than FastEthernet.

Here is a tutorial about how to create the IP connection over Firewire.

http://lifehacker.com/173973/geek-to-live--fast-one-wire-network-ip-over-firewire

After you do this set the IP and subnet masks of both computers accordingly (Subnet mask should be the same and IPs from the same subnet e.g 169.254.1.1 and 168.254.1.2 with the s.m set to 255.255.0.0)

The install Filezilla FTP server and Filezilla ftp client and from the client connect to the IP of the server and you can start transferring files.

You can try other FTP client/server.

If you encounter problems please ask.

yoyo_fun
  • 1,791
  • 5
  • 26
  • 48
1

The problem was partially hardware and partially software misunderstanding. It seemed that my firewire adapter 4-conductor port that I was using had it's pins misplaced. I had to manually fix this using small screwdriver. But even then I got a lot of problem with it so I started using the 6-conductor one and now I got zero problems on the hardware side. The conclusion is to avoid using 4-conductor connectors if possible. Bear in mind that if the 2 PCs are connected properly - device connected sound will be played when cable is plugged and of-course disconnect one when unplugged.

Then on the software side. I got confused with the "Internet Gateway" connection quite some time thinking it was instead the ICS point (on PC1) but now I understand that this is actually something else non-related (which I still can't quite understand but anyway). Another thing I was missing is the fact that in order to enable ICS - you should have at least more then 1 internet adapters enabled. I also got problems with the internet connection from PC2, even though PC1 had proper ICS configuration. This was fixed with renewing the PC2 "1394 Net adapter" ips (by using 'repair' option on it). Another way to get over this would be restarting your machine I think. But before that I now remember I also got problems with creating the ICS on PC1. This was linked with my internet router using the IP 192.168.0.1 which was reserved for ICS to be set up and working. I fixed this by changing my router ip.

Also I think it's strongly recommended to let ip settings be automatically assigned to both PC1 and PC2 1394 adapters.

Right now everything is perfect and working as it would be expected. If PC1 is running, PC2 have internet without any additional settings to be changed at start-up. Another great thing is that both PC1 and PC2 files are directly (and automatically) accessible from any of the computers through the administrator shares of your drives. Because of that though I suggest disabling "File and Printer sharing" on your internet connection (for security measures).

WindowsXpUser
  • 149
  • 1
  • 14