TCP/IP will not bind to 1394 Adapter

[Jim C]

I have a XP Home laptop communicating through a netgear
802.11b router to a DSL connection. Although I had
wireless connectivity, I was unable to establish a dial-
up connection, until I executed Ken's instructions on
uninstalling McAfee firewall, and deleting the winsock
and winsock2 registry keys. After rebooting and
reinstalling tcpip (then rebooting again), both wireless
and dial-up connections worked fine. I was so relieved
because I had been struggling with this a long time.

Next day, we had a power outage, and my battery was
completely drained. Upon reboot, I had lost wireless
connectivity. Tried to use the repair function in
network connections on the 1394 interface, but XP was
unable to resolve problem, returning the message: "tcpip
not enabled for this device". I then tried removing and
reinstalling winsock and winsock2 from the registries
again, but still no tcpip over 1394. Also tried
uninstalling all network devices, and re-installing the
registries. Still no workie.

My modem, LAN and wireless cards are all propely bound to
tcpip. Can I presume there is another registry key that
is interfering with tcpip being bound to 1394? What is
the fix?

Jim Campbell

 

[Guest]

you cannot bind to 1394 as it's a firewire connection and
should not need to

 

[Ken Wickes [MSFT]]

Does it show as bound in the 1394 connection's properties?

Do you really use TCP/IP over 1394?

 

[Quaoar]

I have a XP Home laptop communicating through a netgear
802.11b router to a DSL connection. Although I had
wireless connectivity, I was unable to establish a dial-
up connection, until I executed Ken's instructions on
uninstalling McAfee firewall, and deleting the winsock
and winsock2 registry keys. After rebooting and
reinstalling tcpip (then rebooting again), both wireless
and dial-up connections worked fine. I was so relieved
because I had been struggling with this a long time.

Next day, we had a power outage, and my battery was
completely drained. Upon reboot, I had lost wireless
connectivity. Tried to use the repair function in
network connections on the 1394 interface, but XP was
unable to resolve problem, returning the message: "tcpip
not enabled for this device". I then tried removing and
reinstalling winsock and winsock2 from the registries
again, but still no tcpip over 1394. Also tried
uninstalling all network devices, and re-installing the
registries. Still no workie.

My modem, LAN and wireless cards are all propely bound to
tcpip. Can I presume there is another registry key that
is interfering with tcpip being bound to 1394? What is
the fix?

Jim Campbell

Wireless is not Firewire, 1394 network adapter. It can safely be
disabled unless you are really using it, which I doubt.

Since there was a power failure, try shutting down the computer and
router. Power cycle the modem, leaving it off for a minute or two.
Restart the modem, and when it has finished booting, repower the router,
then boot your computer. If all goes well, the wireless should come
right up. If not, then check the wireless adapter properties and see if
there is a mangled SSID or WEP passphase there. If so, remove or fix
the entries. Then right Repair the wireless connection.

Q

 

[Jim C]

1394 properties indicate tcpip is bound to the device.
I do not know if 1394 is needed for the wireless adapter
connection, however, wireless is not working now on this
computer. I know the router and modem are working
because there is another computer connected to our home
network which can use the wireless router/modem just
fine. Tried removing and reinstalling adapter drivers
again so PPOe could find them. It found them all except
now the LAN card will not work, and it does not show up
in the system tray, but the network connections folder
shows it is installed and working with tcpip bound to it.

I have also tried restoring back to my original
configuration before I removed McAfee firewall (so I
could repeat the process you described). That did not
work either, so now I have no wireless and no LAN
functionality, just dial-up.

BTW: SP1 is installed with all security updates.

-----Original Message-----
Does it show as bound in the 1394 connection's properties?

Do you really use TCP/IP over 1394?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I have a XP Home laptop communicating through a netgear
802.11b router to a DSL connection. Although I had
wireless connectivity, I was unable to establish a dial-
up connection, until I executed Ken's instructions on
uninstalling McAfee firewall, and deleting the winsock
and winsock2 registry keys. After rebooting and
reinstalling tcpip (then rebooting again), both wireless
and dial-up connections worked fine. I was so relieved
because I had been struggling with this a long time.

Next day, we had a power outage, and my battery was
completely drained. Upon reboot, I had lost wireless
connectivity. Tried to use the repair function in
network connections on the 1394 interface, but XP was
unable to resolve problem, returning the message: "tcpip
not enabled for this device". I then tried removing and
reinstalling winsock and winsock2 from the registries
again, but still no tcpip over 1394. Also tried
uninstalling all network devices, and re-installing the
registries. Still no workie.

My modem, LAN and wireless cards are all propely bound to
tcpip. Can I presume there is another registry key that
is interfering with tcpip being bound to 1394? What is
the fix?

Jim Campbell

.

 

[Jim C]

Quaoar,
Thanks for the help. I did not know 1394 had no relation
to the wireless connection, but I thought it did because
device properties show tcpip is bound to it. In any
case, since its not relevant to wireless, it should not
be causing the problem? I would not know how to unmangle
a mangeled SSID or WEP passphase. Our network is not wep
enabled. modem and router working fine as proven by the
other computer connected wirelessly to the network. I
also, now cannot see my LAN adapter in the system tray,
but network folder shows it is installed, working
properly, and is bound to tcpip. Router assigns it an
address, and a different address to the wireless adapter,
but neither device can get communicate past the modem. I
can ping loopback and addresses on the LAN, but not
outside the LAN.

 

[Steve Winograd [MVP]]

you cannot bind to 1394 as it's a firewire connection and
should not need to

Yes, you can. Windows XP supports networking over a FireWire
connection. I have a FireWire network connection using TCP/IP between
two of my computers. I use it because it transfers data much faster
than an Ethernet connection.
--
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