Hi!
Well, I just want to make sure about this:
I have a driver, that I load by demand.
It runs way after the system was loaded.
I want to map the x: drive to a place on the network,
and start the driver from this place.
Again - this happens AFTER all network connections are
up. Moreover - I tried it using Sun's Solstice (NFS), and
it worked. BUT, it didn't work when I mapped a network
driver with SMB.
Why does it happen?
Why am I not allowed to put a driver on the net?
Another clarification: This is not a device driver, it's
a simple network driver that listens on the network
(like the packet.sys driver from the DDK)
thanks in advance, and sorry for the trouble...
- Barak
"Roddy, Mark" wrote:
>
> To elaborate: NO!
>
> > -----Original Message-----
> > From: Jamey Kirby [mailto:
[email protected]]
> > Sent: Monday, April 24, 2000 12:18 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: putting a driver file on a shared network drive
> >
> >
> > No.
> >
> > > -----Original Message-----
> > > From:
[email protected]> > > [mailto:
[email protected]]On Behalf Of Barak
> > Mandelovich
> > > Sent: Monday, April 24, 2000 10:00 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] putting a driver file on a shared network drive
> > >
> > >
> > > Hi, everybody!
> > >
> > > I'd like to know if it is possible to register
> > > a driver in the kernel, where its path is
> > > a shared network drive (e.g.: x:\my_driver)
> > > where x: is a "net use x: \\server\sharename".
> > >
> > > I tried to do this, and the CreateFile returns
> > > a "file not found"....
> > >
> > > What am I doing wrong?
> > >
> > > thanks,
> > >
> > > - Barak
> > >
> > > --
> > > ----------------------------------------------------
> > > Barak Mandelovich Mercury Interactive ltd.
> > >
[email protected] 19 Shabazi st.
> > > Tel: +972 3 539 9286 Yehud, 56100
> > > Fax: +972 3 533 1617 Israel
> > > ----------------------------------------------------
> > >
> > >
> >
> > ---
> > You are currently subscribed to ntdev as:
[email protected]> > To unsubscribe send a blank email to $subst('Email.Unsub')
> >
>
> ---
> You are currently subscribed to ntdev as:
[email protected]> To unsubscribe send a blank email to $subst('Email.Unsub')
--
----------------------------------------------------
Barak Mandelovich Mercury Interactive ltd.
[email protected] 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel
----------------------------------------------------
Comments
local. Offhand I cannot think of a compelling reason why this policy is
implemented for anything other than boot and system start drivers. Perhaps
it has something to do with dependencies on protocol stacks/network drivers
and pagable images?
Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Barak Mandelovich
Sent: Thursday, April 27, 2000 6:20 AM
To: NT Developers Interest List
Subject: [ntdev] Clarification: RE: putting a driver file on a shared
network drive
Hi!
Well, I just want to make sure about this:
I have a driver, that I load by demand.
It runs way after the system was loaded.
I want to map the x: drive to a place on the network,
and start the driver from this place.
Again - this happens AFTER all network connections are
up. Moreover - I tried it using Sun's Solstice (NFS), and
it worked. BUT, it didn't work when I mapped a network
driver with SMB.
Why does it happen?
Why am I not allowed to put a driver on the net?
Another clarification: This is not a device driver, it's
a simple network driver that listens on the network
(like the packet.sys driver from the DDK)
thanks in advance, and sorry for the trouble...
- Barak
"Roddy, Mark" wrote:
>
> To elaborate: NO!
>
> > -----Original Message-----
> > From: Jamey Kirby [mailto:[email protected]]
> > Sent: Monday, April 24, 2000 12:18 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: putting a driver file on a shared network drive
> >
> >
> > No.
> >
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]]On Behalf Of Barak
> > Mandelovich
> > > Sent: Monday, April 24, 2000 10:00 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] putting a driver file on a shared network drive
> > >
> > >
> > > Hi, everybody!
> > >
> > > I'd like to know if it is possible to register
> > > a driver in the kernel, where its path is
> > > a shared network drive (e.g.: x:\my_driver)
> > > where x: is a "net use x: \\server\sharename".
> > >
> > > I tried to do this, and the CreateFile returns
> > > a "file not found"....
> > >
> > > What am I doing wrong?
> > >
> > > thanks,
> > >
> > > - Barak
> > >
> > > --
> > > ----------------------------------------------------
> > > Barak Mandelovich Mercury Interactive ltd.
> > > [email protected] 19 Shabazi st.
> > > Tel: +972 3 539 9286 Yehud, 56100
> > > Fax: +972 3 533 1617 Israel
> > > ----------------------------------------------------
> > >
> > >
> >
> > ---
> > You are currently subscribed to ntdev as: [email protected]
> > To unsubscribe send a blank email to $subst('Email.Unsub')
> >
>
> ---
> You are currently subscribed to ntdev as: [email protected]
> To unsubscribe send a blank email to $subst('Email.Unsub')
--
----------------------------------------------------
Barak Mandelovich Mercury Interactive ltd.
[email protected] 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel
----------------------------------------------------
> a driver in the kernel, where its path is
> a shared network drive (e.g.: x:\my_driver)
> where x: is a "net use x: file://\\server\sharename.
I don't think it's possible. The driver loader is a part of system process -
and it
cannot access the SMB shares due to security reasons.
Max
> Why am I not allowed to put a driver on the net?
Try:
a) path like \Device\LanmanRedirector\Server\Share\Path
AND
b) on the server, allow password-less guest access to this directory.
The driver loader works under LocalSystem, which does now knows any
passwords and thus unable to name them to the server.
Max