1. OS version? windows xp
2. What firewalls you have? mcafee personal firewall plus
3. How much ram? 512 mb
4. Hard Disk space available? 36.8gb
5. Connection type? i think modem
6. Modem & router brand name & model numbers? it only says "webstar" on my my modem
7. Where are you trying to connect from? my apartment
8. What version of LimeWire (LW) & Java do you have? limewire 4.12.6 pro and java 1.5.0_09
9. Who is your ISP provider (Internet Service Provider)? Rogers
10. Do this simple test for us. Using your browser go here: http://www3.limewire.com:6346/ The page should say 'Your test worked!'. What happens when you go there? it says your test worked
11. Are you sharing the connection with other computers or p2p sharing programs? If yes, please give details of set up. i only have bitcomet on my pc, but it doesnt work either
12. Is this a your 1st try at LW or is this a new problem with an experienced user. no i used limewire for a loooooooong time, and this started happening yesterday
13. Do you see a brick wall in front of the blue world icon at the bottom of LW's interface? yes

[B]i tried re-installing limewire a THOUSAND times, but it doesnt work, and its on the allow list on my mcafee firewall. It worked fine, but since yesterday, it doesnt go past the first bar (its stuck on "starting connection" and same with bitcomet). i dont know whats going on, my internet is workin fine...

anyone? i REALLY need help
i dont know what happened, it shows a brick wall on limewire but its allowed on mcafee
i also have emule and bitcomet, but all 3 cant connect... so i dont think its about the program...
i ever tried turnin off my firewall, but there is still a brick wall in front of the globe...

Rogers are known to be anti-p2p, but my understanding is they don't apply their shapers or blocks on all users ... only the high level users or perhaps in certain regions of their domain.

Try changing the listening port LW is using to a higher number between 49152 - 65535. A good one to try is 64049. ie: go to LW's menu bar, Tools>Options>Advanced>Firewalls & make the change there. Then restart LW.

If no good, then you could try deleting your LW Preferences folder whilst LW is closed; instructions here: Point #2 & 3 in Fixes for Limewire (sample image included at bottom of page.) But this will mean you will have to reset "all" your options again once you re-open LW.

Your Webstar, is it port forwarded or does it have UPnP enabled? Did you ever change anything in its settings?

Not sure whether your model has an internal NAT firewall or not. But you could always try forwarding a port if the above fails: http://www.portforward.com/english/r...0/Limewire.htm

i dont know if its port forwarded or upnp enabled cuz i dunno what those things are or how to check. and i never changed anything because uhh i dont know how to lol

Then it sounds like it certainly isn't port forwarded. Open up internet Explorer & type 192.168.0.1 into the address bar & press enter. What happens? If that doesn't work, type in http://192.168.0.1 & see what happens.

on internet explorer:
"We can't find "192.168.0.1""

on firefox:
"The connection has timed out.
The server at 192.168.0.1 is taking too long to respond."

type in http://192.168.0.1 & see what happens

same thing happens... whats the difference n e way?

and also when we got this modem (it was replaced with the old modem from rogers) i dont think we installed any software for that modem, although i wasnt home at the time...

It's not software on your computer, the concept of telnetting is communicating directly with your modem device. The softw page you'd see would be the firmware within the modem itself. But by the sounds of it your modem is "simply" a modem with no internal NAT firewall.

I presume you tried changing the listening port within LW.

I wouldn't normally recommend this, but close LW, turn off your McAffee firewall temporarily until you've finished this test & re-open LW & see if you still get the brick wall at the bottom of LW's interface.

Have you seen this? http://www.gnutellaforums.com/showth...threadid=49331

I don't see where your set up is to blame. The problem is possibly your isp.