I have a 2 day old trial copy of kbox 1000 v5 running on ESXi and I appear to be locked out.

If I boot the system I don't see any errors flying by or halting the boot process. (every thing looks fine). Eventually I get to the login prompt and the IP address just above the prompt reads

I can ping
nmap shows:
Interesting ports on
Not shown: 996 closed ports
25/tcp open smtp
80/tcp open http
139/tcp open netbios-ssn
445/tcp open microsoft-ds
MAC Address: 00:0C:22:AA:73:6B (VMware)

If I try to pull up in the browser I get the default FF or IE, failed to connect type message. Just to verify cookies, cache, or other fancy GUI web browser features weren't screwing with me I tried the same URL from the command line using: links and I get back the error "connection refused".

Other than simply clicking through the tabs in the kbox web UI and strictly just looking at all the features I've only done the following few things.
* added a network scan of 192.168.1-4.0-255
* saved / run scan
* went to settings to try and try and push out the kbox agent onto a few PC's
* Ran it, didn't work, I noticed in the logging of its install attempt I had an error that said the kbox file share was off and it provided a link to go turn it on.
* I folloed the link, turned on the kbox file share, checked the required NTLMv2 for clients and samba (I think that's what things were labeled)
* Clicked save, it told me I had to reboot, I clicked OK
* Waited 1 minutes... 5, 10 20 minutes, and I can't get the web UI to come back

And I've rebooted the system several times and waited 20 minutes... same outcome every time.

Any ideas?

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


OK, I'm not sure what was the true source of the problem but here are a few things support/I found and I would recommend checking in the future.

  • We had a DHCP system on our network trying to use the same static IP that was assigned to the kbox (if you can ping the kbox when its powered off, check this)
  • VMWare ESXi Server v4.? had at some point disconnected the network device assigned to VM and it took a while before I noticed the "connect at boot" checkbox was unchecked. (it had previously been on/connected)

hufff... ya this was a complete pain of a problem to chase down since I didn't know anything about the new DHCP client PC that was added to the network. But the kbox staff was still very helpful in tracing down the problem and it turns out it didn't have anything to do with the kbox itself. :/
Answered 12/07/2009 by: ehart
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity