Re: SMS 2003 and Firewall port exceptions
- From: Kim Oppalfens <kim@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Sep 2005 16:05:00 +0200
In article <ulVFY0euFHA.1644@xxxxxxxxxxxxxxxxxxxx>,
stevethompson@xxxxxxxxxxxxx says...
> "John Hiebert" <John.Hiebert@xxxxxxxxxxx> wrote in message
> news:e5WLu2VuFHA.1264@xxxxxxxxxxxxxxxxxxxxxxx
> > The only thing it talks about is 1433.
>
> Sorry John, it does not... quote:
>
> "When the client establishes a TCP/IP connection, a three-way handshake is
> done. The client opens a source port and sends traffic to a destination
> port, which by default is 1433. The client source port in use is random, but
> is greater than 1024. By default, when an application requests a socket from
> the system for an outbound call, a port between the values of 1024 and 5000
> is supplied."
>
> Steve
>
>
>
All this is about a sql client, the sms admin console doesn't behave
like a sql client it connects to the site server using rpc calls.
--
Kim Oppalfens
MVP SMS
Computacenter Belgium
.
- References:
- SMS 2003 and Firewall port exceptions
- From: John Hiebert
- Re: SMS 2003 and Firewall port exceptions
- From: Steve Thompson
- Re: SMS 2003 and Firewall port exceptions
- From: John Hiebert
- Re: SMS 2003 and Firewall port exceptions
- From: Steve Thompson
- SMS 2003 and Firewall port exceptions
- Prev by Date: Re: Image package problem with sms 2003
- Next by Date: Re: XP SP2
- Previous by thread: Re: SMS 2003 and Firewall port exceptions
- Next by thread: Collections Locked How to unlock
- Index(es):
Relevant Pages
|