No computers show in web admin

[Benisai]

The client computer I installed Templar on is not showing up on the
server web admin software. It lists zero (0) computers. This is what I
get when I type templar.exe -d on the client:

=================================================================
Connected to ROOT\CIMV2 WMI namespace
Ok.

Templar v2.7.2777 Release
scott-2f1e0c5fb, Default
C:\Documents and Settings\************\Desktop\Templar\Templar
\alerts.txt not open
Server: 209.103.83.210:6103
***set hostname
***new_fp
***Handshake
Error: self signed certificate
*****************
-->(738027819 (IDENTIFICATION))
in message: (IDENTIFICATION)
with id: 738027819
out message: ("clientpc" "Default" "thepassword")
=================================================================

Anybody know why the client isn't letting the server know that it's
there? Thanks.

[CybrTek]

I am having the same problem the machine I installed teh agent on is
on teh same network I downloaded the client to my machine from teh web
dashboard and there are no firewalls between teh machines.

On a side note I also noticed that the "administration" link at the
top right doesn't work it references http://machinename/admin.ucw and
should be http://machinename/paragent/admin.ucw I'm new to linux and
have no idea where to go to manually edit the link suggestions would
be greatly appreciated.

[CybrTek]

I figured this out... after searching the discussion threads I found a
similar discussion that referenced creating new self signed
certificates using openssl and after creating them and replacing the
current certs in repros/certs in paragent directory (rename current
ones to old and name new ones the same as origianl) then copy the
certficate (not the key) to the agent and perform the same replacement
name the current cacert.pem to cacert_old.pem and rename the new cert
to cacert.pem then restart the agent. This worked for me and my
clients started showing up and reporting in.

On Jul 13, 2:26 pm, CybrTek <Cybrt...@gmail.com> wrote:
> I am having the same problem the machine I installed teh agent on is
> on teh same network I downloaded the client to my machine from teh web
> dashboard and there are no firewalls between teh machines.
>
> On a side note I also noticed that the "administration" link at the
> top right doesn't work it referenceshttp://machinename/admin.ucwand

> should behttp://machinename/paragent/admin.ucwI'm new to linux and

> > there? Thanks.- Hide quoted text -
>
> - Show quoted text -

[DGleeson]

Creating the self signed certificates worked for me as well.

The admin link I found in repos/nexus/components/components.lisp
search for /admin.ucw and just remove the / and it should be fixed.

I'd say its easiest to make this change before installation as the
file needs to be compiled.
Still learning how its all running so there could be an easier way.

On Jul 14, 7:49 am, CybrTek <Cybrt...@gmail.com> wrote:
> I figured this out... after searching the discussion threads I found a
> similar discussion that referenced creating new self signed
> certificates using openssl and after creating them and replacing the
> current certs in repros/certs in paragent directory (rename current
> ones to old and name new ones the same as origianl) then copy the
> certficate (not the key) to the agent and perform the same replacement
> name the current cacert.pem to cacert_old.pem and rename the new cert
> to cacert.pem then restart the agent. This worked for me and my
> clients started showing up and reporting in.
>
> On Jul 13, 2:26 pm, CybrTek <Cybrt...@gmail.com> wrote:
>
> > I am having the same problem the machine I installed teh agent on is
> > on teh same network I downloaded the client to my machine from teh web
> > dashboard and there are no firewalls between teh machines.
>
> > On a side note I also noticed that the "administration" link at the
> > top right doesn't work it referenceshttp://machinename/admin.ucwand

> > should behttp://machinename/paragent/admin.ucwI'mnew to linux and

[Benisai]

Thanks for the replies. Yes, I have already created the self signed
certificates. I'm having this problem still. I'll make the certs again
and see what happens

On Jul 16, 5:48 am, DGleeson <dglee...@gmail.com> wrote:
> Creating the self signed certificates worked for me as well.
>
> The admin link I found in repos/nexus/components/components.lisp
> search for /admin.ucw and just remove the / and it should be fixed.
>
> I'd say its easiest to make this change before installation as the
> file needs to be compiled.
> Still learning how its all running so there could be an easier way.
>
> On Jul 14, 7:49 am, CybrTek <Cybrt...@gmail.com> wrote:
>
> > I figured this out... after searching the discussion threads I found a
> > similar discussion that referenced creating new self signed
> > certificates using openssl and after creating them and replacing the
> > current certs in repros/certs in paragent directory (rename current
> > ones to old and name new ones the same as origianl) then copy the
> > certficate (not the key) to the agent and perform the same replacement
> > name the current cacert.pem to cacert_old.pem and rename the new cert
> > to cacert.pem then restart the agent. This worked for me and my
> > clients started showing up and reporting in.
>
> > On Jul 13, 2:26 pm, CybrTek <Cybrt...@gmail.com> wrote:
>
> > > I am having the same problem the machine I installed teh agent on is
> > > on teh same network I downloaded the client to my machine from teh web
> > > dashboard and there are no firewalls between teh machines.
>
> > > On a side note I also noticed that the "administration" link at the
> > > top right doesn't work it referenceshttp://machinename/admin.ucwand

> > > should behttp://machinename/paragent/admin.ucwI'mnewto linux and

[Dimitar Stojanovski]

You changed the certificate on the clients side ?

--
__

Dime
__

[Benisai]

Yes.
This is what I get now when I run Templar.exe -d

Connected to ROOT\CIMV2 WMI namespace
Ok.

Templar v2.7.2777 Release

myserver, Default
Server: 192.168.1.1:6103
***set hostname
***new_fp
***Handshake
*****************
-->(1839522708 (IDENTIFICATION))
in message: (IDENTIFICATION)
with id: 1839522708
out message: ("myserver" "Default" "password")





On Jul 23, 10:20 am, "Dimitar Stojanovski" <dimita...@gmail.com>
wrote:

[Benisai]

Apparently I was using the old version of the easy installer. I
completely reinstalled paragent using the 3.0 easy installer and
everything is working as it should. Thanks for all the help!