Anothe Nat Error post

[lovethistuff]

first of let me say this is the best bt client i have use so far. i have been using this since 1.13 and its great. now my problem. before i did not have any problems. now i have a nat error and maybe one or 2 of my 4 torrents will be seeding. some are stuck at .600 and will not go up. it has been a couple of days now that i have the error. i have forward the ports on my dlink and on the firewall that i have. any one know why i get the error?

[slayers]

Maybe you are forwarding to the wrong LAN IP?

The D-Link has a "Virtual Server" mode for forwarding IPs that I don't particularly trust. You could try forwarding it with a specific rule under the "Firewalls" tab.

There are many possible causes to NAT Error, you have to look at everything it involves to properly troubleshoot:

=> UPnP (OS, router and firewall enabled)?

=> Random ports?

=> Software Firewalls?

=> Router port forwarding?

=> ISP blocking?

=> DHCP setup?

=> ... ?

[lovethistuff]

UPnP = manual

random ports = No i have it set at 49156 both dlink and zone alarm

there is no isp blockling. i have been using other p2p's without trouble.

heres what i have been thinking. i had home before and it was a full version. i dled an lite version of pro. could it be that some services have been turned off that utorrent needs?

i was also thinking about moving back to home because it might be that reason.

do you guys also think this might be my source of my problems?

thanks

[slayers]

The only services uTorrent might need from Windows are the UPnP related ones. But you're not using UPnP.

Could it be Windows default firewall? Maybe it got activated when you made the switch.

[lovethistuff]

no, i dont think so. i clicked on windows firewall and it comes up saying that i need to start ics service. what services do i need in order for uTorrent to work fine?

[Firon]

SSDP Discovery Service

[lovethistuff]

tried it but still have the error. do i need some type of drivers for dlink? i am hooked up to the router by cable. hopefully we can work this out. thanks for the help

[lovethistuff]

update: i got it working now. thanks to all who help me. also a big thanks for the programers of such a great bt client. keep up the good work guys

peace

[chaosblade]

You might wanna share your solution for others to be advised.

[lovethistuff]

thoes who are using dlink, this might help you guys out. first go here http://support.dlink.com/faq/view.asp?prod_id=1191&question=DI-604%20/%20DI-614+%20/%20DI-624%20/%20DI-754%20/%20DI-764%20/%20DI-774%20/%20DI-604_revE%20/%20%20DI-614+_revB%20/%20DI-624_revC%20/%20DI-624S%20/%20DI-774_revB%20/%20DI-707P_revC%20/%20DI-704P_revb%20/%20DI-707P%20/%20DI-714P+%20/%20DI-704%20/%20DI-704P_revA

this page will give you the most common apps/games and how to foward the ports. once you decide which port you want (make sure it is in the high numbers like 49000-65000), follow the guide that d link gives you. you should now have a port foward.

the first time i did this, it was all i had to do for the network ok

Now if still have problems do this, go into your dlink router, click advance and then firewall. here you are going to make a rule for uTorrent and what other grogram you want. click enable, give it a name, then click allow. for source it will be LAN. input your ip addy and any other addy you want rule to apply to.

For Destination leave it like it is. change the ip addy to what you have from source. Protocol i left it blank (so uTorrent can use both TCP & UDP) . then put in the ports that you want. I used a range of only 2 ports ie: 49100 - 49102.

make sure that you have Schedule set to Always.

thats it you should now see "Network Ok" in uTorrent. if some one needs some more help post in here and i will try to help

LTS

[h0rnytoad1]

i think this upgrade broke the upnp code in µtorrent.

just today i had a tought time either going on the net (couldnt reach google) or getting µtorrent to connect (got nat error alot) even randomizing the port wouldnt help.

but never before i upgraded, maybe once in 1.1.7.2 but i fixed it by changing port randomly.

i never had to open any ports in my router before 1.2, been using it since 1.1.3 but now this nat error thing pops up all of a sudden.

next time nat error occurs i'll switch to 1.1.7 to check if it has better luck.

Merged Post(s):

i tried v1.1.7.2 and nat error still came up.

So its probly not a bug in the code. unless its necessary to reboot puter, router and modem ?

now im using a specific port and set it in my firewall. its still weird that it didnt happen until yesterday.

EDIT by silverfire: PLEASE DO NOT DOUBLE POST

[paystubs]

I'm a new user to uTorrent. I had been using Azureus, but it was just eating up too many system resources. Since switching, though, I've been unable to get things running without the NAT Error notice.

I had been running flawlessly with respect to ports being open when using Azureus, thanks to uPnP. I have uPnP enabled with uTorrent, but things don't seem to be working. I tried checking the connection with NatCheck at btfaq.com and it failed.

Here are my specifics:

● I'm on a 5 mbit cable connection ( ~ 5120 down/ 640 up)

● Windows XP Home

● Windows Firewall enabled, but with the uTorrent program allowed.

● uPnP had been forwarding (and still does) fine with Azureus

● I've never known mp ISP to manhandle torrent traffic.

Thanks.

paystubs

[chaosblade]

Im guessing the UPnP network port are allowed in the firewall aswell ? IIRC, rules for those are created in the firewall by default but im not sure if its enabled.

[paystubs]

Im guessing the UPnP network port are allowed in the firewall aswell ? IIRC, rules for those are created in the firewall by default but im not sure if its enabled.

Yeah, the uTorrent program is on the allow list fo Windows Firewall.

paystubs

[war59312]

I also started getting nat error in 1.2. Never got this error until 1.2 and nothing changed. I have disabled, software firewall and hardware firewall and anti virus and same. I'm behind a non plug and play router sadly. Yes the correct port is forwared etc and stil nat error. Again never had this issue until 1.2.

And it does not happen right away. It more like 5 mins later after connecting. Well downloads pretty much suck. Highest I have seen is 14kbps. I was getting over 900kbps average before build 1.2.

And nope its not the torrent or tracker. Tried many. One I am using now has 108 seeders and 849 peers. So there should be no problem with speed.

Though u torrent reports only connected to 6 seeds and 31 peers.

Oh and I'm uploading fine though at 60kbps.

[neuromonkey]

I'm having the same problem. I'm using a Linksys router & Agnitum Outpost firewall, both configured correctly. (I've even put my machine in the DMZ and shut down the firewall; no difference.) I also seem to be uploading at full speed.

I get NAT Error right away. Hm. Maybe I'll try downgrading to a previous version of µT.

[neuromonkey]

[Followup....]

Huh. I just killed my firewall and restarted µT, and it took ~3 minutes for "Nat error" to come up. The speed is good all of a sudden though. Up from ~2-4k to 55-190k... Well... It's trending back down now... 30k... 3k... 1.3k. ew.

I also turned off "Randomize port" (I've been manually updating port forwarding lately, just to be somewhat sure.) Hrrr. Ah well.

20 minutes later, upload speed remains fairly constant... Download speed was sawtooth-ing in a very regular pattern, but has since dropped to near zero... maybe as high as 10k. I'm downloading 4 things with bunches of seeds & tons of peers.

I strongly suspect that there's something more sophisticated going on with my ISP (comcast.net) because *all* my traffic (http, POP3, ftp) drops to near-nothing when µT is running. Hm.

[1c3d0g]

There's a major problem between Outpost and µTorrent, as reading all these threads will show you just how many people are having trouble with that specific combo. Lavasoft's version doesn't have this problem, even though it's (apparently) based on Outpost. So my suggestion is to try another firewall and see if it helps.

Edit: neuromonkey: did you enable Lazy_Bitfield in Advanced Options?

[chaosblade]

neuromonkey: ComCast definitly fucks with BT traffic. Try enabling Lazy Bitfield as 1c3d0g (133t sp34k sucks, really ) suggested.

[war59312]

Well I still have this issue with 1.2.1 beta as well.

[slayers]

For the record, I use Outpost with uTorrent and have no problems whatsoever.

war59312, if you're still getting NAT error there's definately something wrong with your configuration. Have you checked if your port is open with a website while uTorrent is running?

http://www.canyouseeme.org/

http://www.btfaq.com/natcheck.pl

https://www.grc.com/x/portprobe=XXXXX (substitute XXXXX for your port number)

If you get OPEN, you're all right, otherwise double check your settings.

Are you sure you enabled both TCP and UDP protocol in your router and not only UDP?

Some routers have funny ways to port forward, the D-Link for example, has "Virtual Server" which is not reliable. It's best to make a hard rule like "from WAN [all IP addresses] to LAN [your LAN IP]:port, allow TCP and UDP", or something of that nature.

Some people use a third party firewall and forget to turn off Windows firewall.

Are you using a port in the range 6881-6999?

Double check your stuff because until you get rid of NAT error speeds are not going to be there.

[war59312]

war59312, if you're still getting NAT error there's definately something wrong with your configuration. Have you checked if your port is open with a website while uTorrent is running?

http://www.canyouseeme.org/

http://www.btfaq.com/natcheck.pl

https://www.grc.com/x/portprobe=XXXXX (substitute XXXXX for your port number)

If you get OPEN, you're all right, otherwise double check your settings.

Are you sure you enabled both TCP and UDP protocol in your router and not only UDP?

Some routers have funny ways to port forward, the D-Link for example, has "Virtual Server" which is not reliable. It's best to make a hard rule like "from WAN [all IP addresses] to LAN [your LAN IP]:port, allow TCP and UDP", or something of that nature.

Some people use a third party firewall and forget to turn off Windows firewall.

Are you using a port in the range 6881-6999?

Double check your stuff because until you get rid of NAT error speeds are not going to be there.

Hey,

First off I am using the Motorola SBG1000 all in one router.

I am now running uTorrent 1.2.2 and still have this issue.

Yes I am 100% open. Yes ports are forwared correctly.

No I am not using banned ports. I have tired other ports just in case. Windows Firewall is disabled.

Hard ware firewall is disabled. No other firewall software or antivirus even installed now.

Take Care,

Will

Update:

Also http://btfaq.com/natcheck.pl reports:

Attempting connect to: xxx port 13153

Fail!

Successfully connected, but didn't get proper a BitTorrent client response. Make sure you entered a correct hash ID that corresponds to the active torrent on your system. Most likely, your network is properly configured, but repeat this test with a valid hash ID to be sure.

Response was: ''

Any ideas?