D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-825 => Topic started by: Twerthi on January 05, 2009, 01:49:36 PM
-
I'm having a problem where port forwarding stops working. I have a Ventrilo server that I use when I play Warhammer Online with my friends. What seems to happen is that the port forwarding rule that I set up simply stops working. I've tried rebooting the router, power cycling the router, and even turned off the router over night to see if it worked. The only thing that seems to make it work again is to change the IP address it's forwarding to (which requires a reboot of the router) then change it back again.
The computer that's it's fowarding to is DHCP with the IP address reserved for that MAC address so the computer should get the same IP every time, which it does.
-
How do you have the Ventrilo forwarding set up?
-
I'm not sure I understand the question. The Ventrilo server listens on port 3784. In port fowarding, I have the TCP and UDP (not sure if I need the UDP, but I have it set anyway) 3784 forwarding to the IP of my Ventrilo server. The Ventrilo server is set up with DHCP reservation so that it's IP won't change.
The schedule is set to Always On, so it's not a schedule interfering with it.
-
Twerthi,
Try to create a virutal server rule and disable the port forwarding rule you created.. Also can you telnet the server?
-
It was my understanding that the only difference between Virtual Server and Port Forwarding is that you can do a range of ports with Port Forwarding whereas you cannot with Virtual Server? I'll give it a shot anyway when I get home, but if it works, then it would lead me to believe that there is still an issue with Port Forwarding.
I am able to telnet to the server, but I do not remember when I tried if I'd already performed my work around or not.
-
It was my understanding that the only difference between Virtual Server and Port Forwarding is that you can do a range of ports with Port Forwarding whereas you cannot with Virtual Server? I'll give it a shot anyway when I get home, but if it works, then it would lead me to believe that there is still an issue with Port Forwarding.
I am able to telnet to the server, but I do not remember when I tried if I'd already performed my work around or not.
If Ventrilo uses UPNP, is it possible that Ventrilo is trying to configure the port (which you manually configured) via UPNP? If so, I'd prefer to disable UPNP support in Ventrilo since UPNP port openings are harder to see and harder to persist.
What is the work-around?
Finally, before and after the port-forwarding stops, take a look at your Status - Internet Sessions screen. You should see:
192.168.0.199:3784 77.66.55.44:3784 *.*.*.*:* UDP - - 128 -
192.168.0.199:3784 77.66.55.44:3784 *.*.*.*:* TCP - - 128 -
or maybe -- not sure which would be right
192.168.0.199:3784 77.66.55.44:3784 *.*.*.*:* * - - 128 -
(where 192.168 is your LAN machine and 77.66. is your WAN port)
-
The work around is to change the IP that it's forwarding to, then change it back. (Actually, the first change fixes the issue, I tested by having two machines running Ventrilo server and have been bouncing back and forth when the issue presents itself).
I do not know if Ventrilo UPNP (Universal Plug and Play?). Is there a way to tell?
I'll have to do check the Internet Sessions when I get home. I changed it from Port Forwarding to Virtual Server last night. I noted that Virtual Server settings don't require a reboot like the Port Forwarding does ... don't know if it means anything, but it was something I noticed. Before I went to bed last night, it was working. I will test it again to see if it's still working when I get home. If it is, then either I'm doing something wrong with Port Forwarding or there is something wrong WITH Port Forwarding.
-
I checked last night and it was working with the Virtual Server. I will check tonight to see if it's still working, but this leads me to believe that something is wrong with port forwarding.
-
Using the Virtual Server seems to have solved the issue of being able to successfully run my Ventrilo server. However, I think there may be an issue with Port Forwarding in the current firmware release.
-
What did you have your port forwarding rule set to? and How is it set to now on Virtual server?
-
Virtual Server is set up with port 3784 and the Both option chosen (for both TCP and UDP).
Port fowarding was set up the same way with 3784 in the TCP textbox and the UPD textbox.
In both cases, schedules were set to Always and Inbound Filter was set to All.
-
Twerthi,
I'm using a DIR-825 at home and I just tried to replicate the issue using remote desktop.. Currently I had virtual server rule for RDP Port 3389 TCP. disabled the rule and applied it to port forwarding and was able to remote into my PC at home. I have a camera at home but it is not connected at the moment. I will see if the router suffers from the same issue. But as it stands right now both port forwarding and virtual server rules work for me.
-
Ru-Fi-Oh,
For me, the Port Forwarding worked for a certain amount of time. I have not done further troubleshooting on how long that time period is since getting my Ventrilo server functional.
So, what I'm saying is that the Port Forwarding did work, but stopped working after 12-48 hours (I think, I play Warhammer Online Mondays and Wednesdays, I got it working on a Monday and by Wednesday it was broken again).
-
Got it.. thanks for the update.. I'll continue testing it out with one of my DCS cameras and see if I can catch what you're seeing
-
I'm curious how your test is progressing?
-
So far I have not been able to replicate the issue. It appears to be working with the camera I have setup. I will keep the port forwarding rule and have the camera running for atleast a week and see if I notice anything.
-
Hmm, I've a camera as well so I'll try it again without Ventrilo ... perhaps it was something with Ventrilo it doesn't like.