Problem Description:

Using an Intel P4 Motherboard (D865PERLK) with built-in IEEE 1394 Firewire, I plug in a Digital video source, turn on its power, and XP Pro recognizes the unit. The Digital Video works fine. However, internet connectivity via the built-in network adapter (CAT5 to Linksys BEFSR41 router) goes away. Reboot doesn't help. To regain Internet connectivity I must rebuild the computer using a GHOST backup image.

Solutions by others:

Searching the internet found several "fixes" that didn't work for me; they may work for you.

• Adaptec says to delete files. Click here for their tech support article. (This is "Ask Adaptec" Answer ID 3743 at http://ask.adaptec.com/ )
  
•  MS in KB 817571 says to rebuild the winsock.
  
• MS in KB 283429 and  KB 823305 suggest it is a "bridge" problem.
  
• XP by default tries to use Firewire for the communications connection: Start | Settings | Control Panel then click on Network Connections. Right Click On Firewire Connection and Disable
  

Others have said these fixes worked for them, with "problem solved" posts. These fixes did not work for me.

My solution to my problem:

The Adaptec fix is correct, it is just not complete.

It seems that when there is an .INF file, there may be also a compiled version, a .PNF file. That is what was not allowing the adaptec fix to work.

Using my GHOST backup,  I reverted to a good machine image, then I deleted the files

Then I plugged in my digital video source and XP found it.

The new hardware wizard wanted to install software, and I canceled the wizard.

Then I went to device manager and found a yellow "?" at Other Devices/Unknown Device.

I selected the Unknown Device and uninstalled it.

All seems ok, reboots with or without the Digital Video Source (Canopus ADVC100) are ok. My internet access is fine. Whew.

I really would like the whole story behind what I have had to do to make firewire work as a video interface, not as a network interface. This should NOT be complicated, and Microsoft should explain what is going on.

I hope this is of help to others. Please let me know if you have something to add.

Jay O'Brien
Rio Linda, California
January 3, 2004

visit my tech page

Followup emails:

-------- Original Message --------
Subject: Re: Firewire conflict
Date: Sun, 04 Jan 2004 02:59:14 -0800
From: Mary Anne 
To:  Jay O'Brien <jayobrien@att.net>

Jay,

Thank you very much for your response on this matter.  To fix my problem I finally ended up calling my motherboard manufacturer (ASUS)and it was first believe my problem was related to an I/O chip as it didn't matter what PCI device I installed, the problem reoccured regardless of the slot and I'd end up reimaging my machine.   To finally resolve the problem, ASUS had me do a clean install of the OS (XP)on another hard drive to see if the problem occurred again.   The problem did not occur with a clean install (not a repair) so I did a clean install on my own hard drive and all functionality of the NIC card and the firewire card were restored.  It is important to note that my NIC in the first instance did not lose functionality.   I lost my DNS resolver capabilities only as I could ping outside with no problem.

A very frustrating problem and resolution but all is running well again and I am able to capture video with no problem AND research any problems on the internet!

Mary Anne

-------- Original Message --------
Subject:     1394 problems - THANKS!
Date:     Wed, 14 Jan 2004 09:18:28 -0700
From:     The Leggett's
To:     <jayobrien@att.net>

I just wanted to drop you a note to tell you that your page about the 1394 problems was a lifesaver for me today.
 
After screwing around with various combinations of the things you list, I believe the following worked for me  

• did a system restore to the previous day (no GHOST reload) exported the winsock and winsock2 entries from another XP machine I have to a floppy (didn't think I'd use the floppy on that computer when I built it!)
• deleted the winsock and winsock2 entries on my machine imported the winsock and winsock2 entries from other machine in windows/inf - renamed net1394.inf and net1394.pnf so they wouldn't be found
• powered off computer (simple restart didn't seem to do the trick) at power on, cancelled the hardware install wizard when it found NIC1394
• and internet worked again
  

I agree that this is an amazingly bad thing for microsoft to leave unaddressed
 
cheers,
bruce
 

-------- Original Message --------
Subject: IEEE 1394 Firewire kills internet connection
Date: Sat, 28 Feb 2004 21:52:31 +0100
From: Adriaan
To: <jayobrien@att.net

Hello Jay,
I experienced the same problem that you described on my (new) computer (MSI 865PE Neo2 motherboard with realtek 8169/8110 adpater on board and sitecom DC-202 router). I cannot say how happy I was finding your webpage. Not able to fix the problem made me nearly mad. It took me a couple of weeks and a lot of phone calls with several companies, but nobody could help me. The fixes that you (and Adaptec) suggested worked OK. But still one "problem" (a minor one) left: I uninstalled the unknown device, but everytime with a reboot or when I put the camera on, XP is asking to install Net 1394 and the install wizard comes up. How do I get rid of those annoying pop-up's ? (XP does too much thinking for you is my experience) But nevertheless thanks very much for your advice on your website.
Adriaan

-------- Original Message --------
Subject: Re: IEEE 1394 Firewire kills internet connection
Date: Sat, 28 Feb 2004 14:37:54 -0800
From: Jay O'Brien <jayobrien@att.net>
To: Adriaan

Adriaan,
I'm glad that my web page helped you. Sorry, but I don't have an answer to your remaining problem. But, should you find that answer, please send me details so I can add them to the web page?
Thanks,
Jay

-------- Original Message --------
Subject:     IEEE 1394 Firewire kills internet connection
Date:     Sun, 29 Feb 2004 08:03:26 +0100
From:     Adriaan
To:     <jayobrien@att.net>

Hello Jay,
This is the quickest response I had since times ! I think I found the "solution". Everytime after a reboot the NIC device comes back in the device manager. When I didn't remove it but simply disabled it, the XP pop-up's were gone. So I think it's better to disable it than removing it. Thanks again,
Adriaan
 
-------- Original Message --------
Subject: Re: firewire/internet problem in xp
Date: Sun, 4 Apr 2004 15:56:55 -0500
From: Marv & Kim Meyers
To: Jay O'Brien <jayobrien@att.net>

Jay,

Unfortunately, the solutions that have worked for you and your website visitors did not work in my case.  However, I have found another solution, albeit a rather painful one, to the firewire/internet problem.  With the firewire card preinstalled, I did a clean reinstall of Windows XP (attempts to simply "repair" windows xp, as suggested by microsoft support, hung up my system).  After doing this, both my firewire card and internet happily coexist in my computer. 

Please feel free to add this as a possible solution on your website for that those as desperate as I was for a solution to this problem.

Thanks,
Marv

/end/