Port forwarding on the Thomson Gateway TG789vn - Page 2

Unfortunately that did not do it either.

On March 25 2013 05:18 LuvMyCap wrote:


Hmmm. When you put the numbers, Example: 22.0.0.150 (or whatever your number is) on the address bar of your browser what does it do or happens or nothing happens?

On March 26 2013 03:13 fabiano wrote:
Looks like I've the same router as you, here is my config:

On March 26 2013 04:11 RouaF wrote:


Ok, first looks like you are using both wired and wi-fi at the same time. To keep things simple you should probably start by shutting wi-fi on your comp. Then you have to give us screenshots of :

- The "Game or application " page (the one which you created)
- The "Device" page

On March 26 2013 11:34 quirinus wrote:
try putting it 6112-6119 on both tcp and udp, try to turn off firewall on your antivirus
did you put a static ip in your windows? if you haven't, the local ip that you're using for port forwarding will change from time to time and fuck it up.

is wireless enabled and ethernet disabled? as someone suggested, try just one of them, preferably ethernet.

wtf I don't see the ip address on any of the router pages, is it on some other page? get a screen shot of that as well.

On March 26 2013 17:47 RouaF wrote:


Good. The port part looks ok (but as suggested you could extend it to 6112-6119 just to make sure).
What is still prolly wrong tho is the "device" part. We need a screen of the "assign a game or application to a local network device"

On March 27 2013 02:47 RouaF wrote:
Hmmm then choose user defined and put 192.168.0.2 in there (in place of "Thomson ....")

On March 27 2013 10:09 Bakuryu wrote:
can u edit this: Game or application page, the one that i made: http://puu.sh/2nV5h
trigger protocol = protocol (so top one is TCP and bottom one is UDP)
trigger port = 6112
(this one should not harm u anything at all, only do good)

what are the names of the devices u can choose in the dropdown menu of "Device" in the "assign a game or application to a local network device" page.

did u confirm that u are connecting to starcraft at port 6112?
(log into iccup for example, go cmd, type "netstat -n", search for the remote adress ip with ":6112" at the end, it could be theoretically that 6112 is blocked by different program, so bw will have 6113 or so.)

On March 28 2013 07:48 quirinus wrote:
You should just install TeamViewer and let someone try to fix it.

For static local ip, go to start, control panel, if it's in view by category - choose "view network status and tasks", change adapter settings, there should be a wireless network connection and local area connection there. You can disable wireless by right clicking on it and disable, enable local area connection if it's not enabled. Right click LAN (local area connection), properties, click on the *text* of "Internet protocol version 4 (TCP/IPv4)" so that whole row is selected. Click properties. "Click on Use the following IP address:" so it's selected. Under IP address put 192.168.0.x (where x is from 2 to 255) - this is your local static ip address that you enter in the router when you portforward (router needs to know what's the network address of the computer so it can forward to the right place). Default gateway should fill on it's own when you click (255.255.255.0), and in default gateway put 192.168.0.1 (that's the IP address of the router, you also use this one to access the router via the browser). For DNS try to leave it on automatically if it lets you, otherwise just leave it blank. Turn on validate settings upon exit. OK, OK. Right click LAN, status, Details... It should say IPv4 Adress 192.168.0.x (where x is from before). You can also check with netstat, but it should say the same. If you're using wireless, it's done pretty much the same way.

If the address isn't static, but automatically obtained, it will change from time to time, so if you use one on the router page, and then it changes, you'll need to update the portforward address all the time when it happens. I don't know when it changes, but it's not thaaaat often. Probably when the router restarts or resets.