[hihoo]

Hi all,
I'm new to using emule. I'm having the 'classic' closed port problem (I read something about this in several threads). The problem is that I'm not using a firewall and instead of a router I'm using tethering with a nokia phone (lumia 520) to connect to the internet. In this moment I don't have the possibility to connect to a router.
My OS is windows 7 with windows firewall disabled.
I ran a portscan (with 'Advanced port scanner') and I found only 2 open ports: 135, 445, which are not useful to be used by eMule.
How can I open the ports? Each thread I read tells that you should do it by configuring the firewall or the router, but my firewall is disabled and I don't think I can make this configuration on my 'router' becouse is a phone...

Thanks in advance for your help

[Zangune]

hihoo, on 22 December 2013 - 03:16 PM, said:

I ran a portscan (with 'Advanced port scanner') and I found only 2 open ports: 135, 445, which are not useful to be used by eMule.

It's not a good idea to use a number between 0 and 1024, but eMule can run (somewhat!) if you choose 135 and 445. Just for fun:

22/12/2013 15.45.11: Trying to setup port forwardings with UPnP...
22/12/2013 15.45.12: 8 servers in server.met found
22/12/2013 15.45.12: Found 2 part files
22/12/2013 15.45.12: Fatal Error: Unable to create socket on port 445
22/12/2013 15.45.13: eMule Version 0.50a ready
22/12/2013 15.45.14: UPnP successfully set up forwardings for ports 135 (TCP) and 445 (UDP)
22/12/2013 15.45.21: Connecting
22/12/2013 15.45.21: Connecting to eMule Security No4 (77.120.115.66:5041 - using Protocol Obfuscation) ...
22/12/2013 15.45.21: Read 192 contacts from file.
22/12/2013 15.45.21: Connected to eMule Security No4 (77.120.115.66:5041), sending login request
22/12/2013 15.45.22: Obfuscated connection established on: eMule Security No4 (77.120.115.66:5041)

High ID.
Please note my soket problem.

hihoo, on 22 December 2013 - 03:16 PM, said:

How can I open the ports?

It's not only a matter of opening, it's a matter of forwarding.
I'm your router, someone tell me he as something to give to someone in my local network, where do I have to send this traffic?
Even if in my network there are just one device this is a problem, too.

hihoo, on 22 December 2013 - 03:16 PM, said:

I don't think I can make this configuration on my 'router' becouse is a phone

It probably acts as a router.
Check your local IP in Windows: Start - All programs - Accessories open Command prompt and type ipconfig, if your IP starts with 192. your phone acts as a router, otherwise it probably acts as a modem.
Anyway you have to check if your internet service provider gives to your phone a public IP. You *have to* find it in your *phone*, *not* over internet.

If your phone acts as a modem and your provider gives to your phone a public IP the problem is in Windows, somewhere.
If your phone acts as a router and your provider gives to your phone a public IP you have to forward eMule ports to your PC's IP. This couldn't be possible or easy.
If your provider gives to your router a private IP, in example an IP that starts with 10., you have to call him. No public IP, no High ID.

This post has been edited by Zangune: 04 April 2014 - 10:53 AM

[xilolee]

Strange is it can create a socket on port 135!
Mine don't want to open a socket on it.
Anyway, I can't get high id on both ports, even if I use tcp 445 and udp 135 (without no socket errors), because probably my ISP blocks them.

[hihoo]

Thanks for your answer.
The ip of my phone (ipconfig->default gateway) is a private one (in the 192.168.0.0 - 192.168.255.255 range).
My understanding till now it's that this is a problem, but I'm not sure if it can be solved.
Furthermore I don't understand if the fact that the port scanner found only two open ports is related to the fact that my 'router' is assigned a private IP. Should I connect with a real router, more ports would probably result in being open? (it could be a silly question, I apologise in advance for my
ignorance )

PS: I already tried with UPnP... but it didn't work

This post has been edited by hihoo: 22 December 2013 - 10:14 PM

[Zangune]

xilolee, on 22 December 2013 - 10:19 PM, said:

probably my ISP blocks them.

Yes.
Incoming TCP: 23, 25, 135, 137, 138, 139, 445, 2525.
Incoming UDP: 137, 138, 139, 161, 162, 445.
Outgoing TCP 135.
Outgoing UDP: 137.

hihoo, on 22 December 2013 - 11:10 PM, said:

The ip of my phone (ipconfig->default gateway) is a private one (in the 192.168.0.0 - 192.168.255.255 range).

That means your phone acts as a router, nothing more.
You have to find the IP your provider assigns to your phone.

hihoo, on 22 December 2013 - 11:10 PM, said:

Should I connect with a real router, more ports would probably result in being open?

No.

hihoo, on 22 December 2013 - 11:10 PM, said:

I already tried with UPnP... but it didn't work

Quite surely a phone doesn't support UPnP.

This post has been edited by Zangune: 23 December 2013 - 03:25 PM

[hihoo]

hihoo, on 22 December 2013 - 11:10 PM, said:

The ip of my phone (ipconfig->default gateway) is a private one (in the 192.168.0.0 - 192.168.255.255 range).

Zangune said:

That means your phone acts as a router, nothing more.
You have to find the IP your provider assigns to your phone.

Do you mean the public ip? (being the private the one returned by ipconfig -> default gateway) Is this public IP the one you can see using sites such as http://www.whatismyip.com/ ?
Once obteined this ip, what should I do to open (or forward..) the ports?

Thanks

This post has been edited by hihoo: 23 December 2013 - 09:12 AM

[fox88]

hihoo, on 23 December 2013 - 12:09 PM, said:

Do you mean the public ip?

You get it correctly. eMule's port test will show your public IP, by the way.

hihoo, on 23 December 2013 - 12:09 PM, said:

Once obteined this ip, what should I do to open (or forward..) the ports?

http://discussions.n...ng/td-p/2248315
People tell that you cannot open random ports.
Try to get lucky with the ones which you found open.
Or use google to see if anybody managed to write suitable application for Lumia.

This post has been edited by fox88: 23 December 2013 - 06:13 PM

[Zangune]

Zangune, on 23 December 2013 - 12:54 AM, said:

You have to find the IP your provider assigns to your phone.

hihoo, on 23 December 2013 - 10:09 AM, said:

Do you mean the public ip? (being the private the one returned by ipconfig -> default gateway) Is this public IP the one you can see using sites such as http://www.whatismyip.com/ ?

Absolutely NO. Read again what I said before:

Zangune, on 22 December 2013 - 04:14 PM, said:

you have to check if your internet service provider gives to your phone a public IP. You *have to* find it in your *phone*, *not* over internet.

In your phone.
You have to know if your provider gives a public IP to your phone.
In Italy only TIM always gives a public IP to users.
If your phone gets a private IP like 10.something you cannot get HighID. In this case it's like your phone is behind a router located in your provider's server room.

hihoo, on 23 December 2013 - 10:09 AM, said:

Once obteined this ip, what should I do to open (or forward..) the ports?

If your phone allows to forward ports you have to do that in your phone.
You may need a third party application. I found nothing on Nokia site, sorry.

Just an example that won't work on your phone, Google Play.

Quote

This app was made to forward inbound connections from internet through your android device to a PC. More Information on Port Forwarding or Port Mapping technique can be found on en.wikipedia.org/wiki/Port_forwarding

CAUTION:
Providers may block inbound connections per default. For use with your public IP please clarify if you are behind a NAT or firewall. Your provider may allow you to disable the firewall. If you can ping the public IP from internet you are good to go!

This app allows you to forward a public network port to one target host of your tethered network. For example, Port Forwarder can be used to play LAN games over USB Tethering. This can also be used as connector for a mobile web-server (PC) if your android phone has a public accessible IP.