A port doesn't "self-exist", it must have a service running that
creates or "activates" the port. In a dedicated Firewall NAT Device
the Operating Systems of those things are designed to do that for you.
I don't think the NAT abilities built into RRAS in Windows will do
that.
It has been a while since I looked into this but I thought I remember
it requiring an identical service running on the NAT box to make it
work. It was typically done with Web or SMTP,...which Windows already
has so that wasn't a problem.
Here's what I suggest you try....
Run a "dummy" copy of the same application on the server itself. Then
NAT will redirect the traffic to the "real" copy on the workstation
and the "dummy" copy running on the server will never get the request.
The "dummy" will only serve to activate the port so that RRAS/NAT can
use it.
Of course I could have been day-dreaming and be totally wrong.
--
Phillip Windell [CCNA, MVP, MCP]
WAND-TV (ABC Affiliate)
www.wandtv.com
"Perquiaga" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> HI!
> I've set up the port/service in NAT settings to forward an incoming
request
> in an special port used by an application witch i need to be
accessed from
> the internet, being installed on an internal workstation.
> Everything is done, but it dows not open the port on the server. The
> settings in NAT indicates everything is OK. Incoming and uotgoing
port are
> the same, the protocol is the same the application uses UDP, and the
private
> ip the workstation has.
> Please, how do i open the port ?
> The portqry keeps saying NOT LISTENENING and I'm getting mad.
> How do i get it to start listening ?
>
>
Similar Threads
Linear Mode
