Re: Force traffic on port OTHER than 445

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mikey (mikey_at_faenza.com)
Date: 07/13/04 

Date: Mon, 12 Jul 2004 19:27:21 -0500

Yes, HTTP, but this is just to install the clinets first....client rollout.

"Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
news:OpDRhtGaEHA.3692@TK2MSFTNGP09.phx.gbl...
> SMS Advanced clients use port 80 to communicate with the MP and site
> systems. In SMS 2003 SP1 you will be able to configure the ports that you
> want the clients to talk to the sites.
> --
> Thanks,
> Jeff Harbaugh [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "mopey" <mopey@usa.com> wrote in message
> news:OtmHnqGaEHA.2544@TK2MSFTNGP10.phx.gbl...
> > Is there any ways to force traffic on ports other 445 - We have AD 2003
/
> > WINS and are trying to roll out SMS Standard security - SMS clients
uses
> > port 445, but we disabled 445 due to virus / worms - WORKAROUNDS anyone?
> >
> > Thx.
> >
> >
>
>

Relevant Pages

  • Re: Force traffic on port OTHER than 445
    ... Yes, HTTP, but this is just to install the clinets first....client rollout. ... > SMS Advanced clients use port 80 to communicate with the MP and site ...
    (microsoft.public.sms.admin)
  • Re: Force traffic on port OTHER than 445
    ... Yes, HTTP, but this is just to install the clinets first....client rollout. ... > SMS Advanced clients use port 80 to communicate with the MP and site ...
    (microsoft.public.windows.server.active_directory)