• March 28, 2024, 07:46:01 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 2 [3]

Author Topic: Port Forwarding , Connection refused or firewall blocking ..?  (Read 50716 times)

gsundeep

  • Level 1 Member
  • *
  • Posts: 19
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #30 on: December 19, 2014, 10:43:43 AM »

Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #31 on: December 19, 2014, 11:00:29 AM »

For a first test it would be enough to specify your web server's address w.x.y.z as source range:  w.x.y.z - w.x.y.z
Logged

gsundeep

  • Level 1 Member
  • *
  • Posts: 19
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #32 on: December 19, 2014, 11:08:09 AM »

For a first test it would be enough to specify your web server's address w.x.y.z as source range:  w.x.y.z - w.x.y.z

hey .. do you have a team viewer ..i  want you to connect my pc and check whether any worng is there . please help me to solve this problem
 
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #33 on: December 19, 2014, 11:19:03 AM »

I would recommend that...Hope PT can help you figure it out.  ;)
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

gsundeep

  • Level 1 Member
  • *
  • Posts: 19
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #34 on: December 19, 2014, 12:55:34 PM »

Thanx PacketTracer for your help  :)
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #35 on: December 19, 2014, 01:03:39 PM »

Hope the results were good?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #36 on: December 19, 2014, 04:27:33 PM »

Hi,

we figured out, that the DIR-600L router sits behind another routing/NAT-ing device that is under exclusive control of the ISP. Hence local devices are not reachable from the Internet, because it is not possible to configure needed port forwardings inside the ISP controlled device. In fact the WAN interface of the DIR-600L only has a private address out of 172.16.0.0/12 and not the public address 175.101.67.138 we assumed it to have in the first place.

This is what I personally messaged to gsundeep, but I think it is neutral enough to post it here again:

Quote
your situation is in principle as described here where you have no access to Router #1 which is under exclusive administration of your ISP only (hence you can't configure port forwardings inside Router #1). This is also called "NAT444". To overcome this situation a possible solution is to use a VPN (based on IPsec or e.g. OpenSSL) that terminates on a box inside your LAN (your local VPN gateway) and on an outside machine that has a public internet IP address (that VPN tunnel must be initiated outgoing by your LAN box and kept alive via perodically sent keep alive packets).

Traffic that shall reach your LAN from the Internet would be send to the public IP address of that external machine (possibly resolvable via DDNS), and that machine would do a port forwarding (a DNAT, where it translates the public destination address and port to the private address and port of a box inside your LAN) and send the modified packets through the VPN to your LAN, this way traversing the two NATs via the tunnel where NAT happens only to the outer IP addresses of the tunneled packets which is possible due to the NAT sessions that exist in both NAT instances, because the tunnel was initiated in outgoing direction.

When the packets arrive at you local VPN gateway, they are decapsulated and routed to the local destination. In your LAN you would have to tell all devices, that shall be reachable from the Internet, to use the local VPN gateway as their default gateway (which also means, that these devices will access the Internet via the VPN tunnel only).

You have two choices to find either a service provider who operates the external VPN gateway on your behalf (so you will probably have to pay for it) or you are able to operate an external device of that kind of your own and configure it accordingly.

A third choice is to use IPv6 which brings publicly accessible IPv6 addresses to your LAN (access from the outside just blocked by IPv6 firewall functionality inside your DIR-600L router but no more by NAT). So ask your ISP for IPv6 Internet access bundled with your present IPv4 only access. Of course any client sitting in the Internet that whishes (and is allowed to) access your LAN must be IPv6 capable and have an IPv6 Internet access.

What you suffer from in the moment are the negative effects of IPv4 address exhaustion (especially critical in the APNIC region, India belongs to) and the not yet happened IPv6 pervasiveness.

PT
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #37 on: December 19, 2014, 04:32:33 PM »

Thanks PT, I was wondering about that...i had asked about it.

Might try the 600L router in the DMZ on the main host router as a suggestion and if the ISP modem can't be bridged.

Thanks for posting.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #38 on: December 19, 2014, 04:49:50 PM »

Hi Furry,

as far as I understood the scenario there is no modem connecting to the ISP. Instead the DIR-600L seems to be connected to the "main host router" (I would call it a Carrier-grade NAT (CGN)) via some other L2 technique (e.g. Fiber). Putting the DIR-600L to the DMZ of the CGN will probably be impossible (as any other special configuration like port forwardings) because ISPs operating such CGNs will most probably not allow/support subscriber specific device configurations on those CGN devices.

PT
« Last Edit: December 19, 2014, 04:54:30 PM by PacketTracer »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding , Connection refused or firewall blocking ..?
« Reply #39 on: December 19, 2014, 05:02:10 PM »

Ah ok. Thanks for the info and I understand now. Hope something can be worked out.

One think the OP can do if native remote connection fails, Use Teamviewer.  ;)
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.
Pages: 1 2 [3]