Firewire network driver?

Archived from groups: microsoft.public.windbg,microsoft.public.windowsxp.hardware (More info?)

The 1394 NIC will not show up via ipconfig until there is another node on
the bus. From that point on it will show up until it is disabled or you
reboot. If you reboot with no cable attached, the NIC will again not show
up via ipconfig. At least that is my experience. If it is connected and
then you unplug the 1394 cable the NIC will show up but will show media
disconnected via ipconfig.

It sounds like you have a hardware problem if you cannot setup a network
connection between the two 1394 cards.

Bill M.

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:1B2CC48D-9229-43DF-85F4-8167F4621F8D@microsoft.com...
> Dear firewire experts,
>
> I've just received my first 1394 cards. The goal is running windbg over
> firewire.
> One card is a cardbus, another one PCI.
> XP auto detected them and installed in-box drivers.
> Windbg connection, of course, did not work (yes I've read the manual).
> Now am trying to get the LAN over 1394 working to verify that cards
> and cables are ok. This doesn't work as well.
>
> A DVD in a firewire enclosure works well with the cardbus card,
> so I assume it and the cable are ok.
>
> But... whether or not the cable is *not* attached, the 1394 LAN connection
> still appears connected and online - no cable disconnected message.
> I can open the LAN connection properties, assign IP address and so on.
> But ipconfig /all does not list 1394 connections at all - as if they don't
> exist.
> Is this normal?
>
> The same behavior is on XP SP1, SP2 and Win2k SP4.
>
> -- Pavel
>

Archived from groups: microsoft.public.windbg,microsoft.public.windowsxp.hardware (More info?)

Thanks

"Bill McKenzie" wrote:
> The 1394 NIC will not show up via ipconfig until there is another node on
> the bus. From that point on it will show up until it is disabled or you
> reboot. If you reboot with no cable attached, the NIC will again not show
> up via ipconfig. At least that is my experience. If it is connected and
> then you unplug the 1394 cable the NIC will show up but will show media
> disconnected via ipconfig.
>
> It sounds like you have a hardware problem if you cannot setup a network
> connection between the two 1394 cards.
>
> Bill M.
>
> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
> news:1B2CC48D-9229-43DF-85F4-8167F4621F8D@microsoft.com...
> > Dear firewire experts,
> >
> > I've just received my first 1394 cards. The goal is running windbg over
> > firewire.
> > One card is a cardbus, another one PCI.
> > XP auto detected them and installed in-box drivers.
> > Windbg connection, of course, did not work (yes I've read the manual).
> > Now am trying to get the LAN over 1394 working to verify that cards
> > and cables are ok. This doesn't work as well.
> >
> > A DVD in a firewire enclosure works well with the cardbus card,
> > so I assume it and the cable are ok.
> >
> > But... whether or not the cable is *not* attached, the 1394 LAN connection
> > still appears connected and online - no cable disconnected message.
> > I can open the LAN connection properties, assign IP address and so on.
> > But ipconfig /all does not list 1394 connections at all - as if they don't
> > exist.
> > Is this normal?
> >
> > The same behavior is on XP SP1, SP2 and Win2k SP4.
> >
> > -- Pavel
> >

Archived from groups: microsoft.public.windbg,microsoft.public.windowsxp.hardware (More info?)

The non-working PCI card fixed. It has an internal power connector that
must be powered. Otherwice it will perfectly appear in device manager
but won't work.
Moral: I will always fix my computers myself, leave nothing to the techs  

--PA

> "Bill McKenzie" wrote:
> > The 1394 NIC will not show up via ipconfig until there is another node on
> > the bus. From that point on it will show up until it is disabled or you
> > reboot. If you reboot with no cable attached, the NIC will again not show
> > up via ipconfig. At least that is my experience. If it is connected and
> > then you unplug the 1394 cable the NIC will show up but will show media
> > disconnected via ipconfig.
> >
> > It sounds like you have a hardware problem if you cannot setup a network
> > connection between the two 1394 cards.
> >
> > Bill M.
> >
> > "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
> > news:1B2CC48D-9229-43DF-85F4-8167F4621F8D@microsoft.com...
> > > Dear firewire experts,
> > >
> > > I've just received my first 1394 cards. The goal is running windbg over
> > > firewire.
> > > One card is a cardbus, another one PCI.
> > > XP auto detected them and installed in-box drivers.
> > > Windbg connection, of course, did not work (yes I've read the manual).
> > > Now am trying to get the LAN over 1394 working to verify that cards
> > > and cables are ok. This doesn't work as well.
> > >
> > > A DVD in a firewire enclosure works well with the cardbus card,
> > > so I assume it and the cable are ok.
> > >
> > > But... whether or not the cable is *not* attached, the 1394 LAN connection
> > > still appears connected and online - no cable disconnected message.
> > > I can open the LAN connection properties, assign IP address and so on.
> > > But ipconfig /all does not list 1394 connections at all - as if they don't
> > > exist.
> > > Is this normal?
> > >
> > > The same behavior is on XP SP1, SP2 and Win2k SP4.
> > >
> > > -- Pavel