Re: Trend CSM 3 config problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you try to do a remote install from a system running Server 2003 SP1, it
will fail unless you change the settings per my post. Once you change the
permissions, remote install works fine.

Gregg Hill




"Bill Dunn" <bill@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ON$76t4FHHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
Thanks to all for these ideas. I did snag the ISAtrpe.zip file last
evening and this resolved the issue immediately!

Using Les's suggestions, I was able to get the client installed but not
via the browser or e-mail invite. I used the link line from the e-mail
invite and placed into the RUN command. Client installed perfectly.

Thanks again for all the suggestions.

Bill Dunn



"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OVpQMoxFHHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
You need to add the SSL port. Download this
http://www.isatools.org/tools/ISAtrpe.zip

It's a great interface instead of writing VB code. After you have added
the SSL port you should be able to access CSM. Delete you rule in the
ISA. It's not needed. If you get an error on the CSM shortcut, edit the
link (you will find it in the CSM folder) to https://localhost/4343.


--
Claus
"Bill Dunn" <bill@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23wRL79uFHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
I just installed the Trend SMB CSM 3.0 and it's dealing me fits! Server
is SBS2K3 Premium with ISA 2004 installed

When I tried to open the management console the first time, I received a
proxy error about the need for port 4343. So, I tried to create a new
ISA firewall policy and used HTTPS "custom" with port 4343 for both in
and outbound. Applied it to "internal" on both.

No joy. So, I created an exemption in Internet Explorer. that worked
and I can now open the management console and config things. Updates
seem to work fine.

But... when I try to do a remote install on a client, everything works
until I log on to the remote client. I receive the error "Unable to
connect to [client computer name]"

I'm sure this has to do with my configuration but after 3-hours of
toying with various settings, I just can't get things to work.

Additionally, when I selected to create an install script for the
clients, ... well, I select the server to house the script, press the
select button and nothing happens.

I'd appreciate suggestions on how to fix my mistake.

Thanks,

Bill Dunn








.

Quantcast