ERROR Watching Mapped drive

Hi There,

i have an application which watches mapped drive events using
FilsSystem Watcher .
the filters i am using are these : NotifyFilters.FileName |
NotifyFilters.Attributes | NotifyFilters.Size |
NotifyFilters.LastWrite

now when there are too many file creation in the mapped drive , i am
getting an error from filesystem watcher
which states like this :"the network bios command limit has been
reached " .

i increased the watcher internal buffer size but ,it did not help .

i searched on the web to find one KB article() but wasn't useful.

everything i am doing is on windows-xp machines .

any help/comments/suggestion are highly appreciated .

Hope am Clear

Regards
Dee

Michael
Thu May 08 20:49:16 CDT 2008

You aren't by any chance running your watcher on an XP system? There is a
known and documented limitation in XP with the network bios command limits.

Mike.

"deepak" <tsdeepak@gmail.com> wrote in message
news:b1bb20e9-0efb-42c5-aa58-85ca3deb46cf@b5g2000pri.googlegroups.com...
> Hi There,
>
> i have an application which watches mapped drive events using
> FilsSystem Watcher .
> the filters i am using are these : NotifyFilters.FileName |
> NotifyFilters.Attributes | NotifyFilters.Size |
> NotifyFilters.LastWrite
>
> now when there are too many file creation in the mapped drive , i am
> getting an error from filesystem watcher
> which states like this :"the network bios command limit has been
> reached " .
>
> i increased the watcher internal buffer size but ,it did not help .
>
> i searched on the web to find one KB article() but wasn't useful.
>
> everything i am doing is on windows-xp machines .
>
> any help/comments/suggestion are highly appreciated .
>
> Hope am Clear
>
> Regards
> Dee
>

deepak
Mon May 12 10:44:40 CDT 2008


Hi Mike ,

Thanks for our response, probably thats the case ,when i host my app
in windows-xp ,i am getting the error("Network bois ......").
i tried hosting my app in windows server 2k3 ,now that error ("Network
bios .. ..") is eliminated. but i am getting one more error now ,it
states "Too many changes to drive V: ". i understand this is because
there is too many file creates and deletes happening .
i have set InternalBufferSize to 64kb and i guess i cannot go beyond
64kb .

could you suggest/comment any ways in which i can go away with this
problem.

Thanks for your time

Cheers
Dee

deepak
Wed May 14 01:58:27 CDT 2008


The error "Too many changes to drive V: " is eliminated buy increasing
the buffer size .
increasing buffer only works when the watcher is on win 2k3
machine.

mike ,can you point me to the documentation of win-xp which mentions
about limitation with the network bios command limits.

Michael
Wed May 14 23:07:06 CDT 2008

"deepak" <tsdeepak@gmail.com> wrote in message
news:4a6de945-1292-429a-ac91-bea9df9a0a92@b5g2000pri.googlegroups.com...
>
> The error "Too many changes to drive V: " is eliminated buy increasing
> the buffer size .
> increasing buffer only works when the watcher is on win 2k3
> machine.
>
> mike ,can you point me to the documentation of win-xp which mentions
> about limitation with the network bios command limits.
>

Enter the exact text you get into Google and search for the technet article
in the results. That's how I found it a couple of years ago.

Mike.