Reply
Thread Tools
Posts: 6 | Thanked: 0 times | Joined on Jul 2010
#1
Hi Folks
Can you please help me to fix my wierd problem with the wireless (wlan)
on my n900?

It is extremely slow whether in infrastructure or adhoc mode.
Its slow even if I just use it to connect to a internal LAN that is not
connected to the internet. From within my lan, pinging the n900 from a
seperate pc hooked onto the same lan results in something like this:

D:\Documents and Settings\guest>ping 192.168.99.3

Pinging 192.168.99.3 with 32 bytes of data:

Reply from 192.168.99.3: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.99.3: bytes=32 time=6ms TTL=64
Reply from 192.168.99.3: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.99.3:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms

D:\Documents and Settings\guest>ping 192.168.99.3

Pinging 192.168.99.3 with 32 bytes of data:

Request timed out.
Reply from 192.168.99.3: bytes=32 time=17ms TTL=64
Reply from 192.168.99.3: bytes=32 time=3ms TTL=64
Reply from 192.168.99.3: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.99.3:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 17ms, Average = 8ms

D:\Documents and Settings\guest>ping 192.168.99.3

Pinging 192.168.99.3 with 32 bytes of data:

Reply from 192.168.99.3: bytes=32 time=3ms TTL=64
Reply from 192.168.99.3: bytes=32 time=6ms TTL=64
Reply from 192.168.99.3: bytes=32 time=3ms TTL=64
Reply from 192.168.99.3: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.99.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 6ms, Average = 4ms

D:\Documents and Settings\guest>ping 192.168.99.3

Pinging 192.168.99.3 with 32 bytes of data:

Reply from 192.168.99.3: bytes=32 time=114ms TTL=64
Reply from 192.168.99.3: bytes=32 time=4ms TTL=64
Reply from 192.168.99.3: bytes=32 time=5ms TTL=64
Reply from 192.168.99.3: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.99.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 114ms, Average = 31ms

D:\Documents and Settings\guest>ping 192.168.99.3

Pinging 192.168.99.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.99.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

D:\Documents and Settings\guest>

As you can see the results are intermittent. Sometimes, I ping then
immediately press ctrl-c but it feels like its hanging, then all of a
sudden I get 20 ping replies and thereafter the command prompt.

Simple ssh over the internal network is slow as well.
What could the problem be ?
I've tried both getting dhcp ip address as well as using a static one.
Thanks for your help
-d
 
atilla's Avatar
Posts: 1,210 | Thanked: 597 times | Joined on Apr 2010 @ hamburg,germany
#2
do you have a other device or pc which is currently downloading?i have such probs if i download with my pc and browse with my n900
__________________


Nobody likes us but we dont care....
 
dchky's Avatar
Posts: 549 | Thanked: 299 times | Joined on Jun 2010 @ Australian in the Philippines
#3
I guess it could be any of a few things:

* Interference from a nearby access point on an overlapping channel.
* Your own access point is positioned poorly.
* You are covering the N900 wifi antenna with your hand.
* Your access point is under load, not able to properly respond to pings. (P2P can do this)
* Your AP radiated power setting is too low
* You are simply too far away from your AP to establish a good quality link.

Given that some pings are getting through, it's exceedingly unlikely to be a hardware fault. More an environmental problem.
 
Posts: 1,729 | Thanked: 388 times | Joined on Jan 2010 @ Canada
#4
or do have wifi volts at 100v?
__________________
if i did help you, just click "Thanks" on the lower right of my post. thanks!

"The best way to break a Spell is to prevent it from being cast in the first place"

N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;
 
Posts: 1,258 | Thanked: 672 times | Joined on Mar 2009
#5
Or AP's wifi powersaving is broken and you need to try lower the powersave level in n900.
 
Posts: 6 | Thanked: 0 times | Joined on Jul 2010
#6
Hi Folks, Thanks for replying.
Well, if I have to be literally standing beside an access point then I won't
have any use for the wlan facility don't you think so too? I mean I also
want to be able to use the wlan in my office and who knows where the
AP there might be. Other guys' n95s connect to the office wlans well and
here I can't even get decent interaction in my home.
I tried this with no other pc connected to the router and with the device very close to the AP. I did think about that.
I don't know guys but I think I've been conned with this thing..
-d
 
Posts: 13 | Thanked: 6 times | Joined on Oct 2012 @ Damascus, Syria
#7
Hello everyone
Maybe you have to change the wireless network mode to mixed
I tried this and I noticed a difference in speed even when I use TOR
 
Reply


 
Forum Jump


All times are GMT. The time now is 01:53.