COnncetion issue with 3.02

I just downloaded and installed 3.02 pro. I now can no longer connect. I even left it running for 3 hours straight with no conncetions. I am connected directly to the internet through comcast. No routers or firewalls.

Basically I get a conncetion for 1 second and then I loose it. Anyone else experiencing this?

I am a Comcast user in the Midwest, and I performed the recommended test specified here:

http://www.limewire.com/index.jsp/refund

The test failed, thereby proving that Gnutella is being blocked. One thing that was curious, I did manage to attain an established 6346 connection with an ultrapeer for about a minute, but then it disappeared, and I haven't gotten another connection. I'm assuming Comcast is blocking Gnutella nationwide.

to further complicate matters:

i tried the test on my connection and i didn't get a GNUTELLA OK either, but i have limewire running and it works perfectly fine (i'm not with comcast).

if i get nmaxfield's post right it stopped working right after installing 3.0.2? it seems unlikely that they would choose that moment to start blocking gnutella.

did you update from a very old version of limewire?

osu_uma brings up a good point - this simple test is not completely definitive. There are other factors that could effect the outcome. For example, if osu_uma is behind a firewall (I suspect this is true), the test will never work properly even though Gnutella is available.

You are wrong. The test would work even though you are firewalled, - if only the server that you are told to connect to were still online.

Currently, this server will never respond (it was taken offline some time last year).

Performed the test and failed. ATT was recently bought by comcast. They must have switched the network over to comcast. Sucks to be me.

i have been forwarding 6346 for the longest time, still, the test doesn't give me 'GNUTELLA ok'.

i think it's something with the test.

limewire runs properly, ultrapeer, incoming/outgoing, tons of uploads...

As trap_jaw said, that server's been down for awhile, so the test is broken. We should have it fixed sometime soon.