> Really stupid question.....what about a wired connection on this laptop ?
> What speeds do you see from that ?
>
> (Unless there isn't a wired connection of course.)
No, that's a perfectly acceptable question, unfortunately the answer is
93Mbs in both directions.
Regarding the other issues that Jeff & John brought up:
>From Jeff:
> Is the ME102 running the Netgear firmware, or has someone
> installed firmware from a DWL-900AP+ or WAP11?
Original Netgear firmware. There is an update available, but it doesn't
mention anything critical as far as I can see. I'm, a bit reluctant to
change it because a) I've seen a number of postings about these AP's
being killed by upgrading firmware and b) I've had this AP for about 4
years, and it used to work find with a different laptop/PCMCIA card.
Yeah, I've just thought, I might dig out that old card and see if that
fixes things - update see end of message.
> Fine. Take the other potential sources of error out of the picture.
> Plug the desktop machine directly into the ME102 access point
> and try again. You might need a crossover ethernet cable.
No change
>From John:
> 1. Restore all settings to default values.
No change.
> 2. Don't use huge packets, which increases the cost of errors.
Using Windows networking, how can I change the packet size?
> 3. Make sure the ME102 has the latest firmware.
See answer above.
> 4. Use the latest Intel reference drivers and software for the 2200BG.
Got to try that one yet.
> 5. Move the wireless units at least a few feet apart.
No Change.
> 6. Try testing with:
> (a) Iperf <http://dast.nlanr.net/Projects/Iperf/>.
With desktop as server:
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 8.00 KByte (default)
------------------------------------------------------------
[820] local 192.168.0.1 port 5001 connected with 192.168.0.3 port 1555
[ ID] Interval Transfer Bandwidth
[820] 0.0-10.0 sec 3.82 MBytes 3.21 Mbits/sec
With laptop as server::
------------------------------------------------------------
Client connecting to 192.168.0.3, TCP port 5001
TCP window size: 8.00 KByte (default)
------------------------------------------------------------
[884] local 192.168.0.1 port 3320 connected with 192.168.0.3 port 5001
read on server close failed: Software caused connection abort
[ ID] Interval Transfer Bandwidth
[884] 0.0-87.2 sec 48.0 KBytes 4.51 Kbits/sec
> (b) Netio <http://freshmeat.net/projects/netio/>
I ran this in server mode on the desktop, client on the laptop.
I tried it first with a wired connection, fine, I see the client both
sends and receives, giving throughput for both.
Then I tried in wireless mode. The laptop did a 1k block size
transmission, 384 kbyte/sec, then simply hung up on reception, it never
did anything else, even though the server end said it had sent.
> 7. Check the Intel statistics after transmissions
Is this to do with the reference drivers you mentioned?
Update: I found my old PCMCIA card, and it produces practically
identical figures on all tests. So that discounts the laptops built-in
network adaptor.
I've not really much idea about how wireless networks work, (I'm a
software guy, always blame the hardware), but presumably each end has a
transmitter and a receiver. I'm now guessing that the transmitter on
the AP is bad. Is that feasible?
Thanks for all your input so far, by the way,
Regards,
Dave