Unable to impersonate via a named pipe until data has been read from that pipe

G

Greg

Error 1368
Server not accessible
Unable to impersonate via a named pipe until data has been
read from that pipe.

Microsoft's support on this issue is poor:<

Client 2000 machines have periodic access to Server 2000
shared files. Reboot machines and leave alone for a while
and client 2000 machines have access to server 2000
again. Why? How do I permanently fix? Server 2000 is a
stand alone server sharing files. Clients access files
through the network neighborhood without a problem for
about a week. Then all of a sudden, no access for about 4
hours with the above error message. Help - Please???
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

network drive connections problem 1
user is unable to map drive 1
Problem on joining the Win2k Domain 2
XP file sharing problem 7
Win 2000 Adv Srv and Win NT 4.0 Workstation Access Issues 4
Problem Opening a Shared Folder 3
XP Pro to Win2K Domain connection problem 1
Slow initial access to shares on a Win2kS domain controller from WinXP clients 2

Top