Verity k2Server VSpider Not Indexing

[Andrew (Webworld)]

Ok, I've got verity k2 server setup on my local machine and working correctly.
I created a cmdfile to keep all the options I need when indexing the site and
everything works on my local machine. However when I try to move this to my
client's server things fall apart.
I have the Verity k2Server service running and we are using CF MX 6.1
Enterprise edition. I create a connection to the server in the CF Administrator
pointing to k2 like so "www.mydomain.com" on port 9901 and I have a collection
defined in the k2server.ini file. The k2Server shows up as being online and the
collection I have defined shows up as well. When I go to the command line and
try to run my bat file to index the site it skips my starting point. My bat
file that I run to index the site looks like so:

net stop k2server
C:\CFusionMX\lib\_nti40\bin\vspider -cmdfile
E:\Inetpub\wwwroot\tmydomain\admin\collections\k2\ cmdfile.txt
net start k2server

The cmdfile looks like this:
-common c:\CFusionMX\lib\common
-collection E:\Inetpub\wwwroot\mydomain\admin\collections\k2
-start [url]http://www.mydomain.com[/url]
-exclude *.css
-cgiok

When I try to run this it runs ok but it skips the starting point and
therefore doesn't in fact index anything. It works on my local machine where
I'm doing -start [url]http://localhost/mydomain[/url] but on the server it does not work
where it is -start [url]http://www.mydomain.com[/url]. I assume the -start is the problem
and somehow k2 thinks I'm trying to index a site other than the one on the box
CF is installed on, but CF is on the same box that the site is running from.
Perhaps I'm doing something else wrong. Can anyone help?

[Andrew (Webworld)]

Well I've figured this one out. The Verity k2Server shipped with ColdFusion MX
only allows you to index local folders on your machine or urls beginning with
localhost. So even though the site I was trying to spider was a site on the box
k2 won't let you index it if you try to use the site's url. You have to use
localhost. Now the hosting company for this particular client has things setup
in a quirky way so I couldn't use localhost at first but I switched things
around and now I can. So problem solved. Just keep in mind that k2 that comes
with CF only spiders local folders or [url]http://localhost[/url] but will NOT spider any
sites by name even if they are on the same machine running off the same CF
Server. At least not in CFMX.

You should also look into the -prefixmap attribute when spidering using k2
because it allows you to map things like [url]http://localhost[/url] to
[url]http://www.mydomain.com[/url] so that even though you spider localhost the results
that people see will say mydomain.