|
TADDM anchor server
|
|
Replies:
6
-
Pages:
1
-
Last Post:
Oct 1, 2009 6:36 AM
Last Post By: tibor122
|
|
|
Posts:
5
Registered:
Sep 22, 2009 12:58:46 PM
|
|
|
|
TADDM anchor server
Posted:
Sep 22, 2009 01:14:05 PM
|
|
|
|
Hello,
what exactly is an Taddm anchor server...is it a new instalation of TADDM server behind the firewall, or is it just a command that describe at what IP is the anchor server. THX
|
|
Posts:
57
Registered:
Jun 10, 2008 08:30:24 AM
|
|
|
|
Re: TADDM anchor server
Posted:
Sep 23, 2009 04:11:28 AM
in response to: tibor122's post
|
|
|
|
The TADDM server will install on the TADDM anchor server some files in order to perform the scans behind the firewall, but it is not a full TADDM installation. I think it's around 200MB of files or more, I can't remember exactly. I don't know if things have changed in recent TADDM version, but in the past each time you were running a discovery using the anchor server, the files were systematically copy over the anchor server, even if there were already there. And also, remember to add your anchor server in your scope of discovery.
|
|
Posts:
5
Registered:
Sep 22, 2009 12:58:46 PM
|
|
|
|
Re: TADDM anchor server
Posted:
Sep 23, 2009 04:31:49 AM
in response to: tibor122's post
|
|
|
|
So I don't neet to do anything, just configure the host (IP) as an anchor in the producht console/anchor and gateway and enable ssh on the firewall? The instalation of anchor server will be automatically. Or what other ports must be enabled?
|
|
Posts:
57
Registered:
Jun 10, 2008 08:30:24 AM
|
|
|
|
Re: TADDM anchor server
Posted:
Sep 23, 2009 06:12:16 AM
in response to: tibor122's post
|
|
|
|
that's right, as long as your TADDM server can ssh/scp to your anchor server, you should be all right! Good luck.
|
|
Posts:
5
Registered:
Sep 22, 2009 12:58:46 PM
|
|
|
|
Re: TADDM anchor server
Posted:
Sep 30, 2009 10:49:58 AM
in response to: G1lles's post
|
|
|
|
I have created a virtual network with 2 subnets. the first subnet is 192.168.2.0, the second is 192.168.3.0. Every host is based on windows 2003 server. I have a firewall between the two subnets so they can't see each other.
The TADDM server IP is 192.168.2.10 (GW 2.1) can connect across SSH to 192.168.3.1. Therefor I set the IP for anchor server 192.168.3.1. The anchor can reach the 3.0 subnet. The question is: if I had configured the taddm gateway or not, every time have the discovery run succesfully with 31 sensors. how is this possible? The taddm redbook say, that on windows host must be an windows gateway created.
On all hosts was enable ssh, snmp and running bitwise WinSSHD server.
|
|
Posts:
57
Registered:
Jun 10, 2008 08:30:24 AM
|
|
|
|
Re: TADDM anchor server
Posted:
Oct 01, 2009 05:07:15 AM
in response to: tibor122's post
|
|
|
|
If you installed your taddm server/anchor on a Windows machine, then you don't need a windows gateway. The windows gateway is needed only if your TADDM server is an unix machine and you need to discover some windows hosts. The windows discovery is done using wmi commands, which a unix server can not handle. So you have to deploy a windows gateway to execute the wmi command to discover other windows machine (I hope it make sense). So if I understood correctly your setup, your anchor is already a windows machine, therefore it can perform all the discoveries on your second subnet.
|
|
Posts:
5
Registered:
Sep 22, 2009 12:58:46 PM
|
|
|
|
Re: TADDM anchor server
Posted:
Oct 01, 2009 06:36:39 AM
in response to: G1lles's post
|
|
|
|
Thanks, yes it make sense. I have both, the TADDM server and the anchor on the Windows machine.
|
|
|
|
|
