RE: SBS2K3 Prem Symantec Security Gaeway

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Keith,

Thanks for your update.

I am not sure if you have followed the wrong steps for the protocol
definitions in my first reply. So I would like to post the correct step in
my second reply again. You can al

============================================
==== Create the Protocol Definitions
1. Start the ISA Management snap-in. To do so, click Start, point to
Programs, point to Microsoft ISA Server, and then click ISA Management.
2. Under Policy Elements, locate the Protocol Definitions container.
3. Right-click Protocol Definitions, point to New, and then click
Definition.
4. In the Protocol definition name box, type a descriptive name for the
definition (for example, type Port 500 UDP Send Receive), and then click
Next.
5. In the Port number box, type 500. In the Protocol type list, click UDP.
In the Direction list, click Send Receive (do not click Receive Send), and
then click Next.
6. Under Do you want to use Secondary connections? Click No.

Note:

1. You can use the same method to add the UDP with range 1024-65535.
However, you need to add those ports one by one. So it is a real time
consuming work. Fortunately, you can install the SBS SP1 to update the
ISA2000 to ISA2004 and in the ISA 2004, there have the feature to add a
range of ports.

2. You can use the similar method to open inbound UDP 500, the difference
is to select Receive Send as the Direction.

3. The "Secondary Connection" is not used for the Source/Destination port
range. Actually, we do not need to configure the Source Port.

==============================================

That means for the inbound protocol definitions, we need to open,
UDP port 49152 Receive/Send,
UDP port 49153 Receive/Send,
UDP port 49154 Receive/Send
.............................
.............................
UDP port 50150 Receive/Send
UDP port 50151 Receive/Send

So, as I have mentioned, it is recommend updating to ISA 2004 to make this
job simple.

If you have any questions or concerns, please feel free to let me know.
It's my pleasure to be of assistance.


Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • Re: Fairly Urgent regarding the CSocket Class (Arent they all)
    ... Running in the IDE it would hang at the .Bind call on the UDP port after ... setting the protocol and port number. ...
    (microsoft.public.vb.general.discussion)
  • Re: Virtualized VPN
    ... If you want to port forward PPTP VPN traffic, you need to forward TCP 1723 as well as GRE or Protocol ID 47. ... Theres's two parts of it, the L2TP traffic uses UDP Port 1701, and the IPSec traffic requires the following: UDP Port 500, Protocol ID 50 and Protocol ID 51. ... Microsoft Certified Trainer ...
    (microsoft.public.windows.server.networking)
  • Re: Never seen this before?
    ... UDP port 500 is Internet Key Exchange protocol which is most commonly ... or using the Windows VPN connection you would see traffic like this. ...
    (comp.security.firewalls)
  • Re: VPN with ADSL
    ... This is not an UDP port 47 but an IP protocol 47. ... SOHO router might have the settings for IPSec pass-through and PPTP ...
    (microsoft.public.win2000.networking)
  • abort at the end of data transfer
    ... data chunk is i.e 6. ... int init_client(int port, char *ip) { ... Protocol Info ... Stream Control Transmission Protocol, Src Port: 1031, Dst Port: ...
    (comp.lang.c)