• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DLink DI-514

Jon855

Golden Member
I am keeping getting a NAT error in Azureus and I believed I have forwarded the proper ports in my router DLink DI-514 as explained below. Any help would be nice, thank you.

In the Application Section of the DI-514 interface -
Trigger Port - 6881-6999 [TCP]
Public Port - 6881-6999[TCP]

Also my firmware is at 1.03 [latest] and if any factor here, I'm using the wireless portion of the router.
 
Originally posted by: Goosemaster
Are you sure that you are pointing to your pc's Private IP.

Make sure.

Also, make sure those ports are the ones set in Azureus

The port forward will open the port to all connections that the router has, this is how it is set up, I don't see any IP address where I'll have to enter. This's where I'm stuck.

 
Originally posted by: Jon855
Originally posted by: Goosemaster
Are you sure that you are pointing to your pc's Private IP.

Make sure.

Also, make sure those ports are the ones set in Azureus

The port forward will open the port to all connections that the router has, this is how it is set up, I don't see any IP address where I'll have to enter. This's where I'm stuck.
I believe the issue is that you are using the incorrect configuration tool.
I believ ethe correct area of the web administration is called "Virtual Servers"



Background info:

Because of NAT, traffic has to be directed at and from an internal PC since they technically do not exist on the internet.

In this case, you are telling the router what do do with traffic that is callign these ports.
YOU MUST specify the internal host that will respond.

I just helped someone set one of these up a day or two ago and there was an IP setting in virtual server

 
Back
Top