Anyone got port forwarding workin on the......

Phil2008 · 15 Jan 2011 at 04:13

Belkin 300Mbps N+ Wireless (F5D8635UK4A)

Ive just got this router and I cannot get port forwarding working from the "Virtual Servers". Well actually I got it working yesterday after about 3hrs of messing with it, but its stopped working again. :mad:

Messiah Khan · 15 Jan 2011 at 09:29

Phil2008 said:
Belkin 300Mbps N+ Wireless (F5D8635UK4A)

Ive just got this router and I cannot get port forwarding working from the "Virtual Servers". Well actually I got it working yesterday after about 3hrs of messing with it, but its stopped working again.

You followed this guide;
http://portforward.com/english/routers/port_forwarding/Belkin/F5D8635au4A/F5D8635au4Aindex.htm ?

Phil2008 · 15 Jan 2011 at 11:43

Messiah Khan said:
You followed this guide;
http://portforward.com/english/routers/port_forwarding/Belkin/F5D8635au4A/F5D8635au4Aindex.htm ?

That dont really help cos you have to buy the software, but I have followed other guides without any success, Heres a few screenys,, see if you can see what Im doing wrong guys as its really doing my head in now :eek:

..........

KIA · 15 Jan 2011 at 13:12

What? You don't need to touch static routing.

As mentioned above, go to http://portforward.com/english/routers/port_forwarding/Belkin/F5D8635au4A/F5D8635au4Aindex.htm and select the appropriate Application guide. You don't need to pay a penny.

Phil2008 · 15 Jan 2011 at 14:19

fluff said:
What? You don't need to touch static routing.

As mentioned above, go to http://portforward.com/english/routers/port_forwarding/Belkin/F5D8635au4A/F5D8635au4Aindex.htm and select the appropriate Application guide. You don't need to pay a penny.

I just tried the static routing to see if it would make a diff, but it didnt

I didnt go through that site that you linked me to properly, but still no joy after doing that, as all the guides Ive looked at say the same steps :mad:

Anyway Ive just reset the router to factory setting and re entered all my details and settings, and hey presto the port forwarding is working, Who knows how long for tho.

Is it safe to leave a port open?

Edit: Ive just checked the port again on the net, and its closed again.....ARRRRRRRGGGGGGGHHHHHHH

I give up :mad:

Phil2008 · 15 Jan 2011 at 15:00

I think its a bug with the routers software as other ppl have reported the same problem. But Ive updated the firmware and still no joy.

Anyway I give up with it for a while, as Ive spent about another 2hrs trying to work it out!!!

Skidilliplop · 15 Jan 2011 at 15:04

Is your P2P definitely using just that TCP port not UDP or both?

Phil2008 · 15 Jan 2011 at 15:27

Skidilliplop said:
Is your P2P definitely using just that TCP port not UDP or both?

Im checking it using this site, as you cannot test the port in uTorrent

http://www.yougetsignal.com/tools/open-ports/

KIA · 15 Jan 2011 at 16:27

Phil2008 said:
Is it safe to leave a port open?

If it's just a port forward for uTorrent, yes.

Phil2008 said:
Im checking it using this site, as you cannot test the port in uTorrent

http://www.yougetsignal.com/tools/open-ports/

You can test the incoming port using uTorrent 2.2.

Options > Setup Guide > Untick Bandwidth > Run Tests

Phil2008 · 15 Jan 2011 at 19:13

fluff said:
You can test the incoming port using uTorrent 2.2.

Options > Setup Guide > Untick Bandwidth > Run Tests

Ah thanks...

Now its saying the port is open,, but I bet you if I try it again later, it will say its closed..... I do not get this at all :confused:

Skidilliplop · 15 Jan 2011 at 21:25

Just reading the uTorrent site uPnP is enabled by default so you shouldn't have to forward ports if you turn on uPnP on the router. Alternatively if you are statically forwarding ports uPnP could be interfering by trying to open and close ports itself.

Possibly worth trying turning uPnP off in uTorrent and see if the port stays open.

Phil2008 · 15 Jan 2011 at 21:28

Ok guys Ive found something out, and it a tad on the strange side, but with uTorrent running, uTorrent and http://www.yougetsignal.com/tools/open-ports/ says the port is open............. Now heres where it gets odd, when uTorrent isnt running http://www.yougetsignal.com/tools/open-ports/ says the port is closed.

So why is this? :confused:

Phil2008 · 15 Jan 2011 at 21:42

The uPnP is turned off on router and utorrent

Skidilliplop · 15 Jan 2011 at 22:28

That's normal. The application listens on a port. If there's no app then it's not listening.

When you connect to a port it doesn't connect to the router, it connects to the end device. The router simply forwards it on to the device, invisible to the devices communicating.

Phil2008 · 15 Jan 2011 at 23:11

Skidilliplop said:
That's normal. The application listens on a port. If there's no app then it's not listening.

When you connect to a port it doesn't connect to the router, it connects to the end device. The router simply forwards it on to the device, invisible to the devices communicating.

Ah, so basically your saying when a browser wants to access the port, the router keeps the port closed and a application can only let the router open the port?

That might explain why theirs quite a few complaints about the port forwarding on belkins routers and why it wont work on xbox and ps3? I guess you need to use the DMZ option with the xbox and ps3?

BloodyL · 15 Jan 2011 at 23:23

You shouldn't need to mess around, this is what uPnP is designed for, disable the manual port forward, enable uPnP in both the router and uTorrent, set uTorrent to use automatic port mapping and away you go.

Phil2008 · 15 Jan 2011 at 23:43

My idea was, if I ever had anymore programs that required a port to be open, I would set the prog to use the same one as utorrent uses,, then I know whats going on, so to speak.

Anyway At least the port forwarding thing is solved and now I know that accessing a port from ie/firefox wont open it. Thanks guys.

csmager · 16 Jan 2011 at 09:36

Phil2008 said:
Ah, so basically your saying when a browser wants to access the port, the router keeps the port closed and a application can only let the router open the port?

Not quite.

The router is always forwarding the port if it's set up that way. If the PC it's forwarding to has a firewall / there's nothing listening on that port, then the external port scanner isn't going to see anything.