XP2XP network connection broken at each reboot

[Philip]

Hi,

Hopefully someone out there can help :).

I have two XP machines (desktop/laptop) connected via firewire. I ran
the home network connection wizard to set them up. Everything works
great: network and internet. However, each time I reboot the laptop,
they don't see each other at all. I then run the wizard, and bam! It
works again. So each reboot required a rerun of the wizard. Is there
any way around this?

Thanks,
Phil

PS I saw some other posts on this, but they only dealt with XP-98
networks.

[Ken Wickes [MSFT]]

Do both machine have valid IP addresses after the reboot?

--

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


"Philip" > wrote in message
om...
> Hi,
>
> Hopefully someone out there can help :).
>
> I have two XP machines (desktop/laptop) connected via firewire. I ran
> the home network connection wizard to set them up. Everything works
> great: network and internet. However, each time I reboot the laptop,
> they don't see each other at all. I then run the wizard, and bam! It
> works again. So each reboot required a rerun of the wizard. Is there
> any way around this?
>
> Thanks,
> Phil
>
> PS I saw some other posts on this, but they only dealt with XP-98
> networks.

[Philip]

How do I check that? Assuming the laptop doesn't (its the only one I
reboot), how do I fix it to where it does?

Thanks!
Phil

"Ken Wickes [MSFT]" > wrote in message >...
> Do both machine have valid IP addresses after the reboot?
>
> --
>
> Ken Wickes [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Philip" > wrote in message
> om...
> > Hi,
> >
> > Hopefully someone out there can help :).
> >
> > I have two XP machines (desktop/laptop) connected via firewire. I ran
> > the home network connection wizard to set them up. Everything works
> > great: network and internet. However, each time I reboot the laptop,
> > they don't see each other at all. I then run the wizard, and bam! It
> > works again. So each reboot required a rerun of the wizard. Is there
> > any way around this?
> >
> > Thanks,
> > Phil
> >
> > PS I saw some other posts on this, but they only dealt with XP-98
> > networks.

[Philip]

Okay, did some checking and no, I'm not getting a valid IP address. I
get 0.0.0.0 After I rerun the network config wizard file from a disk,
boom, I get a valid IP and the network connects and everythings great!
Until I reboot again, and have to run the network wiz file again.
Anybody got any ideas?

Thanks!
Phil


(Philip) wrote in message >...
> How do I check that? Assuming the laptop doesn't (its the only one I
> reboot), how do I fix it to where it does?
>
> Thanks!
> Phil
>
> "Ken Wickes [MSFT]" > wrote in message >...
> > Do both machine have valid IP addresses after the reboot?
> >
> > --
> >
> > Ken Wickes [MSFT]
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "Philip" > wrote in message
> > om...
> > > Hi,
> > >
> > > Hopefully someone out there can help :).
> > >
> > > I have two XP machines (desktop/laptop) connected via firewire. I ran
> > > the home network connection wizard to set them up. Everything works
> > > great: network and internet. However, each time I reboot the laptop,
> > > they don't see each other at all. I then run the wizard, and bam! It
> > > works again. So each reboot required a rerun of the wizard. Is there
> > > any way around this?
> > >
> > > Thanks,
> > > Phil
> > >
> > > PS I saw some other posts on this, but they only dealt with XP-98
> > > networks.

[snowboarder04]

What protocols are you using for the firewire adapter?
Under the 1394 adapter (or bridge) properties there should only be the
following checked:

Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)

nothing else should be checked if there is anything else present.
I had a similar problem, only it raised it head when i was transferring
a large amount of data between the two machines, and it turned out
after an awful lot of tweaking that the problem was that i had "QoS
Packet Scheduler" checked under the protocols.

Hope this helps!


snowboarder04
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message263058.html

[allie]

I need help on the correct way of sharing and setup of normal windows 98
network with one xphome laptop connected to the 98 computers. It is
already connected , but the xp machine keeps on throwing itself off the
network. If I ping an ip address from XP Laptop then there is a reply,
but I can't get access from or to the laptop with xphome. I configured
a windows 2000 laptop on the same way and it is very stable. What is
the problem with Windows XP -HOME Edition????
I never had such problems with the other operating systems including
2000. Maybe there is something in xphome that is not configured
correctly. The cabeling and everything is already checked. 2000 works
fine on this network, but Xphome is not working constantly.

I hope somebody can help me.

Thankyou in advance


allie
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message263058.html

[Philip]

I only have those 3 protocols checked (only those are available). My
problem is after every reboot of the laptop, I have to run the network
setup disk to make it work again. At least that's the only way I know
to make it work again.

Thanks,
Phil

snowboarder04 > wrote in message >...
> What protocols are you using for the firewire adapter?
> Under the 1394 adapter (or bridge) properties there should only be the
> following checked:
>
> Client for Microsoft Networks
> File and Printer Sharing for Microsoft Networks
> Internet Protocol (TCP/IP)
>
> nothing else should be checked if there is anything else present.
> I had a similar problem, only it raised it head when i was transferring
> a large amount of data between the two machines, and it turned out
> after an awful lot of tweaking that the problem was that i had "QoS
> Packet Scheduler" checked under the protocols.
>
> Hope this helps!
>
>
> snowboarder04
> ------------------------------------------------------------------------
> Posted via http://www.mcse.ms
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message263058.html