"BKTMX" wrote:

>     We have a new desktop computer that has been added to a workgroup LAN (peer
> to peer) which does not stay visible to the other computers. The original 5
> units on the LAN have been functioning normally with all appropriate network
> places always accessible. The new unit will become visible in the workgroup
> (or in "net view") only after rebooting it or after virtually unplugging &
> reconnecting the network card such as by running diagnostics on the card. The
> computer will usually disappear from the workgroup after 1/2 hr. - 2hrs,
> although it stayed visible once for several days.The shares on this server
> stay visible to the network longer but will eventually disappear also.  The
> new unit functions otherwise normally on the network in that it sees and can
> access all other network places that are available on the network.
>     The new unit, once it disappears, does not see itself on the network,
> either. It is not counted as a server in 'browstat status'. It is not visible
> to 'net view' but the shares from it show to the 'net view \\Computername'
> command.
>     All six computers have Windows XP Pro. The 5 original computers have SP1
> and the new unit has SP2.
>     The energy saving settings have been turned off on the new unit's network
> card.
>     The missing computer can always be found using "Search" from the Start menu
> or windows explorer and searching for it by the computer name.
>     No error messages have been displayed and no errors have appeared in the
> event viewer of the new unit relating to this problem.
>     The Windows firewall and the McAffee firewall on the new unit have both
> been disabled.
>
>     We need to solve this problem and and additional background information on
> the problem will be cheerfully provided.
>

"BKTMX" wrote:

>     We have a new desktop computer that has been added to a workgroup LAN (peer
> to peer) which does not stay visible to the other computers. The original 5
> units on the LAN have been functioning normally with all appropriate network
> places always accessible. The new unit will become visible in the workgroup
> (or in "net view") only after rebooting it or after virtually unplugging &
> reconnecting the network card such as by running diagnostics on the card. The
> computer will usually disappear from the workgroup after 1/2 hr. - 2hrs,
> although it stayed visible once for several days.The shares on this server
> stay visible to the network longer but will eventually disappear also.  The
> new unit functions otherwise normally on the network in that it sees and can
> access all other network places that are available on the network.
>     The new unit, once it disappears, does not see itself on the network,
> either. It is not counted as a server in 'browstat status'. It is not visible
> to 'net view' but the shares from it show to the 'net view \\Computername'
> command.
>     All six computers have Windows XP Pro. The 5 original computers have SP1
> and the new unit has SP2.
>     The energy saving settings have been turned off on the new unit's network
> card.
>     The missing computer can always be found using "Search" from the Start menu
> or windows explorer and searching for it by the computer name.
>     No error messages have been displayed and no errors have appeared in the
> event viewer of the new unit relating to this problem.
>     The Windows firewall and the McAffee firewall on the new unit have both
> been disabled.
>
>     We need to solve this problem and and additional background information on
> the problem will be cheerfully provided.
>

"vinc_sixx" wrote:

> BKTMX,
> i can see one possible solution to your reoccuring problem. That the NIC may
> possible be bad. Although it may be new it can still be bad. You can try to
> install another NIC to see if that corrects the problem.
> Good luck.
>
> "BKTMX" wrote:
>
> >     We have a new desktop computer that has been added to a workgroup LAN (peer
> > to peer) which does not stay visible to the other computers. The original 5
> > units on the LAN have been functioning normally with all appropriate network
> > places always accessible. The new unit will become visible in the workgroup
> > (or in "net view") only after rebooting it or after virtually unplugging &
> > reconnecting the network card such as by running diagnostics on the card. The
> > computer will usually disappear from the workgroup after 1/2 hr. - 2hrs,
> > although it stayed visible once for several days.The shares on this server
> > stay visible to the network longer but will eventually disappear also.  The
> > new unit functions otherwise normally on the network in that it sees and can
> > access all other network places that are available on the network.
> >     The new unit, once it disappears, does not see itself on the network,
> > either. It is not counted as a server in 'browstat status'. It is not visible
> > to 'net view' but the shares from it show to the 'net view \\Computername'
> > command.
> >     All six computers have Windows XP Pro. The 5 original computers have SP1
> > and the new unit has SP2.
> >     The energy saving settings have been turned off on the new unit's network
> > card.
> >     The missing computer can always be found using "Search" from the Start menu
> > or windows explorer and searching for it by the computer name.
> >     No error messages have been displayed and no errors have appeared in the
> > event viewer of the new unit relating to this problem.
> >     The Windows firewall and the McAffee firewall on the new unit have both
> > been disabled.
> >
> >     We need to solve this problem and and additional background information on
> > the problem will be cheerfully provided.
> >

"Bob Campbell" wrote:

> I agree. I had a client who had a computer with similar symptoms. It seemed
> to me that the network card was overheating and failing. Well, the computer
> was under a hot light in a small enclosed space. I put it in a open space
> with space under it, and it stopped failing. It seems so obvious now.
>
> --
> The Software Tailor
> Las Vegas USA
>
>
> "vinc_sixx" wrote:
>
> > BKTMX,
> > i can see one possible solution to your reoccuring problem. That the NIC may
> > possible be bad. Although it may be new it can still be bad. You can try to
> > install another NIC to see if that corrects the problem.
> > Good luck.
> >
> > "BKTMX" wrote:
> >
> > >     We have a new desktop computer that has been added to a workgroup LAN (peer
> > > to peer) which does not stay visible to the other computers. The original 5
> > > units on the LAN have been functioning normally with all appropriate network
> > > places always accessible. The new unit will become visible in the workgroup
> > > (or in "net view") only after rebooting it or after virtually unplugging &
> > > reconnecting the network card such as by running diagnostics on the card. The
> > > computer will usually disappear from the workgroup after 1/2 hr. - 2hrs,
> > > although it stayed visible once for several days.The shares on this server
> > > stay visible to the network longer but will eventually disappear also.  The
> > > new unit functions otherwise normally on the network in that it sees and can
> > > access all other network places that are available on the network.
> > >     The new unit, once it disappears, does not see itself on the network,
> > > either. It is not counted as a server in 'browstat status'. It is not visible
> > > to 'net view' but the shares from it show to the 'net view \\Computername'
> > > command.
> > >     All six computers have Windows XP Pro. The 5 original computers have SP1
> > > and the new unit has SP2.
> > >     The energy saving settings have been turned off on the new unit's network
> > > card.
> > >     The missing computer can always be found using "Search" from the Start menu
> > > or windows explorer and searching for it by the computer name.
> > >     No error messages have been displayed and no errors have appeared in the
> > > event viewer of the new unit relating to this problem.
> > >     The Windows firewall and the McAffee firewall on the new unit have both
> > > been disabled.
> > >
> > >     We need to solve this problem and and additional background information on
> > > the problem will be cheerfully provided.
> > >