LDAP Setup with Virtualbox

[Dlo]

Context: Newbie to Windows environment but working hard to make it
work..lol
Objective: GSA to Crawl SharePoint2007 running on a VM
Problem: GSA sees the SharePoint structure but not rights to crawl –
Authentication error

GSA v6.8

Physical server running Windows 2008
This server his running Virtualbox as the VM.
The VM runs Windows 2008, DNS’ LDAP, IIS and Sharepoint2007

Logged in the VM, I can create LDAP users


Outside the VM
Logged as SharePoint Admin I can add users through the User lookup

The GSA connects to SharePoint because it returns the SharePoint's
structure
But all folders and documents are in Errors – Authentication error

LDAP Setup
Now I understand that I need to complete the Administration/LDAP SetUp
Not absolutely sure of values I should be providing here

I have tried the HTTP:// with the IP address of the physical box (Port
forwarding is enable for port 389 and port 80 between Physical and VM)

I have left the LDAP Binding information as is because I dont fully
understand what is required here (please provide me information)

The returning message is:
javax.naming.InvalidNameException: Invalid name: /66.46.197.48:389/
Failed to detect base

From this message, is it the "Invalid name" the name of host or of the
Distinguished Name?
Or did it failed to detect the LDAP HOST?

Thank you in advance for you support
DLO

[Dave Watts]

> Context: Newbie to Windows environment but working hard to make it
> work..lol
> Objective: GSA to Crawl SharePoint2007 running on a VM
> Problem: GSA sees the SharePoint structure but not rights to crawl –
> Authentication error

OK. First, you don't really need to use LDAP Setup on the appliance
unless you want to authenticate users against LDAP before performing a
secure search (which you may or may not want to do depending on how
secure documents are actually served, etc).

Second, you have to configure both the crawl and the serve to work
with your security, unless you plan to serve all results publicly
without requiring authorization, in which case you'll only have to
configure the crawl to work with credentials.

Third, you typically don't just crawl SharePoint sites, because they
don't really lend themselves to crawling in their default deployment
configuration. That's why you have a SharePoint connector. You may use
the onboard SharePoint connector, or the offboard one (which requires
installation on a separate server, but has some advantages over the
onboard connector).

Fourth, the way you set up crawl security will depend on how you
configure the connector. If you configure the connector to build a
content feed, the connector will require the appropriate credentials
to interact with SharePoint. If you configure the connector to build a
metadata-and-URL feed, you will also need to provide those credentials
under Crawler Access.

Read this:
https://code.google.com/apis/searchappliance/documentation/connectors/260/connector_admin/sharepoint_connector.html

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
GSA Schedule, and provides the highest caliber vendor-authorized
instruction at our training centers, online, or onsite.

[DLO]

Sorry for the delay to answer back....
Thank you for the time to respond to my questions
Finally got the SharePoint crawling going sucessfully...now need to
resolve a VirturalBox network card issue...
Thank you again Dave

daniel
++++++++++++++++++++++++++++++++==

> Read this:https://code.google.com/apis/searchappliance/documentation/connectors...
>
> Dave Watts, CTO, Fig Leaf Softwarehttp://www.figleaf.com/http://training.figleaf.com/