How to react on \IPC$\srvsvc

NTFSD
1

Hi,

my network redirector driver sometime receives as root \IPC$ and rest of name \srvsvc.
What does it stands for, what return value fits best ?
Now i reuturn STATUS_BAD_NETWORK_NAME, but Windows interprets this as an connection error…
Anyone knows what to do ?

rihal

2

xxxxx@thinprint.com wrote:

Hi,

my network redirector driver sometime receives as root \IPC$ and rest of name \srvsvc.
What does it stands for, what return value fits best ?
Now i reuturn STATUS_BAD_NETWORK_NAME, but Windows interprets this as an connection error…
Anyone knows what to do ?

There is an entire protocol for handling requests to the server service
pipe. If you allow these opens, they will be followed by reads, writes
and fs controls which perform things like enumerate shares on the
server, etc.

Pete

–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

3

> my network redirector driver sometime receives as root \IPC$ and rest of name \srvsvc.

What does it stands for, what return value fits best ?

SMB server’s remote administration endpoints.

I think IPC$ is used for NetShareEnum.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

4

>There is an entire protocol for handling requests to the server service pipe. If you allow these opens, >they will be followed by reads, writes and fs controls which perform things like enumerate shares on >the server, etc.

And how can i disallow these opens?
If i run the driver on Windows Server 2003 i can list content in microsoft explorer, returning STATUS_BAD_NETWORK_NAME on IPC$ requests and everthing works fine. I get the content of my remote storage.
BUT if i try to list content in epxlorer on Windows Server 2008 i get the error ‘The network path was not found’ and i also return STATUS_BAD_NETWORK_NAME on IPC$ requests…
What is the difference between 2003 and 2008 ?

5

xxxxx@thinprint.com wrote:

> There is an entire protocol for handling requests to the server service pipe. If you allow these opens, >they will be followed by reads, writes and fs controls which perform things like enumerate shares on >the server, etc.

And how can i disallow these opens?
If i run the driver on Windows Server 2003 i can list content in microsoft explorer, returning STATUS_BAD_NETWORK_NAME on IPC$ requests and everthing works fine. I get the content of my remote storage.
BUT if i try to list content in epxlorer on Windows Server 2008 i get the error ‘The network path was not found’ and i also return STATUS_BAD_NETWORK_NAME on IPC$ requests…
What is the difference between 2003 and 2008 ?

In my experience, the ipc$ srvsvc interface only came into play for the
‘net’ commands such as running the ‘net view \server’ command. I would
check that there is not some other request failing or not being handled
correctly on Server '08 which is causing this path to be followed.

Pete

–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295