antiviruz Posted February 2, 2006 Report Share Posted February 2, 2006 im having problem regarding port forwarding, i already disable my firewall and i cant identify which port is open...i have read some topics on the forum but still i cant find the right 1... does a wireless connection have a different configuration?... pls some one help me... Link to comment Share on other sites More sharing options...
td4guy Posted February 2, 2006 Report Share Posted February 2, 2006 What is the brand and model of your wireless router? You will need to configure port forwarding on it. Guides can be found at http://www.portforward.com/routers.htm. Link to comment Share on other sites More sharing options...
antiviruz Posted February 2, 2006 Author Report Share Posted February 2, 2006 sorry but im new to this... i think i dont have a router since im connected through the internet to a wifi out door antena using a ethernet/lan card... how can i configure my port forwarding and Not having a NAT error... Link to comment Share on other sites More sharing options...
Firon Posted February 2, 2006 Report Share Posted February 2, 2006 Not a damn thing. You can call your ISP and ask them to, but I doubt they will. My only suggestion is to get a real ISP. Link to comment Share on other sites More sharing options...
1c3d0g Posted February 2, 2006 Report Share Posted February 2, 2006 If/when µTorrent supports NAT traversal, you may be able to get rid of the NAT Error. Until then my friend, I believe there's no way for you to get Network OK. Sorry. Link to comment Share on other sites More sharing options...
Switeck Posted February 2, 2006 Report Share Posted February 2, 2006 Having used BearShare which supports NAT traversal (also called UDP NAT hole-punching), it does not eliminate the TCP firewalled condition. There is even more complex conditions of UDP unsolicited unfirewalled and UDP solicited unfirewalled -- so a connection can be unfirewalled, unfirewalled but only for UDP, "semi-firewalled" even for UDP, and "hopelessly" firewalled on both TCP and UDP.NAT traversal doesn't actually eliminate all the blocking effects of the firewall or NAT router. It just creates a special condition where both end parties negotiate a hole through it that works for the file transfer...but assumes the connection is long-lived in order to be very useful. From what I've seen, many BitTorrent connections last only a couple minutes. The renegotiation process to reconnect to get more of the torrent could be problematic even with "perfect" connections.Unless the BitTorrent protocol has tracker-side support for seeds/peers reporting themselves as firewalled and/or behind a NAT, firewalled and unfirewalled sources will still try vainly to directly connect via TCP to firewalled connections. It's only when they fail (repeatedly?) that they might fall back and try connecting via NAT traversal (UDP NAT hole-punching).In short, NAT traversal (UDP NAT hole-punching) is not nearly as good as being unfirewalled. But it is significantly better than being firewalled. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.