Advanced Telecom Broadband Settings (for NetComm 3G29WN Gateway)

Forums › Spark New Zealand (including Skinny and BigPipe) › Advanced Telecom Broadband Settings (for NetComm 3G29WN Gateway)

1 | 2

Mycenius

106 posts

Master Geek

ID Verified

Lifetime subscriber

#528758 3-Oct-2011 22:26

Portable Firefox didn't help - still says Firmware Update completed after just 5-10 seconds and reboots... I'll take it back to the retailer tomorrow - must be a faulty unit or had the wrong firmware forced on it or something...

Appreciate all the suggestions/advice PB...

“Two things are infinite: the universe and human stupidity; and I'm not sure about the universe.” -- Albert Einstein

Mycenius

106 posts

Master Geek

ID Verified

Lifetime subscriber

#531136 9-Oct-2011 11:21

Just for the record to close off this thread:

1. Unit went back to supplier and they couldn't get it to work. They contacted manufacturer who were mystified and asked for it to be sent back to them for investigation/etc - suggestion was wrong firmware was on there preventing further firmware updates.

2. Supplier provided a replacement brand-new unit which then exhibited all the same faults and symptoms as the original unit above. Once again the label on the unit's base said one version of firmware, but the unit had a different version actually loaded, and neither were the correct Firmware for NZ and it would not update the latter. I did all the same tests and tried every variation of the ATM & WAN settings and also each version of the Telecom/XTRA user name, etc, etc, to no avail so returned unit.

3. Ended up changing to a NetGear unit which is working fine, however it's auto-set-up function failed as it claimed to detect a static IP on my connection. When I configured manually I had to resort to the older .xadsl variant of the Telecom/XTRA user name as that's the only one it would connect under - but otherwise it's now all 100%. Whether this was possibly affecting the NetComm units above as well I don't know, but they wouldn't connect with that user name and still had the firmware issue.

“Two things are infinite: the universe and human stupidity; and I'm not sure about the universe.” -- Albert Einstein

plambrechtsen

1948 posts

Uber Geek
+1 received by user: 459
Inactive user

#531143 9-Oct-2011 12:04

Mycenius: 3. Ended up changing to a NetGear unit which is working fine, however it's auto-set-up function failed as it claimed to detect a static IP on my connection. When I configured manually I had to resort to the older .xadsl variant of the Telecom/XTRA user name as that's the only one it would connect under - but otherwise it's now all 100%. Whether this was possibly affecting the NetComm units above as well I don't know, but they wouldn't connect with that user name and still had the firmware issue.

Great, so your router was faulty...

#3 is standard no matter which ADSL hardware you use with Telecom. If you have a legacy static IP with Telecom you will always need to login with your .xadsl username & password. Logging in with user@xtrabb.co.nz which is the automatic (aka auto-set-up which the netgear would have done) would give you a pseudo static IP which won't expire / renew when you reboot the router.

The only way to get a true static IP or have inbound port 25 open to run your own email server etc is to login with your .xadsl username & password.

Mycenius

106 posts

Master Geek

ID Verified

Lifetime subscriber

#531145 9-Oct-2011 12:11

Cheers PB - yeah looks like there is something wrong with those NetComms - and yes I had a proper static IP last year for about 4 months due to assorted issues Telecom had with their caching & proxy servers which prevented me accessing correctly several website in the USA. Obviously although I officially no longer have that static IP it must still be flagged somewhere on the Telecom Network...

“Two things are infinite: the universe and human stupidity; and I'm not sure about the universe.” -- Albert Einstein

1 | 2