ping packets lost

[nitroshift]

Hi y`all!

I have the following setup: Wireless Access Point ---> Router ---> 2 PC's. I get my internet through the access point. Now, when I try to ping their server with more than 1024 bytes of info i get "request timed out" every single time. This happens from both my pc's. I have a hunch that the problem lies with the ISP's access point, but I may be wrong. Also, I can't get on some web pages (msfn is one of them) and all downloads hang at various stages. I tried rebooting all the hardware without success. I am now writing from my o(ri)ffice . The ip's are static, assigned by dhcp from the isp. Have you got any idea as to why this is happening? Thanks in advance for your help.

nitroshift

[tain]

How did you come to this point?

Will normal pings (32 bytes) work? If you ping with 1024 bytes, the ping works...but with 1025 the packet is dropped? Could be a firewall issue...

It doesn't sound like an MTU issue, 1024 is pretty low, but have you used any MTU tweaks? (sometimes incorporated in "cable modem tweaks" and things of that nature)

Also, I can't get on some web pages (msfn is one of them) and all downloads hang at various stages.

This, combined with the info above, makes me think it might just be a weak wireless connection. Can you gauge the strength of it?

Why are you using DHCP to assign your static IPs?

[nitroshift]

Static dhcp ip is given by the isp, that's how they allocate the ip's to their clients, don't know why... Signal strength is around 80%. I tried the following last afternoon: ping my router with 6400 bytes, 0% loss, average ttl = 3ms. Tried to ping my access point, any packets bigger than 1024 are dropped and "request timed out" shows up. That led me to believe that the problem lies with my access point. Am I right? Funny enough, this setup worked flawlessly until a few days ago. Rang the isp and told them about the problem (the access point is theirs) and they said will come to replace it. Will see if after replacing it I'll have the same problem and will come back here to let you know.

@Tain Thank you for your help. I haven't used any tweaks, any new firmware, everything is exactly as it was when it was working.

[RogueSpear]

I've done a lot of work where I set up a network with DHCP reservations. That way you can document and map out the network a bit better but still have the ability to push certain configuration changes to your clients (like a new DNS server, etc). You may not get any answers, but it shouldn't hurt to inquire with your ISP if they've recently implemented anything in an attempt to thwart P2P/BT traffic.

[nitroshift]

@RogueSpear

They haven't, and it turned out that the problem lied with the access point as I thought. Anyway, problem sorted now