up vote 0 down vote favorite
share [g+] share [fb]

I have replaced my old router with DIR-615 from D-Link, and now the port forwarding is so slow it makes the router practically useless for requests coming from outside of my network.

Accessing the router itself (admin UI) from outside is without any issues, no delay whatsoever. But when I try to access a service residing on any of the computers in my network from outside the requests take minutes and minutes. E.g. I can see source of my GWT-app main page, but loading additional CSS and JS files takes years.

If anyone could recommend any further diagnostics I should do to figure out what is happening it would be great.

Few notes:

  • happens with more services (web-app on Tomcat, viewing directory index via Apache)
  • it does not make a difference whether the service is hosted on wired or wireless PC
  • accessing the service on a localhost works fine, as does any 'inner' communication
  • turning off firewall on target PC does not make difference either (makes sense)
  • when I replace this router with the old one (both 192.168.1.1) everything works fine
  • I see nothing suspicious in the router's log
  • I believe I have the latest firmware (4.11)
  • DIR-615 sucks, it already died once completely

Update:

  1. After re-running the loading tests with buddy of mine (who resides in another city), it appears that the issue is only limited to access from my network using public IP. (Now the guy reports <5s, formerly it was 15-20-ish. But I assume now it was caused by some kind of temporary traffic spikes.)
  2. Latency of the linked resources is what kills the loading process, their download itself is fine. The tool shows 42s latency for 2kB CSS-file, while the d/l is 9ms. But given the above mentioned I should probably close this issue and maybe open a new one, with the issue re-formulated.
link|improve this question
71% accept rate
feedback

migrated from serverfault.com May 29 '10 at 8:57

This question came from our site for system administrators and desktop support professionals.

2 Answers

up vote 1 down vote accepted

For future reference, I think this one describes the issue. It is a network issue after-all. And given DIR-615 does not support NAT loopback I will have to 'solve' this using hosts, which is dirty but will have to do...

link|improve this answer
feedback
up vote 0 down vote

Try pinging the system and reply how long it takes.

link|improve this answer
Is it possible to ping a system that is hidden behind router? (In case you meant to ping the router, the router itself responds with no delay, as mentioned above.) – Jaroslav Záruba May 28 '10 at 2:07
Of course, just discover the IP address(network IP) of said system and ping it. If it's a Windows system, it's ipconfig, Linux is ifconfig. The system pinging the other must also be behind the router, as in, on the same network as the other. – Nik May 28 '10 at 10:19
But I was asking about a system hidden behind a router. (When the other machine is within the same network I wouldn't call it 'hidden behind' a router.) Also, as I said in note 3, my issue is only related to communication that comes from outside: "accessing the service on a localhost works fine". Pinging one system from another within the same network will tell me nothing, as it does not involve port forwarding. (It works fine BTW, as does everything else as long as it resides within my network: Apache, Tomcat, Remote Desktop, SVN...) Thanks anyways. – Jaroslav Záruba May 29 '10 at 1:27
Actually I have to admit the second paragraph of my question might be a bit misleading about when/where do I experience the issues. On the other hand port forwarding is usually related to communication that comes from outside, as ther is little need to use it for inner communication. Anyways, my apologies. – Jaroslav Záruba May 29 '10 at 1:34
Actually, pinging a system behind a router tells you a lot. Also, if it's a common service (like port 80 web services), try testing the times on how fast it responds from outside the router. You are working with residential hardware so it's to be expected, but it could be something else. – Nik May 29 '10 at 2:55
show 3 more comments
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.