Looks like no oneโ€™s replied in a while. To start the conversation again, simply ask a new question.

G4 (800MHz) connects to airport network via N300 wireless modem but won't bring up a browser page (Safari or Firefox)

G4 (800MHz) connects to airport network via N300 wireless modem but won't bring up a browser page (Safari or Firefox) - so the connection is there, everything says its a goer - I get a clear black signal icon in the menu bar on top, and a clear signal strength in the Internet connect dialogue box - - but when I run either of the browsers, it just says 'not connected to internet' - even for the 'software update'.
the N300 is a Netgear N300 Wirelsess Modem Router (model DGN2200) - ADSL (802.11 b/g/n)

Posted on Apr 11, 2015 1:45 AM

Reply
Question marked as Best reply

Posted on Apr 12, 2015 8:34 AM

tests to try:


-- have you tried connecting by cable? What happens?


-- Set your dns to 8.8.8.8 and 8.8.4.4 This is the google dns server. generally faster.


Check out your settings.

apple > system preferences > network


Double click on network connection you are using.


Pick the TCP/IP tab.


Verify that you have a DNS Server.


----


You can use

harddrive > applications > utilities > network utility

to diagnose the situation.


You can ping google.com.

Result:

Ping has started ...


PING google.com (64.233.167.99): 56 data bytes

64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=215.362 ms

64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=279.597 ms

64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=189.747 ms

64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=250.657 ms

64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=183.232 ms

64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=243.753 ms

64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=173.108 ms

64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=230.239 ms

64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=180.639 ms

64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=232.177 ms


--- google.com ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 173.108/217.851/279.597/33.615 ms



If that does not work, try pinging 64.233.167.99 Result:


Ping has started ...


PING 64.233.167.99 (64.233.167.99): 56 data bytes

64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=189.655 ms

64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=213.471 ms

64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=257.873 ms

64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=172.745 ms

64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=226.723 ms

64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=171.883 ms

64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=260.308 ms

64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=172.963 ms

64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=198.840 ms

64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=181.215 ms


--- 64.233.167.99 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 171.883/204.568/260.308/32.247 ms


If pinging 17.254.3.183 works but pinging Google.com doesn't. You have a bad DNS Server address.



I use Google.


Google provides free dns lookup. Their numbers are:

8.8.8.8

8.8.4.4

6 replies
Question marked as Best reply

Apr 12, 2015 8:34 AM in response to onomy

tests to try:


-- have you tried connecting by cable? What happens?


-- Set your dns to 8.8.8.8 and 8.8.4.4 This is the google dns server. generally faster.


Check out your settings.

apple > system preferences > network


Double click on network connection you are using.


Pick the TCP/IP tab.


Verify that you have a DNS Server.


----


You can use

harddrive > applications > utilities > network utility

to diagnose the situation.


You can ping google.com.

Result:

Ping has started ...


PING google.com (64.233.167.99): 56 data bytes

64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=215.362 ms

64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=279.597 ms

64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=189.747 ms

64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=250.657 ms

64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=183.232 ms

64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=243.753 ms

64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=173.108 ms

64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=230.239 ms

64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=180.639 ms

64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=232.177 ms


--- google.com ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 173.108/217.851/279.597/33.615 ms



If that does not work, try pinging 64.233.167.99 Result:


Ping has started ...


PING 64.233.167.99 (64.233.167.99): 56 data bytes

64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=189.655 ms

64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=213.471 ms

64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=257.873 ms

64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=172.745 ms

64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=226.723 ms

64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=171.883 ms

64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=260.308 ms

64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=172.963 ms

64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=198.840 ms

64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=181.215 ms


--- 64.233.167.99 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 171.883/204.568/260.308/32.247 ms


If pinging 17.254.3.183 works but pinging Google.com doesn't. You have a bad DNS Server address.



I use Google.


Google provides free dns lookup. Their numbers are:

8.8.8.8

8.8.4.4

Apr 11, 2015 9:29 PM in response to onomy

Is the wireless frequency available to the old PPC G4 800MHz computer compatible

with any of those provided by the newer model base station choices? I doubt it.


Usually one of the issues is secure settings, as they are obsolete in the old hardware

limits and later ones generally do not apply. Try Ethernet to go online, then look for

a vintage AirPort express (early version) or other AirPort Extreme, and set it up for

use with the older gear so anything newer will not be compromised by running your

entire wireless network with no security at all. WEP, WPA, and the series of frequency

available to the older hardware is where the problem very likely is now.


Good luck & happy computing! ๐Ÿ™‚

Apr 11, 2015 9:42 PM in response to rccharles

yep -have to give this a go.
already have an older airport card - but it could well be those WEP security things ๐Ÿ™‚
Found out it does work via ethernet. I was going to try an externalUSB Wireless dongle -whenIfind it - but then rremembered that the old 800Mhz was only USB1 ๐Ÿ˜Ÿ
This computer is for a daughter who doesn't want to give up her lovely flat screen iMac ๐Ÿ™‚


Thank you very much for your input and for replying ๐Ÿ™‚

Apr 11, 2015 9:44 PM in response to K Shaffer

I think you might be right about ti being a security thing.
already have an older airport card - but it could well be those WEP security things ๐Ÿ™‚
Found out it does work via ethernet. I was going to try an externalUSB Wireless dongle -whenIfind it - but then rremembered that the old 800Mhz was only USB1 ๐Ÿ˜Ÿ
This computer is for a daughter who doesn't want to give up her lovely flat screen iMac ๐Ÿ™‚


Thank you very much for your input and for replying ๐Ÿ™‚๐Ÿ™‚

Apr 12, 2015 4:12 AM in response to onomy

A USB wireless adapter should (normally) work even under USB 1.1, but at a limited speed. For Internet connections below approx. 10 Mbps this could be OK. However, the main problem with the USB adapters is that they need special drivers, and this will be an obstacle for early operating systems. Always check the system requirements for a particular USB device.


A good alternative would be a wireless Ethernet bridge (also known as a gaming or media adapter) connected to the Ethernet port of the desktop computer. A wireless Ethernet bridge (typically) works without special driver software, and can thus be used under almost any operating system. Modern devices (Netgear WNCE2001 and Linksys WET610N are merely two examples) can handle the latest security standards.


Jan

G4 (800MHz) connects to airport network via N300 wireless modem but won't bring up a browser page (Safari or Firefox)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.