RE: connecting to client desktop still not working

Well, I discovered it is indeed Trend Micro's PC-cillin Internet Security
2005 that's blocking my attempts to connect. If I disable the firewall
portion, I can connect to my desktop immediately. I don't know why Norton's
product allows this by default and Trend Micro does not?

Can anyone help me configure an exception in PC-cillin to allow Remote
Desktop to work? Am I the only one out there using PC-cillin on SBS and
trying to connect remotely to my desktop? Overall, I like Trend Micro's
product much more than the latest Norton product. BTW, I have SBS Standard
using one NIC and using the Linksys Router as a firewall, plus PC-cillin on
all desktops to monitor the outgoing connections as well as incoming.

"GeordieB" wrote:

> Thanks to all the great info here, I've successfully completed my first SBS
> install on a client's network, and they absolutely love SBS and Exchange. Now
> for my question: a few weeks back, I discovered I can't access my client
> desktops in my own network through RWW, although I can connect to the server.
> I never got it working right, but the issue was renewed after this client
> installation when I discovered that I could connect to every one of their
> desktops (as well as their server) from the same laptop I'm using to try to
> connect to my own network.
>
> So at least now I've determined the problem isn't on the computer trying to
> make the connection, but on the computer I'm trying to connect to. The only
> real difference I'm seeing between the two networks is I'm using Trend Micro
> Internet Security on my own network (including the laptop), and my client has
> Norton Internet Security as a firewall. Windows firewall is 'on' on every
> computer as well, as SBS has forced this and I haven't yet edited the Group
> Policy to allow client computers to turn it off (and so far, no issues have
> risen because of Windows Firewall being on along with Norton or Trend Micro).
>
> What can I do to connect to my own network's client desktops at this point?
> I've disable the popup blocker in IE, allowed Active X controls, turned off
> add blockers, etc. Suggestions welcome and appreciated.
>
> Geordie
.

Relevant Pages

  • Re: Trend Worry Free Advanced 6
    ... The Trend "Common Firewall Driver" is used for more than just the firewall. ... Just on the odd chance someone else needs to know, I'm getting closer to the FTP problem on a virtual XP machine hosted on the SBS box. ... Trend UK pre-sales have promised me a call in the morning to 'tweak' the system, ... Windows Small Business Server 2008 Unleashed ...
    (microsoft.public.windows.server.sbs)
  • RE: [fw-wiz] Worms, Air Gaps and Responsibility
    ... Some companies try to firewall by business unit, ... Even firewalling each subnet is a support nightmare in the ... "This set of things should never talk" isn't a difficult security policy ... > companies had patched XP desktops, ...
    (Firewall-Wizards)
  • Re: Possible Trend SMB 3.0 CSM problem on SBS2003
    ... Apparently Trend also modifies Group Policy because now we can disable XP ... Firewall at the workstation. ... >>> the installation of the Trend Micro 3.0 CSM install may be to blame. ... Our server had just been upgraded two weeks before using the Swing ...
    (microsoft.public.windows.server.sbs)
  • Re: Possible Trend SMB 3.0 CSM problem on SBS2003
    ... I did an upgrade from CSM 2.0 with the released v3.0 and there was nothing ... during setup that suggested that I either enable or disable the Trend ... > request was made that the Trend firewall default to disabled. ... > I haven't done a clean or upgrade installation using the release version; ...
    (microsoft.public.windows.server.sbs)
  • Re: What security package for SBS?
    ... I have Exchange Defender doing the pre spam/pre virus-ing in front so I've left the a/v on Exchange with Trend, but folks do argue that having differing vendors for desktop versus Exchange might be wise. ... With a business class firewall stripping crap off all incoming traffic and properly implemented security policies in addition to giving your users absolutely no admin rights, there is no reason to believe you can't create a secure Microsoft Network. ...
    (microsoft.public.windows.server.sbs)