SG Broadband Community

Hello all ,please can anybody help me .I have just started downloading movies on Azureus to the delight of my kids , but after it all working well for two weeks , NAT good , share ratio good etc all of a sudden my smileys have gone from green to yellow and my nat saying firewalled (red dot). My port that i was using is now invalid and it will not seem to accept any others .i am running in conjunction with Windows Firewall and my internet provider is is AOL . Iam using a net gear router.Have tried to suss out problem with Azureus Wikki but with me being new to all this i seem to have difficulty in fixing the problem. One thing that i have found is that i tried to down load a french rip (not many seeds and peers ) and my NAT was green but the time that i was going to take to download was massive. Please anybody help me to resolve my Azureus Firewall problem , for my kids have been promised movies which i can not deliver! I will pay a million quid ...erm well maybe not! Cheers

So the default port in azureus is no longer valid? Did this problem begin after a software or OS update? I am not familiar with AOL so I am going to ask a few questions regarding the service. Is there software required by AOL to establish your internet connection? I remember way back in the day that AOL required its users to run their software in order to establish connectivity. A couple of things to check first would be the Windows firewall to make sure that the port used by Azureus is open and check the port forwarding on your netgear router to make sure you have that same port forwarded to the computer on which you are running Azureus. The default port is TCP 22969. If you are not familiar with the Windows firewall interface let me know and I will make you a tutorial on how to access and configure it. The same also applies to your router, if you are not familiar with its web interface let me know the model you have and I will make a tutorial for you on how to access and configure it as well.

Hello , thanks for your quick reply , and sorry for not getting back to you sooner
I an new to all this so please bear with me , thanks for you patience
When i installed AOL , there was software which i had to install
On both tips that you have quoted to me about router firewall acess etc unfortunatly i do not have a clue on what to do so tutorials on both aspects would be absolutly fantastic for i have tried eveything in my small knowledge of computers to solve this problem
You time is and patience is appreciated

hI THERE , i can also remember that in my tray at the bottom of the screen there was a yellow sheild with an exclamtion mark in it , and i can also remember something about an update and for some reason i did not update ,would this have anyting to do with it -thanks again

Sorry mate router model is net gear WG111GE
CHEERS!

SORRY FRIEND - TOLD YOU I WAS NOT THE BRIGHTEST NET GEAR MODEM MODEL IS A DG834 ROUTER NOT THE AFORE MENTIONED NUMBER !!! SORRY

AX1234,

Sorry that I have not gotten back to you sooner, I however have a quick suggestion and also a question as I am a bit confused by your past few replies. I am assuming that you are running the newest version of Azureus and your problems began right after you updated to it.
I had never had any type of connectivity or firewall issues with the software until I upgraded my azureus this last weekend. Then oddly enough I began having the same issue that you sre having. So I changed the port in azureus and configured my router accordingly. I then restarted Azureus and guess what? It was still reporting a closed port. The next thing I did was disable my own personal firewall and again there was no change.
After sitting for a moment I got an idea. Sho I opened up the services snap in control module and enabled all UPNP and that did the trick. So what I am suggesting you do is enable the SSDP discovery service and also the UPNP device host service. Once you have them both up and running reboot the cpu and with any luck your connection problem should no longer be a problem.

I am fairly certain that the problem is related to azureus not your setup. Try going back to the previous release and your problem should be solved.