Arrrrrrrrrrrrrghh!

[Sephiroth]

Originally Posted by mikegreen

After a few months of happy wireless connectivity I am now having problems which I am unable to remedy.

One morning I switched all my equipment on and found I could not connect to my wireless network (this is the VM supplied Netgear router). When looking at the Network settings I was getting a 192.168.0.1 type IP rather than one beginning 82.

Tried my old Be ISP supplied Netgear router and same deal...

Sometimes I can connect when I renew the DCHP lease and I get an 82... address and am connected and able to surf away but this only happens when the router has been reset and all settings are vanilla. As soon as I get the VM config page and I rename the network and security details and save them I am back to self-assinged IP and renewing DCHP makes no difference.
Bit flumoxed TBH.

P.S.
I have spoken to a polite but useless individual on 150 who said he could see that I had connectivity and that there is no reason I should be experiencing problems. Oh, the problem is I am using a Mac ...

P.P.S. Will be happy to supply any additional info to aid troubleshooting. Cheers, Mike.

Reading the paragraph I highlighted in red reminds me of the bery rare occasions when I lose wireless connectivity to the internet.

I use the Windows diagnose & repair function on the wireless card and it works thereafter; no doubt the MAC has a similar function or youy could wheel in a PC for diagnostic purposes I realise you have a slightly more complex issue, but logically we need to find a common cause and the PC seems to be the common link.

[nick.nelson]

I had exactly this problem using a Windows PC so I'm sure it's nothing to do with Mac. It lasted about 18 hours from the morning of 31/11/09 and then miraculously started working again normally.

I think it's a problem with the Virgin DNS servers as I was able to ping various ip's but not the Virgin DNS server ip. I was unable to get to any site via a url
and my router reverted to internal (192.*) ip's I think because it was unable to get the correct settings from Virgin. I didn't even bother contacting technical support - funny how their scripts never include the possibility Virgin is at fault!

Nick

PS I am using wired ethernet to connect

[mikegreen]

Originally Posted by DaiNasty

All good as you say. IP, gateway IP and subnet all look OK.
By rights you should have a working connection.

My next thing to check would be DNS related. Can you ping or tracert to a valid site such as bbc.co.uk?

Thanks. I'll give that a go.

On a related note has anyone tried Google DNS ?

http://code.google.com/speed/public-dns/

[Dai]

Originally Posted by mikegreen

Thanks. I'll give that a go.

On a related note has anyone tried Google DNS ?

http://code.google.com/speed/public-dns/

Not as yet. I run my own DNS on the network here but I've seen reports that it's quite quick. I'll maybe give it a try on the laptop next time I'm out and about.

If the ping to name fails try a numeric such as 212.58.224.138 (bbc) or 87.106.245.143 (cableforum). That should confirm if it's a DNS issue.

[mikegreen]

Originally Posted by DaiNasty

Not as yet. I run my own DNS on the network here but I've seen reports that it's quite quick. I'll maybe give it a try on the laptop next time I'm out and about.

If the ping to name fails try a numeric such as 212.58.224.138 (bbc) or 87.106.245.143 (cableforum). That should confirm if it's a DNS issue.

This is beyond frustrating

Feel a call to tech support coming on, for all the good it did me last time as the guy just blamed it all on my using a Mac!

[Dai]

Would you try the same again please but with one of the numeric IPs I posted.

Let us know if that works.

[mikegreen]

Originally Posted by DaiNasty

Would you try the same again please but with one of the numeric IPs I posted.

Let us know if that works.

Here we go...

Ping has started ...

PING 87.106.245.143 (87.106.245.143): 56 data bytes
92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 5413 0 0000 40 01 17f2 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 764e 0 0000 40 01 f5b6 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 100b 0 0000 40 01 5bfa 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 6335 0 0000 40 01 08d0 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 5bd6 0 0000 40 01 102f 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 c581 0 0000 40 01 a683 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 80f9 0 0000 40 01 eb0b 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 bda6 0 0000 40 01 ae5e 192.168.1.2 87.106.245.143

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 ea25 0 0000 40 01 81df 192.168.1.2 87.106.245.143


--- 87.106.245.143 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

And...

Ping has started ...

PING 212.58.224.138 (212.58.224.138): 56 data bytes
92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 6ac8 0 0000 40 01 9971 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 7dce 0 0000 40 01 866b 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 0fe7 0 0000 40 01 f452 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 680e 0 0000 40 01 9c2b 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 0455 0 0000 40 01 ffe4 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 2220 0 0000 40 01 e219 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 a86e 0 0000 40 01 5bcb 192.168.1.2 212.58.224.138

92 bytes from 192.168.1.1: Destination Net Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 a822 0 0000 40 01 5c17 192.168.1.2 212.58.224.138


--- 212.58.224.138 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

When I look at the DNS settings on my Mac I only see the router IP


Should the DNS addresses 194.168.4.100 & 194.168.8.100 be there?
I did try adding these but it made no difference to anything.

Many thanks to all for your help thus far. Mike

[Dai]

This is extremely frustrating. To be honest my Mac knowledge is minimal so I don't know if what you're seeing on that last screenshot is correct or not. This adds to the difficulty.
I was starting to think faulty hardware at this point but you've tried different kit without success so unless you're the victim of bizarre coincidence even that seems unlikely.

Your Mac is talking to the router, as it's getting a valid IP address. So, something is blocking pass-through to the 'net.
Can you connect to the router's set-up pages via http://192.168.1.1
Perhaps there is something in the router settings that is disallowing net access.

Either that or take Moldova's advice. Connect a Windows PC and if that fails to connect call support for a check and exchange.

[Ignitionnet]

Don't need any MAC knowledge there. Router is reporting not being able to reach the internet, it either has no default gateway or cannot reach its' default gateway, which would be the first hop on the VM network.

Router is losing connectivity to the VM network.

DNS settings on MAC are correct if the router is configured to act as DNS proxy which it probably is. Looks to me like the whole 'DNS' thing is a red herring and the issue is simply that the router's connectivity to the Internet is going down.

A failure to pass packets through on the part of the route would result in pings timing out, not network unreachable.

Is it possible to try pinging from the router to the Internet at all?

[mikegreen]

Originally Posted by Broadbandings

Is it possible to try pinging from the router to the Internet at all?

How would I do this please?

Thanks

N.B.
Also I think your gateway theory may be correct. Have tried to connect using my N96 and although it can connect to my home network it gives a "No Gateway" or "Gateway Not Found" error when attempting to load a webpage.

[Sephiroth]

On my router (Draytek 2910) there is a maintenance menu item that allows me tell tell the router to ping (e.e.) www.bbc.co.uk.

I don't think the Netgear router VM supplies will do this but you can check the router menus from the MAC when you log onto the router.

[mikegreen]

Originally Posted by Sephiroth

On my router (Draytek 2910) there is a maintenance menu item that allows me tell tell the router to ping (e.e.) www.bbc.co.uk.

I don't think the Netgear router VM supplies will do this but you can check the router menus from the MAC when you log onto the router.

Cannot see any way to do this on the Netgear...

Anyroad up. My other half has ordered up a Vodafone dongle as she needs her laptop to able to function wirelessly (as well as the dongle being in general a handy thing to have when out and about).


Not the end of the world as we know it but this whole thing is just so Arrrrrrrrrrrrrghh!

[Phil-ntl]

Originally Posted by mikegreen

Thanks. I'll give that a go.

On a related note has anyone tried Google DNS ?

http://code.google.com/speed/public-dns/

Been using the google dns for quite a while and not only is it a fair bit faster than opendns it doesnt have any silly redirects when there is an error such as a 404.

tbh i'm quite impressed with it up to now.

[Dai]

If you log on to the router interface with your browser the menu items on the left hand side should show under 'Maintenance' an option for router status.

Check this to see if you have an IP address on the WAN side. If it shows 0.0.0.0 or blank then the router is not communicating with the cable modem.

[mikegreen]

Originally Posted by DaiNasty

If you log on to the router interface with your browser the menu items on the left hand side should show under 'Maintenance' an option for router status.

Check this to see if you have an IP address on the WAN side. If it shows 0.0.0.0 or blank then the router is not communicating with the cable modem.

Thanks. I'll give that a go!