Port Forwarding

Dogs · 25-11-2009, 15:42

Hi all....looking for a little help and advice.
I have my WGR614V9 set port forwarding on 12000 as custom service which works realy well but i also need access on 13000 but even with the settings showing as a custom service i cannot get access.
Have used a few port checkers but with no luck.
Even tried a zyxel 318s with the same result...service shows as active but with no port 13000 open again.
Now for the questions....is it the routers?...is it vm?
Any recomendations for a router that would work?

Thanks in advance

Acathla · 25-11-2009, 16:21

Have you also a software firewall running (ie Windows Firewall) that you haven't allowed the port through?

Dogs · 25-11-2009, 16:24

Sorry should have said...tested with the firewall off..on 3 pcs

Acathla · 25-11-2009, 16:51

Tricky to diagnose.

Make sure uPnP isn't using the port already. Turn it off, reboot and try again.
Any logs on the router that might indicate something? Is it seeing the initiation?

If it's identical in setup to your 12000 port I'm not sure what else it could be.

You definitely have something listening on port 13000 on the 'Server'?

Sounds dead basic things to check, but we all have 'blonde' moments so it's worth checking everything!

Dogs · 25-11-2009, 17:45

Your right, i'll check them out and post back tomorrow when i get a chance..thanks for the reply

Aragorn · 25-11-2009, 18:16

According to this, port 13000 is used by a known trojan. It is 'possible' that VM might be blocking it.

flamingeck · 25-11-2009, 21:58

First, check the server is listening on the pot 13000.

Command prompt, use the follow command (on the server).

Code:

netstat -an | find /i "13000"

It should show you if you are listening on that port.

Then attempt to telnet to your local IP on that port.

Code:

telnet serverip 13000

to see if it's accepting connections.

Then, from another pc on the same network.

Code:

telnet serverip 13000

and see if it connects.

If all of that works then it would suggest the port forwarding isn't working and it's not a local issue.

Always start diagnostics on the server, and work upwards to find out where the connectivity issues lies not backwards.

bomber_g · 26-11-2009, 15:17

Quote:

Originally Posted by Aragorn

According to this, port 13000 is used by a known trojan. It is 'possible' that VM might be blocking it.

some ports are blocked - although not many tbh.

usual ones are the netbios ports ( 135 137 and 139 ) also 445 is blocked, but I'm not really sure why

Ports blocked due to viruses / worms etc etc tend to get opened again when they are 'safe'

the easy way to find out if VM are blocking a port is to run a TCP trace on that particular port and see if it gets onto the network at all, if it's blocked the trace won't go any further than your modem

---------- Post added at 15:17 ---------- Previous post was at 14:52 ----------

just had a quick google and SQL slammer exploited a vulnerability on windows servers on port 445 years ago