Orbi WiFi 7 RBE973

Re: Port Forwarding Continued...

Andrzej000
Aspirant

Port Forwarding

 
 
 
260/5000
 
 
Good morning
I have a problem with the SRX5308.
I can not connect to RDP, VNC & ... via WAN.
Simply redirecting ports does not work.
Apparently I'm doing something wrong.
RDP, VNC & ... operate locally correctly.
Please ask for directions as I denied.
Regards

Picture 1

Picture 2

Picture 3

Picture 4

Model: SRX5308|PROSAFE Gigabit Quad WAN SSL & IPSEC VPN Firewall
Message 1 of 7

Accepted Solutions
Andrzej000
Aspirant

Re: Port Forwarding Continued...

 
 
 
 
 
 
230/5000
 
 
Problem solved
Incorrect port translation was performed.
It should be done exactly on the reverse. As a service port we add port 10006, but we translate it into a 3389 rule, ie RDP port.
The previous router was suggested
 
Regards
And I wish you many successes

View solution in original post

Model: SRX5308|PROSAFE Gigabit Quad WAN SSL & IPSEC VPN Firewall
Message 6 of 7

All Replies
DaneA
NETGEAR Employee Retired

Re: Port Forwarding

Hi Andrzej000,

 

Welcome to the community! 🙂 

 

Was this working fine before? 

 

Kindly access the online port scanner here then check if ports 3389 and 5900 is really opened.  If it shows "online/reachable!" it means that the port is really opened. 

 

 

Regards,

 

DaneA

NETGEAR Community Team

Message 2 of 7
Andrzej000
Aspirant

Re: Port Forwarding

Good morning
Thank you for the quick reply.
These ports on the devices are active.
I connect to the devices (on the 5900 and rdp standard port 3389) without problem locally or through the WAN but the old router (Intellinet).
Port scan on the WAN side of the SRX5308 router (http://www.t1shopper.com/tools/port-scan/)- no ports open.
On the WAN side, I think it should be open ports that redirect traffic from ports 5900 ie in my case eg 10006.
I connect seamlessly through WAN to the router (using https: //) to manage it.
Since this location has two links to the other one, the other router is connected all the time and through it I have access to the local network. And I also manage roter SRX3508 through local network.
I do not quite know where to look for a solution to the problem.
With this router I have contact only for the first time so probably somewhere I make an error.
If I could pinpoint an error, I can share other current settings.
Regards

Message 3 of 7
Andrzej000
Aspirant

Re: Port Forwarding

Was this working fine before?

No. This is a new installation.

My intention is to implement IP multicasting on the local network and VPN implementation between the (the same SRX5308) two routers through the WAN.

Message 4 of 7
Andrzej000
Aspirant

Port Forwarding Continued...

I reset the router to factory settings and in these settings the only action I did was to set the WAN1 port and set
security /Services

only:

RDP 3389 & VNC 5900.

&

LAN WAN Rules (ALLOW always)

Port RDP

Lan addres 192.168.1.1 redirected to 2000 port.

The stubborn router only opens one port 443 (SSL access to the router)

The only opened port is the access port for the router, eg 443 via WAN.

What am I doing wrong?

Regards

 

Message 5 of 7
Andrzej000
Aspirant

Re: Port Forwarding Continued...

 
 
 
 
 
 
230/5000
 
 
Problem solved
Incorrect port translation was performed.
It should be done exactly on the reverse. As a service port we add port 10006, but we translate it into a 3389 rule, ie RDP port.
The previous router was suggested
 
Regards
And I wish you many successes
Model: SRX5308|PROSAFE Gigabit Quad WAN SSL & IPSEC VPN Firewall
Message 6 of 7
DaneA
NETGEAR Employee Retired

Re: Port Forwarding Continued...

@Andrzej000,

 

Thanks for the update.  I'm glad to know the you were able to figure it out and solved the problem. 🙂 

 

Since your concern has been resolved, I encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The NETGEAR Community looks forward to hearing from you and being a helpful resource in the future!

 


Regards,

 

DaneA

NETGEAR Community Team

Message 7 of 7
Discussion stats
  • 6 replies
  • 8120 views
  • 0 kudos
  • 2 in conversation
Announcements