M
Martin
Sirs,
I have a Packard Bell C3223 Notebook. It comes with
Windows XP Home pre-installed. Built into the notebook is
a 1394 Firewire port which Windows XP Device Manager says
is working correctly (so is the OHCI driver that goes with
it). In setting this up as a Network device, I have given
it a valid IP address and then tried to ping it (pinging
itself, not going across the network). The requests time
out saying "Destination Host Unreachable". There is no
firewall setup and no routes get created. I started up the
Network Diagnostic Tools (under the Tools menu in winmsd)
and it says that "IPEnabled = FALSE" for the 1394 card.
1) Why?
2) Under what conditions is this flag set to False?
3) Is this information logged anywhere in windows?
4) Is there any debugging support for this setup so that I
can determine why IPEnabled is set to False for this card?
5) How do I enable it?
I have trawled through the registry for settings for this
card without success. My other network cards (the built in
one and the wireless one) both work fine, so it is not the
TCP/IP stack, it must be something more specific to the
1394 card.
It might interest everyone to know that my firewire
connection on my Linux machine works well and took about
1/2 to setup (that is by editing files not using any GUIs).
Please advise as I am sure it is simply my ignorance of XP
and not XP itself that is the problem.
Many thanks,
Martin
I have a Packard Bell C3223 Notebook. It comes with
Windows XP Home pre-installed. Built into the notebook is
a 1394 Firewire port which Windows XP Device Manager says
is working correctly (so is the OHCI driver that goes with
it). In setting this up as a Network device, I have given
it a valid IP address and then tried to ping it (pinging
itself, not going across the network). The requests time
out saying "Destination Host Unreachable". There is no
firewall setup and no routes get created. I started up the
Network Diagnostic Tools (under the Tools menu in winmsd)
and it says that "IPEnabled = FALSE" for the 1394 card.
1) Why?
2) Under what conditions is this flag set to False?
3) Is this information logged anywhere in windows?
4) Is there any debugging support for this setup so that I
can determine why IPEnabled is set to False for this card?
5) How do I enable it?
I have trawled through the registry for settings for this
card without success. My other network cards (the built in
one and the wireless one) both work fine, so it is not the
TCP/IP stack, it must be something more specific to the
1394 card.
It might interest everyone to know that my firewire
connection on my Linux machine works well and took about
1/2 to setup (that is by editing files not using any GUIs).
Please advise as I am sure it is simply my ignorance of XP
and not XP itself that is the problem.
Many thanks,
Martin