Accessing network files from W2K

Dear All!

I’ve encountered the following problem: if a file is shared on Win95/98 I cannot read it from the kernel in Win2K using UNC path.
If I map the UNC path as a drive I can read the same file from the network drive.
If a file is shared on WinNT I can read it using UNC path.

The same driver can read the shared file in WinNT independing on where the file is shared.

BTW, I use thread impersonation when reading the file. Does it matter?

Any ideas?

Regards,
Max Lyadvinsky

The proper way is to do the I/O in the context of a process that has access
rights to the network resource. I do this by creating a system thread in the
context of a known process (i.e. a service under NT/2000).

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Max Lyadvinsky
Sent: Thursday, April 06, 2000 9:56 AM
To: File Systems Developers
Subject: [ntfsd] Accessing network files from W2K

Dear All!

I’ve encountered the following problem: if a file is shared on
Win95/98 I cannot read it from the kernel in Win2K using UNC path.
If I map the UNC path as a drive I can read the same file from
the network drive.
If a file is shared on WinNT I can read it using UNC path.

The same driver can read the shared file in WinNT independing on
where the file is shared.

BTW, I use thread impersonation when reading the file. Does it matter?

Any ideas?

Regards,
Max Lyadvinsky


You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

A service runs in the context of the system process. So does my kernel thread.
I impersonate the known thread, that has access to the network. I don’t think it does matter whether I access the network from the thread I impersonate or from the system thread in which I impersonate. Maybe this is a W2K bug? The same code works fine under WinNT.


??: Jamey Kirby[SMTP:xxxxx@storagecraft.com]
???: File Systems Developers
???: 6 ??? 2000 ?. 21:33
???: File Systems Developers
???: [ntfsd] RE: Accessing network files from W2K

The proper way is to do the I/O in the context of a process that has access
rights to the network resource. I do this by creating a system thread in the
context of a known process (i.e. a service under NT/2000).

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Max Lyadvinsky
Sent: Thursday, April 06, 2000 9:56 AM
To: File Systems Developers
Subject: [ntfsd] Accessing network files from W2K

Dear All!

I’ve encountered the following problem: if a file is shared on
Win95/98 I cannot read it from the kernel in Win2K using UNC path.
If I map the UNC path as a drive I can read the same file from
the network drive.
If a file is shared on WinNT I can read it using UNC path.

The same driver can read the shared file in WinNT independing on
where the file is shared.

BTW, I use thread impersonation when reading the file. Does it matter?

Any ideas?

Regards,
Max Lyadvinsky


You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)


You are currently subscribed to ntfsd as: xxxxx@paragon.ru
To unsubscribe send a blank email to $subst(‘Email.Unsub’)