]
Posted At: Wednesday, September 17, 2003 16:10
Posted To: Exchange
Conversation: Locking down RPC; winexch2k
Subject: Re: Locking down RPC; winexch2k
just apply the durn patch. Sheesh.
- Original Message -
From: Yanek Korff [EMAIL PROTECTED]
To: Exchange Discussions
Why the need to do this?
- Original Message -
From: Yanek Korff [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:00 AM
Subject: RE: Locking down RPC; winexch2k
In an effort to sound stupid... What durn patch? For the recent RPC
vulns
: Locking down RPC; winexch2k
Why the need to do this?
- Original Message -
From: Yanek Korff [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:00 AM
Subject: RE: Locking down RPC; winexch2k
In an effort to sound stupid... What
, September 18, 2003 11:07 AM
Subject: RE: Locking down RPC; winexch2k
Unless I'm mistaken, in order to let a front-end server communicate to
back-end server servers (exchange and ad), a variety of ports are
needed... Including one negotiated port for RPC. Usually this ends up
being 1026 on my server
: Re: Locking down RPC; winexch2k
Why the need to do this?
- Original Message -
From: Yanek Korff [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:00 AM
Subject: RE: Locking down RPC; winexch2k
In an effort to sound stupid
just apply the durn patch. Sheesh.
- Original Message -
From: Yanek Korff [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Wednesday, September 17, 2003 4:07 PM
Subject: Locking down RPC; winexch2k
Quick question.
When restricting RPC to one known port by adding
6 matches
Mail list logo
