Wrong (80.x.x.x) DNS servers

V

vodacom3g

Vodacom Representative
Joined
Jan 14, 2005
Messages
12,065
Reaction score
2
Location
(mostly) Plattekloof, Cape Town
Can I please ask everyone who's seen the wrong DNS settings being pushed back to post their modem type and firmware and dash type and version here?

The symptom will be that you connect but can't open web sites, etc. If you get this, first do an "ipconfig/all" in a command prompt (DOS box) and check your DNS settings. If they start with 80.x.x.x, please post the details requested.

Please don't confuse this thread by posting other connection problems here, i.e. if your DNS is a 196.x.x.x IP.
 
Met die intrap slag vanoggend 9am 2 kliente met hierdie proebleem.

Both using E220's.

Dashboard version 2.2.2.1 VMCLite.

I checked the DNS servers on both, and on both they were 80.95.225.230 & 80.95.225.231

Come to think of it, the majority(say all of the customers) who had this problem who came to see me had E220's. I on the other hand was using my K3520 yesterday.
 
Make that 3.

E220.

Dash version 2.2.2.1

Same DNS servers as i posted above.

According to this customer it started 2 days ago.
 
Yes, we understand the problem and when it started.

I'm now trying to determine which products are affected.

If you're NOT affected at all, you can also post your modem and dash type - version, please.

For now the 'official fix' is to switch to Manual APN settings and enter 'internet' as your APN.
 
Customer Number 4:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Betty's Bay

ipconfig /all reveals DNS servers 80.95.225.230 & 80.95.225.231
 
Customer 5:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Heldervue/Emeraldvue, Somerset West

ipconfig /all reveals DNS servers 80.95.225.230 & 80.95.225.231
 
Customer 6:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Gordon's Bay

ipconfig /all reveals the 80.x.x.x DNS Servers.
 
Last edited:
Customer 7:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Struisbaai, Cape Agulhas

ipconfig /all reveals 80.x.x.x DNS Servers.

This customer claims that he installed VMC Full version and he could get in.
 
Last edited:
Customer 8:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Strand

ipconfig /all reveals 80.x.x.x DNS Servers.
 
Customer 9:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.117.09.04.00 (different Firmware version this time)
Location: Paarlvallei, Somerset West

Customer didnt have laptop with them, so i couldn't do the ipconfig /all, but the symptoms they described are the same. Can connect, but cannot browse or receive emails.
 
Iam3G: Looks like a theme. What happens when you either upgrade the VMC Lite software to 3.2.1 or install VMC 9.3?
 
Customer 10:

Modem: E220
Dash: 2.2.2.1 VMCLite
Firmware: 11.110.05.00.00
Location: Van der Stel, Somerset West

Customer didnt have laptop with them, so i couldn't do the ipconfig /all, but the symptoms they described are the same. Can connect, but cannot browse or receive emails.
 
nuyork said:
Iam3G: Looks like a theme. What happens when you either upgrade the VMC Lite software to 3.2.1 or install VMC 9.3?
Click to expand...

Haven't tried updating yet as i just wanted to get these people sorted because they have lost days of work.

One customer did however confirm that when he installed VMC 9.3 it worked.
 
Customer 11

Hi All:

Any update on this?

Tried getting my dad's connection fixed last night: VMCLite, Hauwei USB modem. Worked fine up to 2 days ago, and the older PCMCIA card still seems to work, though only at GPRS speeds.

It is getting the 80.xx IP addresses as DNS servers; I can connect to the gateway and the DNS servers. I can do a nslookup to google and get an IP but I can't trace or ping outside.

Sound very much exactly like the issue described.

Location:
Centurion, Clubview.
Modem: E220 I believe (Don't have all the info on my at the time, but will need to go back tonight and see if I can get it 'fixed').

Thanks !
 
Last edited:
8 of my company's remote users have the issue,gave them opendns servers to use but thanks for the info v3g

*Edit

Modem is E220 with 2.2.2.1 VMCLite
Firmware 11.110.05.00.00 in each case ( we bought a whole batch of the things )
 
Customer 12:

Modem: E220
Dash: 2.2.2.1
Firmware: 11.117.09.04.00
Location: Gordon's Bay/Heldervue

ipconfig /all reveals 80.x.x.x DNS Servers.

This time instead of changing the APN, i updated the Dash to 3.2.1.156.

It worked with this Dash without changing anything. So updating works as well.
 
OK, we can kill this.

The problem is that the older version of VMC-lite had a 'hardcoded' DNS setting for the 'Automatic' APN setting. The 80.x.x.x address.

This specific DNS server (not a Vodacom server) died 2 days ago and suddenly no-one could do DNS resolution.

By switching to the manual APN, the VC network would push back the correct DNS setting, so you could work again.

So, you can fix this by going to the manual setting or rather upgrade to V3 of VMC-Lite which fixes it properly.

V3 is on the download section of vodacom.co.za and is zero-rated. So you won't pay to download and update.

Added/

We got the server resurrected, so the automatic apn should work, but rather upgrade to V3 as soon as possible.
 
Last edited:
vodacom3g said:
OK, we can kill this.

The problem is that the older version of VMC-lite had a 'hardcoded' DNS setting for the 'Automatic' APN setting. The 80.x.x.x address.

This specific DNS server (not a Vodacom server) died 2 days ago and suddenly no-one could do DNS resolution.

By switching to the manual APN, the VC network would push back the correct DNS setting, so you could work again.

So, you can fix this by going to the manual setting or rather upgrade to V3 of VMC-Lite which fixes it properly.

V3 is on the download section of vodacom.co.za and is zero-rated. So you won't pay to download and update.

Added/

We got the server resurrected, so the automatic apn should work, but rather upgrade to V3 as soon as possible.
Click to expand...

So that means that people who still have the 2.2.2.1 dash with this problem who just waited it out, their connection would work when they tried it now?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X