<div>
I know this sounds like a silly question, but did you actually check the &quot;Enable&quot; box?<br />
<br />
In SETUP | FORWARDING | SERVICE MANAGEMENT you should see your custom fowarding service. If you select it is the &quot;Enable&quot; box checked?<br />
<br />
MO
</div>


<div>
Does the internal device that's listenting on UDP 6000-6002 have any firewall enabled?<br />
<br />
MO
</div>


<div>
No<br />
<br />
Its a Win XP machine, firewall is disabled, &nbsp;I can ping it from anywhere on the network and it can ping the internal IP (read = gateway) on the firewall.<br />
<br />
Do you know how I can test to see if those ports (6000, 6001, 6002) are available on the workstation.<br />
<br />
I want to make sure that we can get from the workstation to the firewall over those ports, making sure they are functional.
</div>


<div>
run a netstat -aon | more on the machine from a command line to see if any services are even listing on those ports. If you don't see any services listening then they are either the wrong ports or the service/application isn't running on the machine.<br />
<br />
MO
</div>


<div>
When the application runs, user logs in to a test site and ports DO show up in netstat, but don't show up from outside the firewall if you use <a href="http://yougetsignal.com" rel="ugc">http://yougetsignal.com</a><br />
<br />
<br />
<br />

</div>


<div>
When you checked and verified that the system in question is listening on those ports (6000-6002) did you verify that it's the correct Process ID? Simply compare the process ID from netstat with the processes in task manager. Make sure to add the PID column to you view. If they are associated to the correct process then perhaps something is wrong with the router. Try and setup a different port forwarding rule to the same machine and test that, e.g. RDP (TCP3389).<br />
<br />
MO
</div>


<div>
Here is a simple way to test your ports on that computer....and follow this to isolate the issue completely.<br />
<br />
a) On the command prompt, &nbsp;do Telnet 192.168.0.xxx &nbsp;6000 &nbsp;from within your LAN. &nbsp;If this gives you a blank screen, without any error message then the port is open. Try same for all the ports.<br />
b) Validate (a) by doing telnet through port 3389 just to make sure that the test works.<br />
c) Do the test from the WAN to see if the router let's the port go through.<br />
<br />
What modem do you have? You are sure you have a modem and not one of the basic router/firewalls provided by ISPs? &nbsp;Have you successfully passed any ports through your linksys before? <br />
<br />
By the way, feel free to type your complete internal(private class C) IP address here. There is no security risk involved with that. &nbsp;It is your WAN IP that you shouldn't share carelessly. 
</div>


<div>
Bokis, these are UDP ports. Telnet will not work. If you read my post I already suggested testing a different port, e.g. RDP on TCP3389. Thanks for repeating that same information though.<br />
<br />
As Bokis comments, it would be good to verify your WAN configuration. How's the ISP's router or modem setup? Needs to be Bridged if you're using the RV082. Is your RV082 set with static IP information or is it dynamic?<br />
<br />
MO
</div>


<div>
MO, sorry for failing to acknowledge your first mention of port 3389......I was only using it in the context of my suggested test.<br />
Having said that, I still think doig the following command on a comman prompt will verify if the port is open or not.<br />
<b>Telnet </b>&lt;<i>IP address of computer</i>&gt; &lt;space here&gt; &lt;<i>port number here</i>&gt;<br />
&nbsp;will work regardless of udp or tcp.<br />
I have customer who uses Open Table Software and I had to pass UDP port 61031 through the firewall. I just tested again before doing this post and it works albeit gives you a few meaningless characters on the prompt unlike like a TCP port which gives you a clean blank screen. &nbsp;<br />
<br />
Good point on the bridging suggestion. For DSL line modems that do PPOE with or without authentication, it is a smooth solution. However, for those large routers provided by say verizon, all I would do is put my linksys on the ISP's LAN with a fixed IP and then make sure that IP is on the ISP's DMZ.......passing everything through. That is another story if we establish that this is in fact the case here. I am on standby for feedback from tech911.
</div>


<div>
Sorry for the delay in responding.<br />
<br />
1.) Router/Firewall DOES pass traffic over 3389 through the firewall and using a port scanner from the outside, one can see that 3389 is open and it works.<br />
<br />
2.) Same test with 6000, 6001, 6002 does not work.<br />
<br />
3.) &nbsp;In my config, 3389 is routed to a server inside and I can connect no problem.<br />
<br />
4.) &nbsp;The thing I find most interesting is that the connection to 6000 ~ 6002 begins from the application inside the firewall, thus it is Solicited traffic and should go through, but I its not, which I find very odd. &nbsp;I am going meet with my client and ask that we get the software vendor involved.<br />
<br />
I will post my results shortly.
</div>


<div>
If you make a connection from inside the gateway firewall to the host system and all is well, but it doesn't work from outside the network then the focus is on the Linksys or the ISP. ISP's will sometimes block non standard ports. Have you checked with your service provider to confirm? The only other thing I can think of is replacing the Linksys just for testing to see if the problem persists even with different equipment.<br />
<br />
MO
</div>


<div>
I am going to this client site tomorrow, will advise once I have a view of the application and a status on site.
</div>


<div>
I think it might be the application, we are going to test, stand by...
</div>


<div>
I may have missed it but I don't see where it is confirmed that those ports are open and reachable from within the LAN.<br />

</div>


<div>
You already did an internal telnet test to the system on ports 6000 - 6002 as suggested in an earlier post, right? I think I had you verify that the system was listing on the correct ports first and then Bokis suggested that you telnet to that system from the LAN using those ports. I'm not sure we got a definitive answer on whether you verified that the listing ports matched the correct application process or that the telnet from the LAN worked.<br />
<br />
Can you confirm?<br />
<br />
MO
</div>


<div>
We really didn't find a solution, we just went a different direction.
</div>


<div>
Hmmm, so your accepted solution is an &nbsp;unanswered question that MO asked you about previous things we all, in separate comments, pointed you on how to isolate the issue?
</div>


<div>
<div class="content wysiwyg-content">
Have Linksys RV082<br />
Client requested that port 6000~6002 Via UDP, &nbsp;be port forwarded to machine on inside of firewall.<br />
<br />
I did the following<br />
Created Service called &quot;AudioApp&quot; Port range 6000~6002 UDP and forwarded it an internal IP 192.168.0.xxx<br />
<br />
When the user tries to run the Audio Application is says the ports are not mapped. &nbsp;When I check the ports from the outside(Public Interface of the router), it says they are closed.<br />
<br />
What am I doing wrong, how can I check to see if the ports work from the user's machine to the firewall on the inside.<br />
<br />
Thanks,<br />
<br />
C
</div>
</div>


Have Linksys RV082
Client requested that port 6000~6002 Via UDP,  be port forwarded to machine on inside of firewall.

I did the following
Created Service called "AudioApp" Port range 6000~6002 UDP and forwarded it an internal IP 192.168.0.xxx

When the user tries to run the Audio Application is says the ports are not mapped.  When I check the ports from the outside(Public Interface of the router), it says they are closed.

What am I doing wrong, how can I check to see if the ports work from the user's machine to the firewall on the inside.

Thanks,

C

Router Config Linksys RV082

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network security consists of the policies adopted to prevent and monitor authorized access, misuse, modification, or denial of a computer network and network-accessible resources. Network security involves the authorization of access to data in a network, and covers a variety of computer networks; conducting transactions and communications among businesses, government agencies and individuals. Networks can be private, such as within a company, and others which might be open to public access.