Announcement Banner

tunibbles

updated

12 years ago

T

tunibbles

6 Posts

0

1400

February 18th, 2015 06:00

vnx emulator and cava

Hi,

i'm trying to learn something about the cava antivirus solution for vnx systems.

I downloaded the vnx simulator, created a global cifs server (gcifs.domain.local) and a vdm (vdm2.domain.local)

i also setup a windows server to install the event enabler and our antivirus (mcafee 8.8).

now i can start viruschk on the vnx and i get:

-----------------------------------------------------------------

server_2 :

10 threads started.

1 Checker IP Address(es):

172.17.100.48                                  ERROR_AUTH 5 at Wed Feb 18 14:30:58 2015 (GMT-00:00)

                                               MS-RPC over SMB, CAVA version: 6.6.0.0, ntStatus: SUCCESS

                                               AV Engine: Network Associates

                                               Server Name: AV1.domain.local

                                               Last time signature updated: Wed Feb 18 09:46:56 2015 (GMT-00:00)

10 File Mask(s):

*.EXE *.COM *.DOC *.DOT *.XL? *.MD? *.VXD *.386 *.SYS *.BIN

37 Excluded File(s):

*.DWL *.EDB *.FMB *.FMT *.FMX *.FRM *.INP *.LDB *.LDF *.MAD *.MAF *.MAM *.MAQ

*.MAR *.MAT *.MDA *.MDB *.MDE *.MDF *.MDN *.MDW *.MDZ *.NDF *.ORA *.ORC *.OST

*.PST *.SC *.SQC *.SQL *.SQR *.STM *.TAR *.TMP *.ZIP ???????? *RECYCLER*

Share \\gcifs.domain.local\CHECK$.

Max size of checked files=1048576 bytes.

RPC request timeout=25000 milliseconds.

RPC retry timeout=5000 milliseconds.

High water mark=200.

Low water mark=50.

Scan all virus checkers every 10 seconds.

When all virus checkers are offline:

Continue to work with Virus Checking and CIFS.

Scan on read disable.

Panic handler registered for 65 chunks.

MS-RPC User: adma26905eu

MS-RPC ClientName: gcifs.domain.local

-----------------------------------------------------------------

the "error auth 5" should mean that the user running the event enabler is missing the virus checking privilege.

when i try to connect to gcifs.domain.local on the  mmc snapin for data mover management i get an "access denied" and so

i cannot grant the needed checking privilege.

what can i try to do ?

best regards

Maurizio

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    899

    0

    Posted February 18th, 2015 07:00

    If vdm2 is your CIFS server name then
    vdm2\C$
    vdm2\C$> should work

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    899

    0

    Posted February 18th, 2015 06:00

    Same as with a physical server

    Before you run the MMC make sure you have a security context as Administrator on the VNX CIFS server

    Easiest way is to connect a share

    Then open C$ and make sure you are Administrator

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    899

    0

    Posted February 18th, 2015 07:00

    Shares dont matter

    If you have working shares then you do have a CIFS server

    See server_cifs

    That CIFS server always has a C$ share – just like a Windows server

  • tunibbles

    6 Posts

    899

    0

    Posted February 18th, 2015 07:00

    on vdm2 i have 2 shares and i can connect to them

    but i cannot connect to \\gcifs\c$ or \\vdm2\c$

    what am i missing ?

    Maurizio

  • tunibbles

    6 Posts

    899

    0

    Posted February 18th, 2015 07:00

    thanks you put me on the right way !!!

    ok, i found !! the matter was that my account (domain account) has not the right permissions in my domain to acces c$

    so i unjoined  the cifs server from the domain and readded after the command


    server_param ALL -f cifs -m djAddAdminToLg -v 1

    thanks

    Maurizio

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    899

    0

    Posted February 18th, 2015 07:00

    Name resolution maybe ?

    You should always be able to connect to
    >CIFS_server_name>\C$
    %3eCIFS_server_name%3e\C$>

    VDM or not doesn’t matter

  • tunibbles

    6 Posts

    899

    0

    Posted February 18th, 2015 07:00

    on my vdm2 i have 2 shares :

    - folder1

    - folder2

    i can access \\vdm2\folder1 and i can access \\vdm2\folder2

    i can also write files, move them or delete

    but no connection to c$

    maybe i'm missing something on the initial appliance configuration ?

    name resolution is working

    maurizio

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    899

    0

    Posted February 18th, 2015 08:00

    You’re very welcome

    Yes permissions there can be tricky and if you don’t have the right permission often the Windows response isn’t helpful