pipes instances busy

June 22, 2011 at 10:30:38
Specs: Windows XP
No longer able to map drives. Using Win 2003 cannot map between server and external storage, and, unable to map networked pc's to networked drives (on the external storage device, buffalo terastation). This worked well before, but after replacing server box, now get this message: all pipe instances busy.

See More: pipes instances busy

Report •

#1
June 22, 2011 at 13:40:08
what exactly do you mean "but after replacing server box"?
you running active directory or a workgroup?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
June 22, 2011 at 14:38:38
Active Directory. The server (hardware) had to be replaced. Everything mirrored or re-installed.
We had had drives mapped: from PC's to shares on the Terastation, which was itself mapped to the Windows 2003 R2 server. PC - Server - External Storage Device.
Although we had mapped drives before, without problems, since the new hardware, mappings have been a problem. A while ago, we were able, by using the IP, to map some drives, intermittedly. (Sometimes it worked, mostly not) But right now, mapping can not be done to any PC or even between the server and storage device (Buffalo Terastation). We do not know what/anything changed.
I have tried both thru wizard off 'tools' and via command line, and by using either names or ip address.
The message we usually get is that
all pipe instances are busy.
Or, cannot find network.
Or, no logon server running.

Is there a limit to how many drives can be connected? We have 25 PCs and would have 0 - 3 mapped network drives on each, and one with 12 mapped drives. About 8 mapped drives are still working now.


Report •

#3
June 22, 2011 at 20:25:47
When you replace a server that is only half of the network configuration.

You have to rejoin all the pcs to the new [even if same name] domain
You have to recreate all users/groups
You have to remap all drives, etc

You are in effect building a completely new network. This is why its recommended to:
have a second dc
have a second dns server
have good backups which include system state.

Who setup the new hardware and installed the server?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •


Ask Question