wonder if the DNS issue has been resolved in the above firmware release?
Cheers
The issue that the OP is talking about also affects the latest firmware update for the Telecom Pace v5542 (the update in the link you provided). Seeing how this issue is still ongoing after 31/3/13, its safe to assume that we have to wait for another firmware update from Telecom & Pace to address this problem.
Looks like Telecom is in the midst of updating firmware for this device. They have added new CLI enabled firmware to the site, however as yet the firmware download link does not work.
Firmware update working now. http://telecombusiness.custhelp.com/app/answers/detail/a_id/29376
Note the Pace V5542 Gateway Firmware Update link still downloads the old firmware (B41005-TNZ7-84710.bin), however the Pace CLI Firmware link below it downloads a newer version of the firmware (B41005-TNZ-RC7-91052-CLI.bin) that is CLI enabled.
username: tnz password: tnZ90/*o
The username and password are case sensitive.
Interesting to see if the faults noted in this thread are fixed...
Bazil: Firmware update working now. http://telecombusiness.custhelp.com/app/answers/detail/a_id/29376
Note the Pace V5542 Gateway Firmware Update link still downloads the old firmware (B41005-TNZ7-84710.bin), however the Pace CLI Firmware link below it downloads a newer version of the firmware (B41005-TNZ-RC7-91052-CLI.bin) that is CLI enabled.
username: tnz password: tnZ90/*o
The username and password are case sensitive.
Interesting to see if the faults noted in this thread are fixed...
thanks for the reply - however we threw the router back at Tc and got our own. If I run into another I'll try the links.
I grabbed one of these routers out of our lab yesterday, and if I have time this weekend (unlikely!) I will see if the latest update does indeed fix the DNS issue, and if not chase up with our device team again.
plambrechtsen: I grabbed one of these routers out of our lab yesterday, and if I have time this weekend (unlikely!) I will see if the latest update does indeed fix the DNS issue, and if not chase up with our device team again.
thanks for looking into it. I think you need to really emphasize to the device team this is a big security issue and if this is your commercial level router should of been fixed months and months and months ago. It's not a small issue it's a major problem for people to using your commercial routers that's a big way to lose commercial customers
plambrechtsen: I grabbed one of these routers out of our lab yesterday, and if I have time this weekend (unlikely!) I will see if the latest update does indeed fix the DNS issue, and if not chase up with our device team again.
thanks for looking into it. I think you need to really emphasize to the device team this is a big security issue and if this is your commercial level router should of been fixed months and months and months ago. It's not a small issue it's a major problem for people to using your commercial routers that's a big way to lose commercial customers
Sorry but when the word 'commercial' is thrown in there this router would not even be on the radar. Cisco would be the only router in that area.
This Pace router works no problem for SME's utilising Cloud and SaaS. If you are running a server behind this you really need to look at 'proper' routers.
It may be moot now as i believe telecom are now supplying a technicolour TG589 for new connections.
Specs look ok Adsl/Vdsl, can do full bridging which is handy, can use decent routers behind it ready for UFB :-)
But will be good if we can get the pace sorted out. Have a few clients using software based on SQL Express and this screws up the obdc unless I use ip numbers
plambrechtsen: I grabbed one of these routers out of our lab yesterday, and if I have time this weekend (unlikely!) I will see if the latest update does indeed fix the DNS issue, and if not chase up with our device team again.
thanks for looking into it. I think you need to really emphasize to the device team this is a big security issue and if this is your commercial level router should of been fixed months and months and months ago. It's not a small issue it's a major problem for people to using your commercial routers that's a big way to lose commercial customers
Sorry but when the word 'commercial' is thrown in there this router would not even be on the radar. Cisco would be the only router in that area.
This Pace router works no problem for SME's utilising Cloud and SaaS. If you are running a server behind this you really need to look at 'proper' routers.
By commercial I mean this is the one TCom hands to business clients when they set them up with business internet.
Dreytek produce some nice routers - microtik and a few others have also got some nice little boxes around. Personally I still think my Linux based system works just fine for me.
"Fault Two: Changing Wireless Lan settings. I put in all the settings, untick WPS as I dont want it and get told I need to put an 8 digit password / pin into the WPS field. Even after doing so it fails. No combination of turning it on, off , pin codes etc let me save wireles settings.
The reason for this is Telecom technicians have decreed a pin driven wps is a security hole and turned the functionality off in the firmware (leaving push button WPs running) However they have not told the front end this, so changing your SSID, password etc results in you not being able to save settings via the gui owing to a conflict between front and back end programming issues.
"
I have tried on four of these modems and if you enter the pin (at least on the batch i got) of 13467982 as the WPS pin (with or without the WPS enabled tick it seems to allow changes to the wireless lan settings.
Please test, i cannot promise it will work with your particular router but it worked on the 4 i have for work.
clinty: It may be moot now as i believe telecom are now supplying a technicolour TG589 for new connections.
I wouldn't hold your breath, there is a history of issues with Telecom supplied Thomson/Technicolour modems.
All software has bugs it's just the way, usually they get fixed over time. The problem is Telecom never support these modems properly with firmware updates post release and because Techincolour is this psuedo white label supplier you generally can't get firmware direct from them.
I also have a Pace V5542 (running VDSL from Bigpipe / 64920 kbps down, 10336 kbps up :-)) but even with the latest firmware installed I also still have this same frustration: NetBIOS hostnames only resolve to LAN IP addresses (192.168.1.xyz) when you address then as hostname.local (ie. with ".local" appended) Being a linux household this isn't a big deal for us, but it must be a major blowout for Windows users.
Aside from the router's (apparently not changeable default FQDN of home.gateway.pace.net), it might also be a Firewall Rules default configuration issue. (By default, it seems NetBIOS ports 137:139,445 are blocked to/from * Local * Remote) To change it you need to select Custom rather than the Pace V5542's default "Security Level Low" setting.
Seems they tried to make it too user friendly to be actually user friendly. Pity, as the hardware seems capable overall.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
