Planes, Trains and Useless Wireless Networks

Borris · 21 May 2006 at 22:19

Firstly - there are not trains or 'planes in this post. If you thought that there were, I apologise for misleading you.

Secondly - why can't my wirelessly connected machine ping ping the network?

My setup:

Modem router: 10.0.0.1 (D-Link DSL-504T)
Wireless access point: 10.0.0.254 (subnet mask 255.255.255.0) (Belkin F5D7130)

Wired box - 10.0.0.10 (sn - 255.255.255.0, gw - 10.0.0.1, dns - 10.0.0.1)

Wireless box - 10.0.0.60 (sn 255.255.255.0, gw - 10.0.0.254, dns - 10.0.0.1) (Netgear WG311)

The WAP is ssid hidden, 54g only and 128 bit WEP enabled.

My wireless machine (let's call it Gertie) can connect to the WAP, albeit at low strength, but is unale to ping it, or anything else, and t'internet access is a no-no.

I've added it's IP to the LAN client list on the wired router, so I'm now completely stuck.

Is there anything else that I need to try?

[Edit - Added hardware spec']

Burbleflop · 21 May 2006 at 22:50

Double check that you've entered the WEP key correctly - Windows likes to report you as connected sometimes when you're not.

If you're 100% sure you've entered the key right, temporarily disable security and see if that makes any difference.

Borris · 21 May 2006 at 23:47

Cheers for that - I must have copied the key incorrectly.

I can now see the network (pinging the router, WAP and other machines) - Unfortunately, that was at the same time Zen decided to turn off their primary DNS.

(Two weeks ago they changed them completely - I only found out after phoning their premium rate line - Thanks a bundle.)

tolien · 22 May 2006 at 00:01

Borris said:
(Two weeks ago they changed them completely - I only found out after phoning their premium rate line - Thanks a bundle.)

It's lo-call rate, and it has been on their support site (and in their newsletter) for ages

Jez · 22 May 2006 at 00:15

Am i the only one confused by the thread title?

Borris · 22 May 2006 at 00:29

tolien said:
It's lo-call rate, and it has been on their support site (and in their newsletter) for ages

Meh

And there was me enjoying feeling hard done by.

I never read the site, unfortunately, and I opt out of all circulars.

Now that the DNS is sorted, I still have the same problem (with the wireless, that is) - pinging away internally, but not a sausage on the outside - not even the DSL gateway or DNS.

Jez said:
Am i the only one confused by the thread title?

Ah, but it's an attention grabber, in't it

iwrox · 22 May 2006 at 06:52

Wireless box - 10.0.0.60 (sn 255.255.255.0, gw - 10.0.0.254, dns - 10.0.0.1) (Netgear WG311)

Your gateway needs to be set to the routers ip address does it not...

Burbleflop · 22 May 2006 at 07:11

iwrox said:
Wireless box - 10.0.0.60 (sn 255.255.255.0, gw - 10.0.0.254, dns - 10.0.0.1) (Netgear WG311)

Your gateway needs to be set to the routers ip address does it not...

Well spotted, indeed it should.

Borris · 22 May 2006 at 13:00

Your Honour, I enter a plea of stupidity, mitigated only by fact of knowing nothing.

Thanks guys - the machine is now up and running as it should be.

(I think I understand the WAP bit now - it's basically an invisible CAT5 cable, and your network config is the same as if it were wired.)