Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mendonsy]

Is there a way to map 3 unique incoming ports to the same port # on 3 different IP addresses??
Example: incoming port 5000 to 192.168.0.100 port 21
              incoming port 5001 to 192.168.0.101 port 21
              incoming port 5002 to 192.168.0.102 port 21

[FurryNutz]

Check the user manual for Virtual Server or Port Forwarding options? Not sure if port 21 can be mapped all at once to different IPs.

[mendonsy]

I have not found anything that will allow an incoming port to be mapped to a different port number. It appears that I can map any incoming port to an IP address, but nothing that will allow me to change the port number.
FurryNutz .... Is there an active email address for D-Link tech support for the DSR250N??
I tried to get there through the D-Link website cut it will not let me. It just continues to loop back to the automated answers bot that doesn't understand the question and presents me with a list of FAQ's that will not open.

[FurryNutz]

Best way to get to D-Link support is to phone contact your regional D-Link support office for immediate help there. I found that email doesn't provide the level of support needed.

Let us know how it goes.

[simpsonehh]

even though the post is old.  this info may be useful for others.

port redirect

running the 2.01_WW code on DSR-250N

security > custom services
Add a new service
   give it a descriptive name for reference (no spaces)
   select tcp or udp
   enter start and finish ports as the same
      (for example TCP 55505)  <-- we will redirect this to remote desktop TCP 3389 soon.
   save
select Security > Firewall rules
Add
from zone - insecure wan
to zone - secure vlan  <-- unless you have something else set for your client
available vlan - default <-- unless you have something else set for your client
service - select your new service
action - allow
source hosts - any
optional - set log to always
set the IP of your internal server
TURN ON enable port forwarding
translate port = 3389 (or whatever number you need to go to)
external IP = WAN
Save

Make sure that it is ENABLED

[FurryNutz]

Thank you for posting and the feed back and information. Hope it helps future users.

even though the post is old.  this info may be useful for others.

port redirect

running the 2.01_WW code on DSR-250N

security > custom services
Add a new service
   give it a descriptive name for reference (no spaces)
   select tcp or udp
   enter start and finish ports as the same
      (for example TCP 55505)  <-- we will redirect this to remote desktop TCP 3389 soon.
   save
select Security > Firewall rules
Add
from zone - insecure wan
to zone - secure vlan  <-- unless you have something else set for your client
available vlan - default <-- unless you have something else set for your client
service - select your new service
action - allow
source hosts - any
optional - set log to always
set the IP of your internal server
TURN ON enable port forwarding
translate port = 3389 (or whatever number you need to go to)
external IP = WAN
Save

Make sure that it is ENABLED

[DBrowne]

even though the post is old.  this info may be useful for others.

port redirect

running the 2.01_WW code on DSR-250N

security > custom services
Add a new service
   give it a descriptive name for reference (no spaces)
   select tcp or udp
   enter start and finish ports as the same
      (for example TCP 55505)  <-- we will redirect this to remote desktop TCP 3389 soon.
   save
select Security > Firewall rules
Add
from zone - insecure wan
to zone - secure vlan  <-- unless you have something else set for your client
available vlan - default <-- unless you have something else set for your client
service - select your new service
action - allow
source hosts - any
optional - set log to always
set the IP of your internal server
TURN ON enable port forwarding
translate port = 3389 (or whatever number you need to go to)
external IP = WAN
Save

Make sure that it is ENABLED

Just checking in to say that this helped me a lot.
I was initially on the V2.11 Firmware, which when adding a new custom service now requires 2 sets of ports (source and destination). I couldn't get this configuration to work, so I ended up downgrading to V2.01. As implied in the quote above, V2.01 only takes a single port range (source), and the destination port is determined by the Port Forwarding option in the firewall rules. Now it works flawlessly.

[FurryNutz]

What were you configuring for the local and destination ports when you were using 2.11?
It should have worked...If you configured the right destination port. Local and Destination ports can be configured to use the same port numbers I believe in some configurations.

even though the post is old.  this info may be useful for others.

port redirect

running the 2.01_WW code on DSR-250N

security > custom services
Add a new service
   give it a descriptive name for reference (no spaces)
   select tcp or udp
   enter start and finish ports as the same
      (for example TCP 55505)  <-- we will redirect this to remote desktop TCP 3389 soon.
   save
select Security > Firewall rules
Add
from zone - insecure wan
to zone - secure vlan  <-- unless you have something else set for your client
available vlan - default <-- unless you have something else set for your client
service - select your new service
action - allow
source hosts - any
optional - set log to always
set the IP of your internal server
TURN ON enable port forwarding
translate port = 3389 (or whatever number you need to go to)
external IP = WAN
Save

Make sure that it is ENABLED

Just checking in to say that this helped me a lot.
I was initially on the V2.11 Firmware, which when adding a new custom service now requires 2 sets of ports (source and destination). I couldn't get this configuration to work, so I ended up downgrading to V2.01. As implied in the quote above, V2.01 only takes a single port range (source), and the destination port is determined by the Port Forwarding option in the firewall rules. Now it works flawlessly.
[/quote]

[DBrowne]

What were you configuring for the local and destination ports when you were using 2.11?
It should have worked...If you configured the right destination port. Local and Destination ports can be configured to use the same port numbers I believe in some configurations.

I wanted to do a direct pass-through on port 85 (so accessing [router ip]:85 forwards through to [device ip]:85)
I configured the custom service as:
Name: MyCustomService
Type: TCP
Port Range:
  Source start: 85
  Source end: 85
  Destination start: 85
  Destination end: 85

I configured the firewall rule:
From: WAN
To: LAN
Service: MyCustomService
Action: Always Allow
Source Hosts: Any
Internal IP: [device ip]
Enable Port Forwarding: On
Translate Port Number: 85
External IP Address: WAN

This didn't work. However changing the Service to HTTP forwarded the connection from external port 80 to device port 85 as you'd expect. This makes me think it was something in the configuration of the service.

[FurryNutz]

Makes me think a mis-configuration was a miss when you had v2.11 installed as well. 

[DBrowne]

Makes me think a mis-configuration was a miss when you had v2.11 installed as well. 

Well I had it configured exactly as described above with no avail. I also tried a bunch of variations on this, including completely omitting destination ports in the Custom Service configuration (to try and emulate the v2.01 configuration options). Downgrading to v2.01 and configuring it exactly the same worked fine. Given that OP of this thread http://forums.dlink.com/index.php?topic=65313.0 has had a very similar issue I'm inclined to think there's something else going on here.

Would you have configured it any differently to how I described above?

[FurryNutz]

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[certinet]

Created a user just to post the answer. I contacted dlink by chat. To make Custom Services work with firmware 2.11_WW, just don't put any information in Sources, just Destination.

Thanks

[FurryNutz]

Awesome information. Thank you for posting this information. Hope it helps future users while using v2.11WW

Created a user just to post the answer. I contacted dlink by chat. To make Custom Services work with firmware 2.11_WW, just don't put any information in Sources, just Destination.

Thanks