tuansandman / opendlp

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

Can't get Windows Agent Scan to deploy #33

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run OpenDLP server VM and WinXP VM on VirtualBox at the same time
2. Open OpenDLP webpage on host computer,
3. Start New Scan on WinXP VM.

What is the expected output? What do you see instead?
I see the "Attempting to deploy..." message, and a warning not to navigate away 
from the page until it's done. It's never done. 

What version of the product are you using? On what operating system?
OpenDLP 0.4.1

Please provide any additional information below.
I'm fairly certain I'm just doing something wrong here, and it's not an issue 
with OpenDLP itself. I've set the Network Adapters on both VMs to Host Only 
(after previously having had them as Bridged). NetBIOS confirmed on WinXP VM. I 
make sure both VMs can see each other via ping. I've even turned off the 
Firewall in the WinXP VM. Each time it just hangs there.

What am I missing?

Original issue reported on code.google.com by loum...@gmail.com on 15 Sep 2011 at 8:31

GoogleCodeExporter commented 9 years ago
From another Windows box, can you do this to your WinXP VM:

net use \\1.2.3.4\C$ password /u:WORKGROUP\username

By default with a standalone Windows XP system, you cannot do this and will 
have to modify the system.

By default in a domain environment, you can do this.

Original comment by andrew.O...@gmail.com on 16 Sep 2011 at 4:26

GoogleCodeExporter commented 9 years ago
Ah, I see. Thank you! I cannot run that command. My VM is a standard standalone 
installation.

I'm not too familiar with windows domain environments. Does this mean I have to 
see about having the VM join the office domain registry, or is there a simple 
way to set up a mini domain environment? Or can I just tweak the appropriate 
settings without actually having to bother with the domain issue?

Original comment by loum...@gmail.com on 16 Sep 2011 at 4:54

GoogleCodeExporter commented 9 years ago
Scratch that, I managed to get the VM joined to our company domain without 
hassle.

It has (semi) successfully deployed!

Question, how long does deployment usually take? Looking at the Scan 
Results/Detail page, it's been going on 9 minutes...

Original comment by loum...@gmail.com on 16 Sep 2011 at 8:15

GoogleCodeExporter commented 9 years ago
Deployment on a LAN usually takes 5-15 seconds. Keep in mind that the scanned 
system must be able to see the OpenDLP VM's web server in order to communicate 
back to it. If you left the OpenDLP VM's network settings on "host only" and 
the Windows XP VM is something else, the Windows XP VM will not be able to 
communicate with the OpenDLP VM.

If this is not an issue, the OpenDLP agent is probably still enumerating the 
file system after 9 minutes. This part of the scan can take longer if you have 
a lot of files on the system. Once it's done enumerating all the files, it will 
begin actually searching them. It will then upload results every X seconds (300 
seconds in a default policy).

Original comment by andrew.O...@gmail.com on 16 Sep 2011 at 10:13

GoogleCodeExporter commented 9 years ago
The XP client can ping the server, and both are on Bridged mode, so I think
that's okay.

The XP client is a completely fresh install. I didn't even bother putting
test files in there, so I don't think it's that big...

I checked the log file on the client though. It seems to finish scanning
files fairly quickly, and then just kind of loops with the following:

Done with everything. Sending request to web server to uninstall us.

over and over again...

at least twice libcurl returns 23, which google says is:

CURLE_WRITE_ERROR (23)

This sounds like there is, in fact, something preventing either the client
from talking to the server, or the server from responding.

I took another look at the various messages that popped up during boot, and
I found a few warnings:

According to the VirtualBox forums, that piix4 error shouldn't be an issue
since the SMBus refers is just a warning about not being able to find the
motherboard theremometer, etc.

I'm not sure how bad the apache errors are, since the web page loads and
everything deploys correctly.

I did try "start ssh", but got the following error message:

No idea if that's the cause of the problem, since, i'd think that if that
was the issue, it wouldn't have been able to deploy at all.

Anyway, I'm completely out of ideas, if you have any thoughts...

Original comment by loum...@gmail.com on 19 Sep 2011 at 8:04

GoogleCodeExporter commented 9 years ago
Hi, I have installed OpenDLP in my virtual box. I can scan my PC and other PC 
too within the subnet but can not scan few devices within its subnet? Friends, 
do you have any idea on it. And also I can not scan other network devices 
however I can ping and telnet those devices on port 443 and 445 from OpenDLP 
installed device that is Virtual Machine.

Tx
Damodar

Original comment by pathtopo...@gmail.com on 22 Oct 2014 at 11:41