TCP/IP not working in IEEE 1394 connection

[Jerry Paquette]

About 10 days ago I had my laptop stolen (Acer Travelmate, 2000
vintage). I've replaced it with a current Travelmate (800). I had a
Ghost image of the old machine (XP Pro, retail license version, not OEM)
and decided to try putting in on the new machine and doing an inplace
hardward upgrade to avoid the misery of reconfiguring and reinstalling
everything.

Generally the process worked flawlessly. Unfortunately, however, the
NIC (IEEE 1394) doesn't function with TCP/IP. The card connects but no
packets are exchanged. Trying to "Repair" the connection results in an
error saying "TCP/IP is not enabled for this connection. Cannot
proceed." TCP/IP works fine on the (internal) wireless connection on
the same machine. I use a linksys router so the IP numbers are supplied
by the router

I tried running netsh as described at:
http://support.microsoft.com/defaul...port/kb/articles/Q299/3/57.ASP&NoWebContent=1

It ran okay but didn't affect the problem. I've also tried removing the
IEEE 1394 adapted in Device Manager and rebooting with no luck.

ipconfig /all gives (the IEEE 1394 connection isn't even found):

-------------------------------------

Windows IP Configuration


Host Name . . . . . . . . . . . . : machine_name
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Wireless Network Connection 2:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless LAN
2100 3B Mini PCI Adapter
Physical Address. . . . . . . . . : 00-04-23-4B-3E-23
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 129.100.2.12

129.100.74.79
Lease Obtained. . . . . . . . . . : Sunday, July 13, 2003
3:25:35 PM
Lease Expires . . . . . . . . . . : Monday, July 14, 2003
3:25:35 PM

 

[Jerry Paquette]

Okay--as a colleague just reminded me, IEEE 1394 is firewire--so the real problem here is
why isn't XP recognizing the onboard NIC in the new laptop? Any ideas?

 

[jal]

snap

Exactly the same problem, manage to get it fixed?

 

[cmmabry]

not sure if this could help.... 2 years later lol

not sure if this applies but..... i'm trying to help others avoid my frustration
okay, i had the same message...did everything from reinstalling hardware to updating drivers to going through settings line by line

MY SWITCH WAS OFF
didn't know I even had one
some computers have a little button
mine was (Fn + F2) two keys simultaneously pressed...... not too intuitive

If there is a light on the keyboard that resembles a wifi symbol
ie ((*))
and it doesn't light up.....
look for some sort of button that could possibly turn on
look at the function keys and their alternate functions when Fn is pressed

The wifi off button drives me crazy

 

[gdeep28]

Okay--as a colleague just reminded me, IEEE 1394 is firewire--so the real problem here is
why isn't XP recognizing the onboard NIC in the new laptop? Any ideas?

Jerry Paquette wrote:
> About 10 days ago I had my laptop stolen (Acer Travelmate, 2000
> vintage). I've replaced it with a current Travelmate (800). I had a
> Ghost image of the old machine (XP Pro, retail license version, not OEM)
> and decided to try putting in on the new machine and doing an inplace
> hardward upgrade to avoid the misery of reconfiguring and reinstalling
> everything.
>
> Generally the process worked flawlessly. Unfortunately, however, the
> NIC (IEEE 1394) doesn't function with TCP/IP. The card connects but no
> packets are exchanged. Trying to "Repair" the connection results in an
> error saying "TCP/IP is not enabled for this connection. Cannot
> proceed." TCP/IP works fine on the (internal) wireless connection on
> the same machine. I use a linksys router so the IP numbers are supplied
> by the router
>
> I tried running netsh as described at:
> http://support.microsoft.com/defaul...port/kb/articles/Q299/3/57.ASP&NoWebContent=1
>
>
> It ran okay but didn't affect the problem. I've also tried removing the
> IEEE 1394 adapted in Device Manager and rebooting with no luck.
>
> ipconfig /all gives (the IEEE 1394 connection isn't even found):
>
> -------------------------------------
>
> Windows IP Configuration
>
>
> Host Name . . . . . . . . . . . . : machine_name
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
>
>
> Ethernet adapter Wireless Network Connection 2:
>
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless LAN
> 2100 3B Mini PCI Adapter
> Physical Address. . . . . . . . . : 00-04-23-4B-3E-23
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.102
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 129.100.2.12
>
> 129.100.74.79
> Lease Obtained. . . . . . . . . . : Sunday, July 13, 2003
> 3:25:35 PM
> Lease Expires . . . . . . . . . . : Monday, July 14, 2003
> 3:25:35 PM
>
> ------------------------------------------
> Does anyone have any idea what is going wrong here and how to fix it?
>
> Thanks in advance for any help on this!
>

There are Only 2 Problems
I think your DNS Servers or your DHCP Server to are not Correct