D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: SSVegeta on August 25, 2010, 03:23:38 PM
-
Just one day to another the router stop forwarding the ports of Enable Remote Management no mater what port I put it's doesn't work.
I have two routers in my network and the problem that I found:
1. Lan to External IP with the port: doesn't work
2. Lan to External IP second router port: doesn't work
3. From another Network to External IP with the port: Work.
4. From another Network to External IP second router to the port: Doesn't work.
If I put the same port to another computer works ok.
If I put the IP of the second router in the DMZ is work ok also.
If I ping to any unused IP for example 192.168.1.200 the ping respond.
Reply from 192.168.1.4: Destination host unreachable.
When the IP 192.168.1.4 is in use.
Why the address change?
All the other port is working fine.
Already reprogram the Firmware without success.
Hope some one can help.
BR
-
I switch the router with a friend who was the same router of mine, because I believe that the problem is the router. But for me surprise I still have the same problem.
If you have any solution from Dlink please post it or PM to me I will appreciate it.
-
I switch the router with a friend who was the same router of mine, because I believe that the problem is the router. But for me surprise I still have the same problem.
If you have any solution from Dlink please post it or PM to me I will appreciate it.
Did the router work correctly with portforward when it was connected to your friend's PC?
Check for all: did you change the router firewall settings?
Double NAT is usually the problem when PF does not work...
http://www.google.nl/search?client=opera&rls=nl&q=router+double+NAT&sourceid=opera&ie=utf-8&oe=utf-8
Also you can check your multicast settings on the router ánd internet modem device (when applicable)
-
Did the router work correctly with portforward when it was connected to your friend's PC?
I didn't test it in their place.
Check for all: did you change the router firewall settings?
Firewall is disable.
Double NAT is usually the problem when PF does not work...
http://www.google.nl/search?client=opera&rls=nl&q=router+double+NAT&sourceid=opera&ie=utf-8&oe=utf-8
No the second router is AP mode
Also you can check your multicast settings on the router ánd internet modem device (when applicable)
Multicast on or off the problem persist, Cable Modem Arris nothing I can do, My ISP doesn't block the ports because if I use the same port to a computer or NAS is working flawless.
-
Ziggo client?
The first check is very important.
Firewall cannot be disabled, only set to a certain preset. What are the current settings?
-
Ziggo client?
The first check is very important.
Firewall cannot be disabled, only set to a certain preset. What are the current settings?
No Ziggo Clients
Firewall Settings
Enable SPI : Checked and Unchecked doesn't works.
Nat Endpoint Filtering
UDP Endpoint Filtering:
Endpoint Independent doesn't works
Address Restricted doesn't works
Port And Address Restricted doesn't works
TCP Endpoint Filtering:
Endpoint Independent doesn't works
Address Restricted doesn't works
Port And Address Restricted doesn't works
Anti-Spoof checking
Enable anti-spoof checking: Checked and Unchecked doesn't works.
DMZ Host
Not the problem
Application Level Gateway (ALG) Configuration
PPTP : Checked and Unchecked doesn't works.
IPSec (VPN) : Checked and Unchecked doesn't works.
RTSP : Checked and Unchecked doesn't works.
SIP : Checked and Unchecked doesn't works.
Thanks in advance.
-
A reboot after changes does some tricks sometimes...
By the way, forwarding works fine here.
-
Thanks, but still can not fix the problem.
I already sent an email to Dlink.
-
Setting up a virtual server might do the trick instead of PF.
-
I have tried both Virtual Server and Port Forwarding. Even DMZ. Doesn't do the trick. Router is behind a Cable modem (Ziggo Client), and the PC after it have for testing the firewall disabled. I don't get the picture anymore.
What ís strange: When I go to my own IP, it says: "Waiting for <IP>", and then I get a connection error. Strange, because normally it says "The server doesn't exist"...