Azureus & Wingate
Sep 06 07 10:50 am
Hi Qbik Staff,
It is me again :) sorry about asking alot but for this problem i searched about it in the forum and i did as you explained befor but it didn't worked well.
The problem with Azureus and port forwarding.
Wingate server: 192.168.1.1
Client: 192.168.1.5
Azureus port is 41000
i did allowed it in wingate and redirected it to 192.168.1.5
but when i test this port it in Azureus it always give me an error it didn't pass. "Testing port 41000 ... NAT Error - Connection reset by peer (196.218.114.153:41000)." what else missing?
i tried another ports didn't worked
BTW i review other posts in this forum with a pictures and did as it exactly
what i want is to forward any port to Azureus & when i test it in Azureus give me OK massege. how it come?
It is me again :) sorry about asking alot but for this problem i searched about it in the forum and i did as you explained befor but it didn't worked well.
The problem with Azureus and port forwarding.
Wingate server: 192.168.1.1
Client: 192.168.1.5
Azureus port is 41000
i did allowed it in wingate and redirected it to 192.168.1.5
but when i test this port it in Azureus it always give me an error it didn't pass. "Testing port 41000 ... NAT Error - Connection reset by peer (196.218.114.153:41000)." what else missing?
i tried another ports didn't worked
BTW i review other posts in this forum with a pictures and did as it exactly
what i want is to forward any port to Azureus & when i test it in Azureus give me OK massege. how it come?
Sep 06 07 9:24 pm
Ok, I think I have seen the image you are talking about. Let me give you a background and then I will show you the redirection. I also believe you have set the correct port number up in the Azureus software - and it needs TCP/UDP?
1. Your Port Redirection in the Extended Networking Service. You need to know the following:
a) Confirm how your network card pointing towards your router is marked in WinGate.
2. Now, when you are doing redirection for ports on that network card you need to make sure you are using the correct option in the Port Security area:
Connections from the internet = Connections to an EXTERNAL Adapter.
LAN Connections to WinGate PC = Connections to an INTERNAL Adapter.
LAN Connections to the Internet = Connections received on an INTERNAL adapter that are not for the WinGate computer.
*That last option should not be used for this scenario - because I presume your router has its port mapping to the WinGate PC.
**And for the sake of education, notice in the picture above that there is an option at the bottom right of the interface called "Default Action". The Default Action for Connections from the Internet is "Deny" - where the Default Action for Connecitons to WinGate / to internet is allow
i.e. By default, you do not need to open any ports to connect to / through an INTERNAL adapter - but you do for an EXTERNAL adapter.
Now, with all that said - here is the Redirection for an EXTERNAL adapter - and don't miss out on the "Don't translate Source IP in image" - you may not need to check that box if your adapter is INTERNAL.
If you are still having problems then make sure no third party secuirty suites with firewalls are causing the problem. Also beware that the users connecting to this Azureus port will be seen in as "Guests" in WinGate - so make sure the Guest has access to that port in the ENS
e.g.
ENS --> Policies.
Add --> Guest, user may be unknown.
Advanced tab:
Filter 1
This criterion is met if Server Port Equals 4100
*ASk for a second opinion if you are not sure
1. Your Port Redirection in the Extended Networking Service. You need to know the following:
a) Confirm how your network card pointing towards your router is marked in WinGate.
2. Now, when you are doing redirection for ports on that network card you need to make sure you are using the correct option in the Port Security area:
Connections from the internet = Connections to an EXTERNAL Adapter.
LAN Connections to WinGate PC = Connections to an INTERNAL Adapter.
LAN Connections to the Internet = Connections received on an INTERNAL adapter that are not for the WinGate computer.
*That last option should not be used for this scenario - because I presume your router has its port mapping to the WinGate PC.
**And for the sake of education, notice in the picture above that there is an option at the bottom right of the interface called "Default Action". The Default Action for Connections from the Internet is "Deny" - where the Default Action for Connecitons to WinGate / to internet is allow
i.e. By default, you do not need to open any ports to connect to / through an INTERNAL adapter - but you do for an EXTERNAL adapter.
Now, with all that said - here is the Redirection for an EXTERNAL adapter - and don't miss out on the "Don't translate Source IP in image" - you may not need to check that box if your adapter is INTERNAL.
If you are still having problems then make sure no third party secuirty suites with firewalls are causing the problem. Also beware that the users connecting to this Azureus port will be seen in as "Guests" in WinGate - so make sure the Guest has access to that port in the ENS
e.g.
ENS --> Policies.
Add --> Guest, user may be unknown.
Advanced tab:
Filter 1
This criterion is met if Server Port Equals 4100
*ASk for a second opinion if you are not sure
Sep 06 07 9:45 pm
oops - my images are showing 4100 instead of 41000
Sep 07 07 5:54 pm
Thanks alot for help
i think that i was missing to enable the guest account in polices when i did it worked well but also i didn't make redirect to "Internet computers to the wingate PC" i just make it for "Local coputers to the wingate pc"
It is working good but i want to know why this happened
But it is OK ;)
i think that i was missing to enable the guest account in polices when i did it worked well but also i didn't make redirect to "Internet computers to the wingate PC" i just make it for "Local coputers to the wingate pc"
It is working good but i want to know why this happened
But it is OK ;)
Sep 07 07 8:25 pm
Good stuff.
"It is working good but i want to know why this happened "
Welll it sounds like you have a single NIC installation - that is fine.
Router
|
|
|
Switch -----------INTERNAL - WinGate Server
|
|
|
---------------------Azureus Client
So in that scenario you would have the WinGate servers network card as Internal because NAT only works through INTERNAL adapters.
Quite a lot of networks will have two network cards in the WinGate server so to isolate the LAN Clients from the Router - it also makes it easier to manage in my opinion because you have clearly definied boundry between the internet and LAN Clients - obviously the routers has a firewall as well but generally are not as configurable as WinGate.
Router
|
|
|
EXTERNAL
WinGate PC
INTERNAL
|
|
|
Switch ------------- Azureus Client
|
|
|--------------------- LAN Client X
So in this INTERNAL / EXTERNAL Scenario - that is when you would have used "Internet computers to WinGate PC"
Now the reason you probably had to put that Guest policy in was because you had setup policies in ENS with an authentication level of "User may be assumed". Since you do not know who will be connecting to that Azureus port you are exposing to the internet then we need to allow unauthenticated access for them with the Guest account.
And the reason I used the "Server Port" policy is because when the Azureus clients on the internet connect through WinGate they are connecting to a server - if I had set it as "Client Port" then it would probably be impossible to guess what the Azuresus Clients port is being used to connect to port 41000 on the server. I hope that does not confuse ya :)
"It is working good but i want to know why this happened "
Welll it sounds like you have a single NIC installation - that is fine.
Router
|
|
|
Switch -----------INTERNAL - WinGate Server
|
|
|
---------------------Azureus Client
So in that scenario you would have the WinGate servers network card as Internal because NAT only works through INTERNAL adapters.
Quite a lot of networks will have two network cards in the WinGate server so to isolate the LAN Clients from the Router - it also makes it easier to manage in my opinion because you have clearly definied boundry between the internet and LAN Clients - obviously the routers has a firewall as well but generally are not as configurable as WinGate.
Router
|
|
|
EXTERNAL
WinGate PC
INTERNAL
|
|
|
Switch ------------- Azureus Client
|
|
|--------------------- LAN Client X
So in this INTERNAL / EXTERNAL Scenario - that is when you would have used "Internet computers to WinGate PC"
Now the reason you probably had to put that Guest policy in was because you had setup policies in ENS with an authentication level of "User may be assumed". Since you do not know who will be connecting to that Azureus port you are exposing to the internet then we need to allow unauthenticated access for them with the Guest account.
And the reason I used the "Server Port" policy is because when the Azureus clients on the internet connect through WinGate they are connecting to a server - if I had set it as "Client Port" then it would probably be impossible to guess what the Azuresus Clients port is being used to connect to port 41000 on the server. I hope that does not confuse ya :)
Sep 07 07 9:12 pm
:) you are great yes it is one nic
i see no problems everything is ok
i see no problems everything is ok