Can DirMon process files on Remote Drives?

TheThumper · #1 05-11-2006, 09:25 AM

I am still using the "older" version of DirMon and was wondering if it is possible to process files on Drives located on other machines. When I select to add a directory it allows me to navigate across my Network and select a drive, but when it processes files the log indicates that it is only checking my local drive (which I also added as a drive to process) and nothing else.

Any help would be appreciated!

Thump

digitalgm · #2 05-11-2006, 10:01 AM

If you have a network drive mapped to a drive letter DirMon should really not care since it appears as a local drive. I could be wrong though. In any case, I use DirMon2 to run ShowAnalyzer on a network drive and it works fine.

TheThumper · #3 05-11-2006, 01:46 PM

Mapping a drive appears to have done the trick. I should have thought of that. Thanks for helping me out!

Thump

digitalgm · #4 05-11-2006, 02:20 PM

Quote:

Originally Posted by TheThumper

Mapping a drive appears to have done the trick. I should have thought of that. Thanks for helping me out!

Thump

My pleasure... Glad I could have been of service.

blade · #5 05-11-2006, 04:12 PM

Works fine for me with UNC paths also.

TheThumper · #6 05-12-2006, 07:53 AM

Well that is weird then as I wasn't having any luck with the UNC paths. Is this with DirMon or DirMon2? I am using DirMon still.

dflachbart · #7 05-12-2006, 07:55 AM

Quote:

Originally Posted by TheThumper

Well that is weird then as I wasn't having any luck with the UNC paths. Is this with DirMon or DirMon2? I am using DirMon still.

UNC paths didn't work for me in DirMon either, once I upgraded to DirMon2 it was fine ...

Dirk

digitalgm · #8 05-12-2006, 07:58 AM

There was one issue I forgot to mention about using mapped drives that may be a hindrence for you. As I remember it, mapped drives are based on the user not the system which means they are connected at login (IIRC). This means that anything running as a service will not be able to access that mapped drive until the user who mapped it is logged in. If I got this wrong, please correct me.

blade · #9 05-12-2006, 11:03 AM

Oops, I am running Dirmon2.

You need to upgrade anyway if you have more than 1 capture card because it supports processing multiple shows at once.

TheThumper · #10 05-12-2006, 11:14 AM

I was going to upgrade, but I heard there was a little trouble with it and running ComSkip (something about not being able to find the ini file that went with ComSkip. So I have been holding off for a bit.

blade · #11 05-12-2006, 12:25 PM

Quote:

Originally Posted by TheThumper

I was going to upgrade, but I heard there was a little trouble with it and running ComSkip (something about not being able to find the ini file that went with ComSkip. So I have been holding off for a bit.

I just dropped my comskip.ini in the system32 folder and it works fine. Has worked for everyone else that has tried it as far as I know. You can also place a copy in each of your recording directories. Seems like there is a parameter you can add at startup as well that will fix the problem.

dflachbart · #12 05-12-2006, 12:55 PM

Quote:

Originally Posted by blade

I just dropped my comskip.ini in the system32 folder and it works fine. Has worked for everyone else that has tried it as far as I know. You can also place a copy in each of your recording directories. Seems like there is a parameter you can add at startup as well that will fix the problem.

Yep, at the time when I used comskip the parameter solution worked fine too ...

Dirk

wbarber69 · #13 02-11-2007, 05:05 PM

I'm using dirmon2 to access unc paths or mapped drives but I'm unable to get it to actually scan the drives or do anthing to the networked drives at all, it works perfectly though on local drives

AndyS · #14 02-13-2007, 01:05 AM

Quote:

Originally Posted by wbarber69

I'm using dirmon2 to access unc paths or mapped drives but I'm unable to get it to actually scan the drives or do anthing to the networked drives at all, it works perfectly though on local drives

Make sure you're running the Dirmon2 service with a 'real' userid that has enough permission to access network shares. The 'System' userid is not allowed to do this....

Andy.

nyplayer · #15 02-13-2007, 08:20 AM

Quote:

Originally Posted by wbarber69

I'm using dirmon2 to access unc paths or mapped drives but I'm unable to get it to actually scan the drives or do anthing to the networked drives at all, it works perfectly though on local drives

Dirmon does not handle mapped drives at all. It can handle them by using the UNC name for example.

Mapped drive is M:\

In Dirmon in the "Where directories" box you would have to put in the whole UNC named for this ex: it would be \\servername\m$\recordedtv

Here is my setup

Sage server Recording directories
m:\sagem
n:\sagen
o:\sageo

Client mapped drives
m:\ mapped name \\myserver\m$
n:\ mapped name \\myserver\n$
o:\ mapped name \\myserver\o$

Dirmon on my server looks at ]
m:\sagem
n:\sagen
o:\sageo

Dirmon on my client looks at
\\myserver\m$\sagem
\\myserver\n$\sagen
\\myserver\o$\sageo

Ken C · #16 02-13-2007, 08:38 AM

An alternate way is to install DirMon, along with ShowAnalyzer, on the other machine.

When I first added a server with several hard drives, Sage recorded to it constantly until all the drives were equally used. Had DirMon and ShowAnalyzer only run on the main machine and accessed the server via the LAN, things would get really busy. It just made sense to install them locally.

Ken C

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)