Wingate 6.2 + eMule
Feb 23 07 12:56 am
Hi,
I have an wingate sever and run behind the server a emule client.
I've redirected the Ports in Extended Networking.
I redirected the port to the pc with the emule client in "connections from he internet" and "connections to the internet"
I had run the connection test, he worked!
All worked at firs well and I had a high ID but after 15 minutes the I had a low id.
Then I made the connection test, he failured.
Sorry for my bad English, im German.
Can you help me?
Best Greetings, Michael
I have an wingate sever and run behind the server a emule client.
I've redirected the Ports in Extended Networking.
I redirected the port to the pc with the emule client in "connections from he internet" and "connections to the internet"
I had run the connection test, he worked!
All worked at firs well and I had a high ID but after 15 minutes the I had a low id.
Then I made the connection test, he failured.
Sorry for my bad English, im German.
Can you help me?
Best Greetings, Michael
Feb 23 07 11:38 pm
This is how I would troubleshoot assuming possible information is left out.
1. Since you are using a port redirection for "Connections from the internet", confirm that your network card/modem pointing towards the internet is marked as EXTERNAL in WinGate; if it was INTERNAL, then you would use LAN Connections to internet/or WinGate PC.
2. Since you are using a port redirection, confirm that you have Don't translate source ip" in the port redirection setting.
3. I believe eMule needs a TCP and UDP hole open.
4. Consider what connection method you are using. Since having port redirections, I am assuming you are using the NAT or WinGate Internet Client (WGIC) connection method - or both. Personally I would use NAT.
a) If the WGIC is catching the connection, then you can expect to see the eMule.exe application name in the Activity screen of the WinGate server. If that is the case the setup scenario could be:
1. Set the eMule application to Global Access in the WGIC properties, and I think you could remove the ip address in the port redirection of WinGate - The application set to Global in the WGIC will tell WinGate that it is claiming that port.
2. If you also have the NAT connection method available, then you could set eMule.exe to Local Access in WGIC properties and then the WGIC will allow the application to connect with NAT.
b) If you are using NAT, confirm that you have gateway and dns connectivity.
(Windows) Start menu --> run --> cmd --> ping www.wingate.com
(Windows) Start menu --> run --> cmd --> ping 210.55.214.36
5. Confirm any security suites are disabled on the WinGate server or eMule LAN Client for the sake of testing if you deem it safe. The Window Firewall is best disabled in the Windows Services.
1. Since you are using a port redirection for "Connections from the internet", confirm that your network card/modem pointing towards the internet is marked as EXTERNAL in WinGate; if it was INTERNAL, then you would use LAN Connections to internet/or WinGate PC.
2. Since you are using a port redirection, confirm that you have Don't translate source ip" in the port redirection setting.
3. I believe eMule needs a TCP and UDP hole open.
4. Consider what connection method you are using. Since having port redirections, I am assuming you are using the NAT or WinGate Internet Client (WGIC) connection method - or both. Personally I would use NAT.
a) If the WGIC is catching the connection, then you can expect to see the eMule.exe application name in the Activity screen of the WinGate server. If that is the case the setup scenario could be:
1. Set the eMule application to Global Access in the WGIC properties, and I think you could remove the ip address in the port redirection of WinGate - The application set to Global in the WGIC will tell WinGate that it is claiming that port.
2. If you also have the NAT connection method available, then you could set eMule.exe to Local Access in WGIC properties and then the WGIC will allow the application to connect with NAT.
b) If you are using NAT, confirm that you have gateway and dns connectivity.
(Windows) Start menu --> run --> cmd --> ping www.wingate.com
(Windows) Start menu --> run --> cmd --> ping 210.55.214.36
5. Confirm any security suites are disabled on the WinGate server or eMule LAN Client for the sake of testing if you deem it safe. The Window Firewall is best disabled in the Windows Services.