Technicolour router woes

[BUDFORCE]

Hi guys,

I thought I would start this thread in a last ditch effort to try and save this game before I give up on it completely.

Basically I have a technicolour TG589vn v3 router. This router is know for being a bit over sensitive with certain ports that games use, and I had to give up previously with a game called Warframe for similar issues.

I am trying to play Destiny 2 and I am having similar issues, I found a most relevent thread as below:

https://www.bungie.net/en/Forums/Post/231008613

However....I have issues with the guide given, although I have added telnet on to Win 10, for some reason why I try and type in teh correct command it jsut says invalid command.

I am type exactly (without the ")

"telnet 192.168.1.254"

The IP address is the correct one for the router as if I type that in my browser it takes me to the router settings. Any ideas what I am doing wrong?

There is a suggest furtheer down that you dump the config file for your router and then restore it using one you have modified, hwoever as the the guide in the link, when I search for the 2 lines, they do not appear, so that method doesnt seem to work either.

I did even call my ISP, but they didnt have a clue.

Any ideas?

 

[bremen1874]

You're trying to start Telnet from within Telnet.

Open a command prompt and start Telnet from there.

Alternatively, type 'open 192.168.1.254' at the Telnet command prompt where you are.

 

[BUDFORCE]

You're trying to start Telnet from within Telnet.

Open a command prompt and start Telnet from there.

Alternatively, type 'open 192.168.1.254' at the Telnet command prompt where you are.

Thanks that helped, I got as far as this:

typed the line as per the guide but it says failed to delete the binding, reckon the setting is locked?

 

[BUDFORCE]

Nevermind I think I may have cracked it, I needed to unbind the entire port range containing 3074 so 501-5059

types that command and it seemed to accept it, also then types saveall

hopefully, maybe, possibily, with fingers crossed that might have solved it, time to get in game and test.

 

[Django x2]

you've got a cone(UDP) port range, not a port, so you'd have to unbind the range that the port fell into (501-5059)