my network status is always working offline... what seems to be the problem??!!!??? how do i configure my proxy settings??

Try connecting to the internet. If you already are (and you are certian you have a connection, which is very likely because you were able to make this post), tell me where you are getting that message. I don't belive Xolox will generate that. Maybe IE will, (used as Xolox's browser).

my network staus is now "connecting to the gnutella network".... but still i cant connect..... i key in the correct proxy server and port but xolox always propmt me "network error..."... what else could be wrong??!!??.... tnx

I do jnow that Gnutella does not work with proxies at this point. If you are using a proxy that you will simply not be able to get a connection.

i'm haveing the same problem. even after doing an uninstall, clean registry, and reinstall. i like this app when it works, but if i cann't get it to work i may as well go back to kazaa . somebody, anybody, PLEASE HELP!!!!!!

It will always take a long time the first time you use Xolox, because it needs to get it's own list of hosts. It will also take a long time if you use a firewall. Make sure you internet connection is up, and you have some bandwidth left to work with. (if you are using alot of it in other programs Xolox will not have any to use)

You might want to try Shareaza as an alternative... I have used Xolox as well as Bearshare, Limewire & Gnucleus... Shareaza is by far my favorite and it is rich in features... plus, of course it works. It is FREE and has no ads or spyware... what could be better... give it a try... I am certain you will like it.

i am trying Shareaza, and so far i like it. it looks like a winner. THANKS

khool_it :
First check to see what version you are using, go to help > about.
If it says v1.22 build 160 , download the latest one which is build263 which resolves connection issue you may be having.


Download it Here

KayaMan, I do have the latest build. Got it when I did the uninstall, registry clean, and reinstall. I am still looking forward to the next build hopeing it will fix this bug.