RTP: Specifying a Static Port

Dears,
As you know, RTP uses port range 16384 to 32767 dynamically. Can we define any specific static port manually so that rtp always use that udp port for voice call. I am using 3800 series router for voip setup. I tried to find any configuration but couldn't.
Waiting for immediate positive responseâ¦â¦.
Best Regards
Rameez

NBAR can properly classify RTP and RTCP, so you could use NBAR on the outbound GigEthernet interface to remark the packets to a specific ToS/DSCP value that would match your service provider's contracted CoS value(s).
You do have multiple classes of service in your contract with your service provider?
You mentioned in an earlier post that this is a satellite link. Not for voice (UDP) traffic, but have you tried Cisco RBSP Satellite optimizations for TCP over the Satellite link?

Similar Messages

Step by Step to Set up DFSR port to Static port

Is there any guide for Step by step guide to implement DFSR ports to static.

It’s easy: use the dfsrdiag staticRPC command. You can verify the static RPC port change by using the
dfsrdiag dumpmachinecfg command. (Note: the default value of the StaticRPC parameter is 0. This indicates a dynamic port assignment.)
Will this setting last across reboots? You bet. According to DFS Replication guru Rob Post, when you specify a static port, the server-specific DFS Replication configuration file (stored in %SYSTEMDRIVE%\System Volume Information\DFSR\Config\DfsrMachineConfig.XML)
is updated with the port information. This allows the setting to hold across reboots and service starts and stops. If someone ever deleted the configuration file, the configuration file would be reset to defaults, though this should be extremely rare.
If it did occur, you will see event 6702 in the DFS Replication event log notifying you that the custom server configuration settings have been erased.
http://blogs.technet.com/b/filecab/archive/2006/05/26/429364.aspx

Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.

We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR

WRVS4400N Static Port Forwarding

Hi
I'm trying to get 3CX working and it is detecting that there are issues with the firewall on router. I think have narrowed it down to the router as the problem still exists with Kaspersky and Windows Firewall off. Please see the bottom of this page for the results page from 3CX.
There is a description 3CX provide on getting this working are for Linksys and Cisco routers.
The Linksys description is fairly straight forward and doesn't make any difference; the Cisco description appears to be a Windows based Utility with some similarities to the WRVS4400N web interface and setting up ACL rules and as close as I can replicate what I think should be set doesn't work either.
The link for the cisco description is http://www.3cx.com/blog/voip-howto/cisco-voip-configuration/
The link for NAT firewall issues on 3CX http://www.3cx.com/blog/voip-howto/static-port-mappings/
If anyone has any ideas or can point me in the right direction i'd be very grateful.
Kind regards
Mark
Firewall Output
3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
<11:40:57>: Phase 1, checking servers connection, please wait...
<11:40:57>: Stun Checker service is reachable. Phase 1 check passed.
<11:40:57>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<11:41:07>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:41:07>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<11:41:08>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:41:08>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<11:41:08>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.
<11:41:08>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<11:43:23>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
<11:43:23>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
<11:43:23>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
<11:43:23>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
<11:43:23>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
<11:43:23>: UDP RTP Port 9005. NO RESPONSE received. Phase 4-06 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:43:23>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
<11:43:23>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
<11:43:23>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
<11:43:23>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
<11:43:23>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
<11:43:23>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
<11:43:23>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
<11:43:23>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
<11:43:23>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
<11:43:23>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
<11:43:23>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
<11:43:23>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
<11:43:23>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
<11:43:23>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
<11:43:23>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
<11:43:23>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
<11:43:23>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
<11:43:23>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
<11:43:23>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
<11:43:23>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
<11:43:23>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
<11:43:23>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
<11:43:23>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
<11:43:23>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
<11:43:23>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
<11:43:23>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
<11:43:23>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
<11:43:23>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
<11:43:23>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
<11:43:23>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
<11:43:23>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
<11:43:23>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
<11:43:23>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
<11:43:23>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
<11:43:23>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
<11:43:23>: UDP RTP Port 9041. NO RESPONSE received. Phase 4-42 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:43:23>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
<11:43:23>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
<11:43:23>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
<11:43:23>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
<11:43:23>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
<11:43:23>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
<11:43:23>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
<11:43:23>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.
Application exit code is 4

Hi Sir,
I'm sorry if i dind't understand your question, but already you tried the configuration as attached? Please change the IP to your 3CX IP.
Regards.
Andrey Cassemiro

NTDS single/Static port vs Fixed port range.

I'm well aware on how to setup a custom Fixed RPC port range (as per https://support.microsoft.com/kb/154596?wa=wsignin1.0).
I also know NTDS can be configured to use a single/Static TCP port (as per http://support.microsoft.com/kb/224196).
My question is:
What happens if you *only specify a Fixed RPC port range*
AND
*Do not* specify a single/Static Port for
NTDS
-> Will NTDS simply offer its services through the
Fixed RPC port range?
Thanks.
Regards,
A.

Hi A,
How is it going? I agree with Pierre. If you need further help regarding this question, please don't hesitate to let us know.
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Best regards,
Frank Shen

Can you configure a static port to use with certsrv.msc?

I am trying to use certsrv.msc to connect from my workstation to the CA for administration purposes. Workstation is Win7, CA is 2008 R2 Enterprise running Enterprise Subordinate on a dedicated box.
I configured a static DCOM port for certsvc by following this article, including bouncing the service and also rebooting the CA box:
http://social.technet.microsoft.com/wiki/contents/articles/1559.how-to-configure-a-static-dcom-port-for-ad-cs.aspx
The static port was opened in the firewall from my workstation to the CA. We also found that TCP 445 was required, so that has been opened as well, port 135 & other ports normally needed for autoenrollment should be open. Sniffing the firewall
showed that a random high numbered port that is not the static dcom port is being attempted - this is the only port showing dropped packets & no traffic on the static port.
I am wondering if there is a way to configure a static port for this high-level random port to use with certsrv.msc as I was able to do with the certsvc dcom port? I am trying to avoid having tens of thousands of network ports wide open going to my
CA... Thanks in advance!

Hi Steve,
I am sorry that I wasn’t able to find references about restricting certificate services only use one port in the random port range.
However, we can configure RPC dynamic ports allocation to restrict port range. In the meantime, we should keep at least 100 ports open to keep necessary system services running.
More information for you:
How to configure RPC dynamic port allocation to work with firewalls
http://support.microsoft.com/kb/154596/en-us
Service overview and network port requirements for Windows
http://support.microsoft.com/kb/832017/en-au
Firewall Rules for Active Directory Certificate Services
http://blogs.technet.com/b/pki/archive/2010/06/25/firewall-roles-for-active-directory-certificate-services.aspx
Best Regards,
Amy Wang

SQL Server 2012 - 3 SQL clustered instances - one default/ two named instances - how assign/should assign static ports for named instances

We have two physical servers hosting 3 SQL 2012 clustered instances, one default instance and two named instances.
The default instance is using port 1433 and the two named instances are using dynamic port assignment.
There is discussion about assigning static port numbers to the two named clustered SQL instances.
What is considered best-practice? For clustered named instances to have dynamic or static ports?
Are there any pitfalls to assigning a static port to a named instance that is a cluster?
Any help is greatly appreciated

Hi RobinMCBC,
In SQL server the default instance has a listener which listens on the fixed port which is TCP port 1433. And for the named instance the port on which the SQL server listens is random and is dynamically selected when the named instance of the SQL server
starts.
For Standalone instance of the SQL server we can change the dynamic port of the named instance to the static port by using SQL server configuration manager as other post, however, in case of the cluster, when we change the port no. of the named instance
to the static port using the method described above, the port no. again changes back to the dynamic port after you restart the services. I recommend you changing the Dynamic port of the SQL Server to static port
on all the nodes , disabling and enabling the checkpointing to the quorum.
For more information, you can review the following article about how to change the dynamic port of the SQL Server named instance to an static port in a SQL Server 2005 cluster.
http://blogs.msdn.com/b/sqlserverfaq/archive/2008/06/02/how-to-change-the-dynamic-port-of-the-sql-server-named-instance-to-an-static-port-in-a-sql-server-2005-cluster.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Risk and Rollback to assigning Static ports.

Good afternoon.
We have been using Exchange CAS servers using MSNLB for the past 3 years. Works well for us with a few bugs but now we are upgrading our virtual infrastructure and MSNLB is no longer really an option. Going through the process I see the requirements
of using static ports for RPC. I have a couple of questions.
What is the risk/outtage to users? I understand the RPC Client service gets restarted. Do users need to restart outlook? repair their profile? etc etc
To make the changes on SP1 and Later (we are SP2) it appears to be just adding the reg key and restarting the service. Is there a rollback procedure ? (delete the key and restart the service?)
Anyone have any issues in doing this?
Thanks
Drew

We will be using a hardware loadbalancer (coyotepoint) although we are also considering software lbs
So why the need for static ports? Isnt that just something the vendor recommends? I have never set static ports with a load balancer myself and its been fine.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

[SOLVED] NFS Static Ports

Hi, I just switched over to Arch a couple of days ago. I have been extremely pleased with this distro, but am confused on one part. I have an IPCOP firewall setup with dmz pinholes from blue to green for a couple of nfs shares. For this I have to have the nlockmgr, status, and mountd on static IP's. In other distros I have followed these steps:
1. Create the file "/etc/sysconfig/nfs" and add the following contents:
STATD_PORT=4001
LOCKD_TCPPORT=4002
LOCKD_UDPPORT=4002
MOUNTD_PORT=4003
2. Append the following to the file "/etc/services":
rquotad 4004/tcp # rpc.rquotad tcp port
rquotad 4004/udp # rpc.rquotad udp port
3. Restart the nfs services
This does not seem to work in Arch though. Can someone point me in the right direction to setting these ports to static??
Thanks
Last edited by oiad (2010-06-18 04:47:03)

Yes it works fine. The nfs server, on ipcop's green subnet, has the following in /etc/modprobe.d/* :
# Static ports for NFS lockd
options lockd nlm_udpport=2232 nlm_tcpport=2232
as well as the /etc/conf.d/* settings, which results in this:
$ rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 2231 status
100024 1 tcp 2231 status
100021 1 udp 2232 nlockmgr
100021 3 udp 2232 nlockmgr
100021 4 udp 2232 nlockmgr
100021 1 tcp 2232 nlockmgr
100021 3 tcp 2232 nlockmgr
100021 4 tcp 2232 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100005 3 udp 2233 mountd
100005 3 tcp 2233 mountd
'rpcinfo -p <server>' on the client, which is on ipcop's blue subnet', gives the same output. I have setup pinholes for the five ports listed.
See if the modprobe settings work for you.

What is the recommended static port range for SQL Server 2008 to SQL Server 2014 named instance?

I want to assign a static port to SQL Server 2008 to SQL Server 2014 named instance. Should the port be greater than 49151? The following links give contradicting information:
https://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx
Avoid numbers greater than 49151 which Windows might select for other purposes.
https://technet.microsoft.com/en-us/library/ms345327(v=sql.100).aspx
Port numbers should be assigned from numbers 49152 through 65535
Thanks..

I would still pick a port number below the ephemeral list (dynamic port usage [41952-65535]) as it'll reduce the chances of having a port collision when SQL Server starts up.
Also, I'd stick to lower numbers if possible (<25,000) as some firewalls skew higher port numbers to be more malicious (if heuristics are used).
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

How to specify an SMTP port rather than 25 in JavaMail?

This is my segment of code, but I don't know where I can specify the SMTP port. Please help me.
Properties props = System.getProperties();
props.put("mail.smtp.host", "smtp.mail.yahoo.com");
Session session = Session.getDefaultInstance(props,
    new MyAuthenticator("dxxvi", "nopassword"));
MimeMessage message = new MimeMessage(session);
message.setFrom(new InternetAddress("[email protected]",
                                    "Thai Dang Vu"));
message.addRecipient(Message.RecipientType.TO,
    new InternetAddress("[email protected]"));
message.setSubject("I test the Yahoo! Mail Plus service");
message.setSentDate(new Date());
Multipart multipart = new MimeMultipart();
BodyPart bodyPart = new MimeBodyPart();
bodyPart.setText("If you can read this, $19.99/year is worthy");
multipart.addBodyPart(bodyPart);
bodyPart = new MimeBodyPart();
bodyPart.setDataHandler(
    new DataHandler(new FileDataSource("Resume.doc")));
bodyPart.setFileName("Resume.doc");
multipart.addBodyPart(bodyPart);
message.setContent(multipart);
Transport.send(message);

props.put("mail.smtp.port", "42");

Assigning static port address

Hello All,
We are having a standalone BOE server. I have a doubt about assigning static port addresses to servers. We had a standard deployment of BusinessObjects 4.0 SP2. Our admin has assigned static request port address to APS, CMS, FRS, Crystal report servers and Dashboard server instead of using "Auto assign".
Does it necessary to assign static port address to these servers and does it necessary to open these ports on firewall?
What are the advantages of assigning static port address instead of using "Auto assign"?
As per my understanding, request port of APS, FRS and other servers are used to communicate those with CMS. And CMS and all other servers are hosted on the same server. Then why do we need to open those ports on firewall in a server.
Appreciate your help and suggestions.
Thanks and Regards,
Aashutosh

Hi,
if you dont have a Firewall in between your Client PCs and the BOE Server you dont need to assign static ports. You only need this if a Firewall is controlling the communication between these two parts.
Most of the Services communicate only with the CMS - thats correct.
But if you use the BI LaunchPad only for vieweing and creating Reports like WebI you need to open the Port 8080 for the Application Server.
If you are using Front- End Clients for viewing and or editing Reports you need to open the CMS Port 6400 and assign a static Port to the IFRS and OFRS and open these ports too.
Regards
-Seb.

How to find mac address of a client computer in specified time and port in WIFI WCS Control system

how to find mac address of a client computer in specified time and port in WIFI WCS Control system

WCS record-keeping is very crude.
You'll get the time/date when the client authenticated. You'll get the local inside address but you'll need the router to translate the outside IP address and the port.
You will need a proxy server to determine what sites did a wireless client goes.

Static Port Address Translation 8.4

Hello Experts,
Is the static Port Address Translation is bidirectional in 8.4 ???
I have configured static port address translation for the 2 server with same Public IP for the port 80 and 23. The strange thing is when they initiate a connection to the outside world they are allowed access to the internet as they are not included in the Dynamic Port address translation pool.
object network inside network.
subnet 192.168.10.0 255.255.255.0
Can anybody help me.
Thanks

Hello Dears
Packet tracer for the Static port redirection server IP's.
ciscoasa(config)# sh conn
1 in use, 1 most used
TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:09, bytes 149, flags UIO
ciscoasa(config)# sh xlate
2 in use, 3 most used
Flags: D - DNS, i - dynamic, r - portmap, s - static, I - identity, T - twice
TCP PAT from inside:2.2.2.2 23-23 to outside:3.3.3.3 23-23
    flags sr idle 2:11:34 timeout 0:00:00
TCP PAT from inside:10.10.10.1 8080-8080 to outside:3.3.3.3 80-80
    flags sr idle 2:11:34 timeout 0:00:00
ciscoasa(config)# sh local-host
Interface management: 0 active, 0 maximum active, 0 denied
Interface inside: 1 active, 2 maximum active, 0 denied
local host: <2.2.2.2>,
    TCP flow count/limit = 1/unlimited
    TCP embryonic count to host = 0
    TCP intercept watermark = unlimited
    UDP flow count/limit = 0/unlimited
Conn:
    TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:21, bytes 149, flags UIO
Interface outside: 1 active, 1 maximum active, 0 denied
local host: <1.1.1.1>,
    TCP flow count/limit = 1/unlimited
    TCP embryonic count to host = 0
    TCP intercept watermark = unlimited
    UDP flow count/limit = 0/unlimited
Conn:
    TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:21, bytes 149, flags UIO
ciscoasa(config)# packet-tracer input inside tcp 2.2.2.2 28826 1.1.1.1 23
Phase: 1
Type: FLOW-LOOKUP
Subtype:
Result: ALLOW
Config:
Additional Information:
Found flow with id 15, using existing flow
Result:
input-interface: inside
input-status: up
input-line-status: up
Action: allow
ciscoasa(config)# sh conn
1 in use, 1 most used
TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:18, bytes 149, flags UIO
ciscoasa(config)# sh xlate
2 in use, 3 most used
Flags: D - DNS, i - dynamic, r - portmap, s - static, I - identity, T - twice
TCP PAT from inside:2.2.2.2 23-23 to outside:3.3.3.3 23-23
    flags sr idle 2:15:10 timeout 0:00:00
TCP PAT from inside:10.10.10.1 8080-8080 to outside:3.3.3.3 80-80
    flags sr idle 2:15:10 timeout 0:00:00
ciscoasa(config)# sh local-host
Interface management: 0 active, 0 maximum active, 0 denied
Interface inside: 1 active, 2 maximum active, 0 denied
local host: <10.10.10.1>,
    TCP flow count/limit = 1/unlimited
    TCP embryonic count to host = 0
    TCP intercept watermark = unlimited
    UDP flow count/limit = 0/unlimited
Conn:
    TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:36, bytes 149, flags UIO
Interface outside: 1 active, 1 maximum active, 0 denied
local host: <1.1.1.1>,
    TCP flow count/limit = 1/unlimited
    TCP embryonic count to host = 0
    TCP intercept watermark = unlimited
    UDP flow count/limit = 0/unlimited
Conn:
    TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:36, bytes 149, flags UIO
ciscoasa(config)# packet-tracer input inside tcp 10.10.10.1 31862 1.1.1.1 23
Phase: 1
Type: FLOW-LOOKUP
Subtype:
Result: ALLOW
Config:
Additional Information:
Found flow with id 17, using existing flow
Result:
input-interface: inside
input-status: up
input-line-status: up
Action: allow
Thanks

Remote debug application static port

Hi!
I wonder if is it possible to assing static port to remote debuggable application? I know that NI Service Locater manage the dynamic port that the application will be using, but than I have to open all the ports on firewall, because I don't know which port the remote debuggable application is using currently.
Thanks, andrej

Hi all,
has this ever been solved ?
I have the same problem. A stand-alone firewall prevents opening up the complete high port range.
So port 3580 has been opened and the NI service locator can be contacted, I see the debuggable applications on the remote machine.
But the Debuggable application gets a "random" port assigned by the NI service locator (?), which cannot be reached through the dedicated FW.
So can I restrict the NI service locator or Labview application to use a specific port ?
Thx & br
Martin

RTP: Specifying a Static Port

Similar Messages

Maybe you are looking for