Jump to content
Comet Forums

UDP Port still blocked


Recommended Posts

Hi,

In the Statistics page of my Bitcomet, it is saying that the TCP listening port 60000 was opened by my router and the UDP Port was blocked by my router still. I am using Bitcomet Version 1.18 stable with windows vista, I have DSL using a router which acts as a network gateway. I have configured both windows firewall and my actual router-Dlink Model DVA3810 to port forwarding as per the guide and still the statistics show that the UDP is being blocked. As per the guide I do have the port mapping off. Why is the one port still blocked?

Thanks

Link to comment
Share on other sites

Hi,

Thanks for your reply. Yes I do have it specified for both and nothing seems to work. However, my router in the security section is noting a lot of blocking of ICMP which I'm not sure if that has anything to do with this but seems to be new since the port blocking

Link to comment
Share on other sites

Things are a bit slow today, but when I was able to check, I noticed that this model of router appears to require that you set two rules, one for each protocol. That might not be accurate, or it might be an older version of the firmware. If you must, you must.

Ping-blocking isn't usually an issue for most people, and I really wouldn't worry about ICMP settings.

It is odd, though, particularly if you haven't changed anything. You may want to reset the router to its defaults and configure it again, to make certain all is as you think it is.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...