Andrew writes:

> Completely off the 3000 but this site spoils you when looking for help.
>
> I've tried the so called various PC discussion groups but no one wants to
> know (shame I hear you say) so I thought there might be some kind soul out
> there who might have a few clues.
>
> I've a SBS2003 server with one external and one internal card. Several XP
> boxes (as well as the 3k) hooked up to the (so called) network on my
> internal network.
>
> On booting one of these XP's and logging onto the domain I can access the
> shares but approx after three hours they drop off with 'clinetpc cannot be
> accessed network path cannot be found' type of message. All the net views
> etc show the PCs but I cannot get into them. Its strange after three hours
> so I think it must be either something expiring or something failing to re-
> register.
>
> has anyone experienced this in their office and/or provide any clues as to
> where to start (i.e. any good discussion groups out there) to an old HP
> hack who had enough trouble with the 3k let alone this microsoft malarkey.

Have you checked MS support web? I used the phrase "network path cannot
be found" under Win 2003 and found quite a few documents. The first one in the
list seems to describe something similar to your problem although it describes
an 8 second timeout. But maybe it will provide some leads. The article is titled:

'You may receive a “The network name cannot be found” error message when you
use the fully qualified domain name to connect to a remote computer on a
Windows Server 2003-based domain controller'  (article ID 875441)

One solution to this was to use regedit to change the "LmhostsTimeout" registry
entry. The other was installing IPv6.

hth,

Bill
hp/vCSY
===========================================
  Reply to: bill . vcsy -at- comcast . net
===========================================

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *