search

jbenz / opendlp

Automatically exported from code.google.com/p/opendlp
0 stars 0 forks source link

OpenDLP deploys to Windows 2012 R2 but scan never starts #114

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a Windows filesystem (agent) profile using a Windows domain account
2. Start a scan using profile in step 1 of a Windows 2012 R2 (64bit) server.
3. Receive error "Possible error starting OpenDLP, check scan results when done 
deploying all agents here".

When I look at the server I wish to scan, I see that the OpenDLP directory has 
been copied to c:\Program files but the "OpenDLPz" zip file is still 
compressed.  Another item to note, I have tried using a copy of the sc.exe file 
from a 32-bit Windows machine and a copy of sc.exe from the 64-bit Windows 2012 
R2 machine in two separate tests and receive the same results. 

What is the expected output? What do you see instead?
I expect to see progress from the scan but instead see -1 Deploying forever.

What version of the product are you using? On what operating system?
0.5.1.  I'm using the pre-built VM.

Please provide any additional information below.

Original issue reported on code.google.com by csprague...@gmail.com on 11 Mar 2014 at 6:47

GoogleCodeExporter commented 8 years ago 
Yeah we are having the same problem.

Original comment by Luke.Mi...@gmail.com on 12 Mar 2014 at 8:53

GoogleCodeExporter commented 8 years ago 
Are you using a password or passing the hash?
What is the md5 checksum of the OpenDLPz.exe file on the Windows machine?
Does that md5 checksum match the checksum of OpenDLPz.exe on your OpenDLP 
server?

Original comment by andrew.O...@gmail.com on 13 Mar 2014 at 4:36

GoogleCodeExporter commented 8 years ago 
I am using a password.
Here is the MD5 of the OpenDLPz.exe on the Windows machine:
 91F0B176308DB8255274043E0B37DD68
And yes, that MD5 matches the MD5 of OpenDLPz.exe on the OpenDLP server.

Original comment by csprague...@gmail.com on 13 Mar 2014 at 4:52

GoogleCodeExporter commented 8 years ago 
Any other thoughts on this issue?  I'm sure it has something to do with new
security features in Windows Server 2012 but am unsure where to start.
Anyone intimately familiar with what OpenDLP does on the Windows box when
an agent scan is submitted that can offer suggestions as to what may be
causing this problem?

Original comment by csprague...@gmail.com on 24 Mar 2014 at 5:01

GoogleCodeExporter commented 8 years ago 
It sounds like the "winexe" step of deployment is not working.

1. What happens if you issue the following command from the OpenDLP server (is 
"c:\dir.txt" created)?

winexe --user='DOMAIN\\username' --password='password' //win2012.ip.address 
'dir c:\\ > c:\\dir.txt'

2. If this fails, look at this possible solution: 
https://code.google.com/p/opendlp/issues/detail?id=89

Let me know how it works out. If step 2 works, I'll release a new version of 
OpenDLP with this fix included.

Original comment by andrew.O...@gmail.com on 26 Mar 2014 at 1:08

GoogleCodeExporter commented 8 years ago 
Is there a fix for this issue? I tried the new winexe and it still does not 
work.

Original comment by ericgome...@gmail.com on 4 Jun 2014 at 6:04