RE: Port Forwarding
- From: v-mzhuan@xxxxxxxxxxxxxxxxxxxx (Manfred Zhuang [MSFT])
- Date: Mon, 21 Jan 2008 08:46:12 GMT
Hello Philip,
Thank you for posting here. Also thanks to Les for input.
From your post, I understand that you would like to know how to map a port.Please follow the steps below:
Note that the methods are different for SBS 2K3 Standard (which utilizes
RRAS as Firewall) and SBS 2K3 Premium (with ISA):
For ISA, in order for a custom protocol to be considered a "Server"
protocol, its definition must begin with an inbound connection:
1. In the ''Policy Elements'' branch of ISA server mmc, right click on
Protocol Definitions and choose "New >", "Definition..."
2. Give the Protocol a name. It is recommended that the last word of the
name be "Server"
3. Next...Enter the destination port number for the custom protocol being
created. For example, for Terminal Server, the port number would be 3389.
4. Choose either TCP or UDP for the Protocol Type as appropriate for the
definition. For example, for Terminal Server, the type would be TCP.
5. For the direction, choose an incoming type direction. For example, if
you chose TCP above, the direction should be inbound. If the type was UDP,
choose either Receive or Receive, Send.
6. Finish defining the protocol using the wizard. It may be necessary to
consult the publisher of the protocol for the specifics such secondary
connections. Many well-known protocols are already predefined or can be
found in RFC''s
7. Once the protocol definition is complete, publish it using "Server
Publishing Rules". Right clisk "Server Publishing Rules" and choose "New
", "Rule...". On the Protocol Setting page of the Wizard, the serverdefinition you created will appear in the drop down box. Simply select the
definition and proceed with completing the wizard.
For SBS 2K3 Standard (without ISA,) we can use RRAS to publish a service on
the private network to the Internet; however, one port can only be used
once, which means it's not possible to publish the same services (utilizes
the same port) on different private computers. And if the service requires
secondary connection, it cannot be published by RRAS:
1. Bring up the ''Routing and Remote Access'' console, and then expand to
''Server name'' '' ''IP Routing'' '' ''NAT/Basic Firewall.''
2. In the right pane, right click ''Network Connection'' to choose
Properties.
3. Switch to the ''Services and Ports'' tab, and then Add the desired
service.
For example, if you want to publish RD on different internal client
computers, you will need to configure them listen on different ports:
''306759 How to Change the Listening Port for Remote Desktop -
http://support.microsoft.com/?id=306759''.
If there's anything unclear, please do not hesitate to let me know.
Best regards,
Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Port Forwarding
| thread-index: AchazKc/RWW6Z6slQYGlinyVi3hqKA==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?UGhpbGlwQg==?= <PhilipB@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Port Forwarding
| Date: Sat, 19 Jan 2008 10:54:00 -0800
| Lines: 10
| Message-ID: <25139F8A-7F4B-4DCA-8029-8FCC6C120BDF@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:87639
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi
|
| I need to set up a port forward for requests on certain ports on the SBS
| 2003 external IP address so that they can access an IP telephone server
from
| a remote branch.
|
| Can anyone point me in the right direction for some instructions as to
how
| to port forward?
|
| Thanks
|
.
- Prev by Date: RE: Windows Server Update Services 2.0 Error
- Next by Date: Re: SBS Log On MMC crashes / .DLL Faulting.
- Previous by thread: Re: Port Forwarding
- Next by thread: Re: Repairing IIS
- Index(es):
Relevant Pages
|
