Has anyone configured nimsoft on a Threat Management Gateway server? I am really having hardtime to get it in nimsoft.
Ananda Guberan K
Yes, if you mean allowing robot access to hub. It's not really any different from other common TMG rules. Just allow your port range to both directions from proper source / destination. TCP 48000-x
Generally speaking, no. I suggest you monitor the traffic in TMG's tools and check what's going on. It should be fairly straight forward.
It's easy to do it wrong if you allow it to both directions in one rule. To troubleshoot, I suggest you try creating a separate rule for each direction.
Did you make sure to set the first probe port on the controller to 48004 or something like that? I think the range you opened looks good (we use the same), but that will only work with the first probe port set. Otherwise you get random port numbers.
The first probe port is 48000 in this case. And also on the TMG host, an exception is set to the nimsoft server. And I guess we should have some better insight when we have the route table for this host. May be with that we can understand the communication factor.
Creating a seperate rule here makes sense. Let me investigate on this.
I was able to identify that the packets were rejected by the TMG which we found out by monitoring the traffic in TMG. So upon adding a rule (inbound and outbound) we were able to set up monitoring. But we had distsrv on another hub so we need to add another rule atleast till we have the probes installed and have them disabled post probe deployment. But if the server and distsrv are on the same hub then one single rule should be good enough.