The best way to do this is using Win32::Lanman and connecting to the IPC$ share of the server. The IPC$ share let's you establish a security token with the remote server, without limiting yourself to a particular share. Then you can test for the existence of that file using UNC paths.

An example:

use strict;
use Win32::Lanman;

my $result = Win32::Lanman::NetUseAdd({
    remote     => "\\\\yourserver\\ipc\$",
    password   => "yourpass",
    username   => "youruser",
    domain     => "yourdomain",
    asg_type   => &USE_IPC
});

if (! $result) {
    print "Sorry, something went wrong; error: ";
    print Win32::Lanman::GetLastError();
    exit 1;
}

#test for file existence
if (-e "\\\\yourserver\\c\$\\winnt\\system32\\myfile.dll") {
    print "File exists\n";
} else {
    print "File does not exist\n";
}

[download]

In reply to Re: Remote Win32 User by meetraz
in thread Remote Win32 User by nimdokk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.